What's this about?
OneCLI, a Y Combinator S26 company, launched an open-source sandboxed agent harness aimed at teams rather than individual developers.
What exactly does "sandboxed, for teams" add?
A sandbox isolates the agent so the code it runs can't reach your real filesystem, credentials or network — the mitigation people have been demanding all month as agents gained the ability to modify external state. The "for teams" part is the harder problem: shared configuration, consistent policy across developers, and an audit trail of what agents did on whose behalf. An individual can decide their own risk tolerance; an organization needs the same rules applied to everyone, and evidence afterwards.
Why is this worth noticing?
HN 52 points, 16 comments
- It's the harness as a product category rather than a research artifact, in a fortnight where DarwinX, StateM, ClawGym II and Agent Lightning all treated it as the object of study.
- Sandboxing plus team policy is the concrete answer to this month's security thread — the Copilot workflow compromise, CompoSkill's chained skills, and the Web3 survey's finding that 65% of tool calls now modify state.