DEV Community

Felipe L
Felipe L

Posted on Originally published at automationscookbook.com

OneCLI Launches OSS Sandboxed Agent Harness for Teams

#agents #llm #devtool

What Happened

OneCLI, a YC S26 startup, released its sandboxed agent harness on GitHub. The open‑source framework lets teams run AI agents in isolated containers, with built‑in security policies, resource limits, and audit logs. The launch includes a command‑line interface, adapters for popular services, and a lightweight orchestration layer that plugs into CI/CD pipelines.

The release targets developers building n8n or custom AI‑agent workflows who need safe, scalable deployment. By packaging agents in containers and enforcing sandbox rules, OneCLI reduces the attack surface and simplifies rolling out updates without disturbing downstream services.

Why This Matters for Builders

  • Secure execution out of the box – The harness enforces namespace isolation, file‑system restrictions, and network policies, preventing data leaks or host interference.
  • Simplified deployment – A CLI can spin up a sandboxed agent in seconds, making it easy to treat each agent as a deployable microservice in your CI/CD pipeline.
  • Resource control – CPU, memory, and I/O limits keep runaway agents from exhausting cluster resources, enabling many agents to run concurrently on shared infrastructure.
  • Auditability – Every action performed by an agent is logged, providing a clear audit trail useful for compliance and debugging.
  • Extensibility – The adapter system lets you add new data sources or APIs with minimal boilerplate, so you can extend functionality without rewriting sandbox logic.

FAQ

Q: How does OneCLI differ from running agents in a standard Docker container?

A: OneCLI adds a policy layer that enforces file‑system and network restrictions, plus automated resource limits and audit logging, delivering tighter security and better observability.

Q: Can I run OneCLI agents on Kubernetes?

A: Yes. The harness can run as a sidecar or a standalone pod and exposes a REST API that your workflow orchestrator can call.

Q: Is there any commercial support or a paid tier?

A: The project is open‑source only. The community can contribute plugins, and maintainers are open to enterprise discussions if dedicated support is needed.

Originally published on Automations Cookbook.

Top comments (0)