Origin retweeted
Watching agents cohabitate is fascinating. This trace in particular reminds me of this paper arxiv.org/abs/2606.03237
My bet is that understanding the systems agents form together will become a bigger constraint on autonomy alongside humans than individual model capability.
Origin retweeted
I might be a bit rusty on my basic math, but that's a pretty big fraction for "risky commands".
Origin retweeted
I've found an interesting case of agent coordination.
Two agents were working in a shared directory. One was repeatedly sweeping the other’s unfinished changes into its commits.
The affected agent reprimanded the first and raised the issue with the user.
More traces in🧵
When the work spans multiple sessions, the workspace walkthrough helps you follow what happened, with links back to the evidence so you can check it yourself.
Here’s the investigation:
originhq.com/investigations/…
Origin retweeted
Task completion is an incomplete measure of AI work. Agent traces let us infer an organization’s norms and intents, then evaluate behavior against its purpose, practices, and policies. Securing AI work requires modeling the organization.
originhq.com/blog/norms-and-…
Origin retweeted
Defense has fundamentally shifted away from an external actor/campaign-centric model toward insider threat, but so much of what we’ve built over the past 15+ years wasn’t designed for this. Years of ATT&CK bingo have atrophied the muscles required to combat subtle acts of subversion, and now they’re occurring at machine speed and often without the users’ knowledge.
Countless teams I talk with are drowning in alerts generated by agents operating in massive grey areas, doing things that look malicious but are completely benign and vice versa. The missing piece is, as it always has been, the intent behind the action. False positive tuning was already the painful exercise of explaining that intent in org-specific context so we could make exceptions for acceptable behavior. Agents make that substantially harder through their speed, volume, and contextual ambiguity.
The next generation of security controls has to reason about intent in organizational context, because the behaviors we’ve spent many years learning to detect are becoming indistinguishable from the work we’re paying agents to do.
Origin retweeted
Using Origin's own data, I followed what agents did after receiving auto-review denials.
I found multiple cases of denial bypasses, including one where the agent attempted to launder permissions through a subagent.
Read more here:
originhq.com/research/auto-r…
Replying to @tyholms
@tyholms' latest Origin investigation asks a good question. Can an agent rewrite the rules it’s meant to follow?
A deployment safeguard blocked the work. The agents added a “one-off” exception, committed it, and used it again.
When an agent maintaining an application has set rules around deployment conditions, who has the authority to override them?
We found a case in our data where an agent bypassed another agent's rules, all without human input.
Read the investigation: originhq.com/investigations/…
Origin retweeted
Check out my new post covering AI swarms and how agents coordinate on shared surfaces. I'm also releasing Swarm Lab to observe how agents share and use information in a controlled environment: originhq.com/research/eye-of…
github.com/originsec/swarm-l…
Origin retweeted
Recently discovered that one of our agents just took itself off and tried to discover API keys on the public internet!
Yet another instance of emergent behaviour.
One of the Origin product features that we've recently enabled is called 'Findings'.
One can think of them as org-specific contextual 'detections'; but instead of acting in the flat behavioral space like legacy EDR - they're active in the semantic space where context is important and understanding an action can mean following a task across multiple sessions through delegations and handoffs.
So I was looking at our internal company findings and saw that we had discovered this behaviour several layers deep in an agent-to-subagent delegation chain.
Wrote it up here:
originhq.com/investigations/…
What does an agent do with output from a backdoored model? Our team has been testing this technique in Origin.
Our team has been testing this vector in the @originhq platform this morning and we're seeing strong detections fire via auto trace review.
If you're interested in this technique, @depletionmode put out a blog a few months ago on a similar area: originhq.com/research/the-mo…
When Codex hands work to another agent, the trace needs to follow it.
We used Origin to trace the sub-agent's session directly from the parent and see the work and context behind the handoff.
Follow the whole job from one place. Read our full investigation here: originhq.com/investigations/…
Origin retweeted
Yesterday we found an interesting trace during review of our own data. Codex needed an MCP tool it didn't have, found that Claude Code had it, and launched Claude to do the work. When Claude needed approval, Codex eventually relaunched it with --dangerously-skip-permissions.
Big thanks to @originhq for sponsoring my blog this week! SACR's Endpoint Control and Prevention report, live Oct 1 with its author and Origin's founder, deep on endpoint AI observability. Register: originhq.com/webinar/next-la…
The cases keep adding up. @TransluceAI found agents trying SQL injection and other exploits after routine data retrieval failed.
And these are only the ones we know about. Every business running agents needs to monitor them.
transluce.org/agent-activity
Agents work on your machines with your credentials. Origin helps you monitor what they’re doing and investigate unexpected behavior in the traces they leave.
originhq.com/
You can also find behavior that repeats across sessions to see whether it’s part of a wider pattern.
See what we’ve found in our own agent traces:
originhq.com/investigations















