At a glance
An open agent platform and developer control center with CLI, web, SDK, and automation surfaces; provider and local-model flexibility; MCP and browser tools; and local, Docker, or remote execution environments.
Good choice if
- Longer autonomous tasks in an isolated runtime
- Self-hosted agent-platform and SDK workflows
- Issue, IDE, and automation integrations beyond one terminal session
Check before choosing
- The platform is materially heavier than a focused CLI and spans separately versioned OSS app, Cloud, and SDK release trains
- Docker is the recommended local isolation; ProcessSandbox runs directly on the host and is explicitly unsafe for untrusted tasks
- Headless CLI runs in always-approve mode, and direct SDK execute_tool calls bypass the normal security analyzer and confirmation policy
See 4 more considerations
- Security analyzers and confirmation policies reduce risk but do not make model-generated actions trustworthy; remote deployments still require infrastructure hardening
- Persistent memory is opt-in, while session persistence, condensation, and memory solve different context problems
- Scheduled and event-driven automations run unattended in fresh sandboxes with the user's configured LLM, stored secrets, MCP integrations, and Git-provider credentials, so trigger scope and credential scope still require review
- Local models are supported with documented functional limitations, and the project evaluation harness is not independent evidence of product quality