Parallel work with isolation
Use worktrees or sandboxes for separate tasks so multiple agents can implement, test, and prepare PRs in parallel.
Public launch: July 12, 2026 · Developer surface
A coding agent suite where the model is not the product prison.
Codex and Claude Code set the bar: terminal agents, IDE extensions, cloud tasks, diffs, tests, permissions, and parallel work. AGI Code targets that workflow while letting builders choose local models, BYOK providers, or invite-only AGI Cloud.
CLIVS CodeDesktop CodeWorktreesPermissions
Developer parity
The core AGI Code checklist.
Agentic CLI
Read files, edit patches, run tests, inspect git, manage permissions, compact context, and resume sessions from the terminal.
VS Code and Cursor-style extension
Chat, edit, review, accept/reject diffs, @-mention files, and switch models without leaving the editor.
Permissions before power
Ask, accept edits, plan, auto, and bypass-style modes need visible tool inputs, command risk, and workspace scope.
Use the model fit for the job
Route quick edits to fast models, hard debugging to frontier reasoning models, and private experiments to local models.
Background automation later
Cloud coding tasks should stay invite-only until metering, abuse, logs, and environment controls are production-ready.
What the ads should say
Developer positioning against Codex and Claude Code.
| Core claim | AGI Code gives developers a coding-agent workflow across CLI, desktop, web, and VS Code with Local, BYOK, and Cloud invite modes. |
| Differentiator | OpenAI and Anthropic ship excellent agents locked to their model ecosystems. AGI makes provider choice the default. |
| Proof to show | Demos should show model switching, permission prompts, file diffs, test loops, and provider labels in one session. |
| Risk to avoid | Do not imply managed cloud coding is public before invite access and control-plane readiness. |
Developer pages
Split developer traffic by workflow.
Public launch: July 12, 2026
Ship the developer product as a suite, not a terminal-only utility.
Your target users need the same task to move between CLI, editor, desktop, web, and mobile approvals without losing context or provider choice.