A broad provider catalog and mid-task switching separate the coding surface from one model vendor.
Agent Atlas / Coding agents
Kilo-Org/kilocode
An open coding-agent platform spanning VS Code, JetBrains, a CLI, cloud execution, code review, multiple modes, MCP, and many model providers.
Coding agent platform
Full dossier
Project documented
Reviewed August 26, 2026
Intended operator
Developers moving among IDE, terminal, cloud, and automated review surfaces.
Primary surfaces
VS Code and JetBrains / CLI and cloud agent / automated code review
Tracked repository
Teaching mechanism
Autonomous mode deliberately removes confirmation prompts
The project documents an automation mode in which permission prompts are disabled, making the trust placed in the surrounding CI or sandbox environment explicit.
Evidence limitProject documentation states the contract; TheGitReporter has not yet traced the enforcement path through the implementation.
Inspect the source
System Map
Eight inspection boundariesProject context, specialized modes, and custom agents shape the active task envelope.
File editing, terminal, browser, and MCP capabilities cross IDE, CLI, and cloud surfaces.
Interactive surfaces use prompts while documented autonomous mode delegates trust to the surrounding environment.
Checkpoint and cross-surface continuity require deeper source inspection.
Specialized and custom agents divide work by role; worker lineage remains an inspection question.
Plan, ask, debug, code, and review modes give the operator distinct work surfaces.
README contracts, repository packages, security policy, tests, and future Daily reporting form the evidence trail.
Learn Through This Project
9 lessons
Chapter 1
Before the First Model Request
Chapter 2
The Invisible Prompt
Chapter 3
Tool Calls: Contract, Authorization, Execution
Chapter 4
Loops, Workflows, and Recovery
Chapter 5
Delegation Is a Distributed System
Chapter 7
The Approval Trap
Chapter 8
The Human Control Loop
Chapter 9
Trust Must Make Its Case
Chapter 10
The Future Has Three Branches
Latest Reporting
4 articles
Kilo’s Migration API Lets Agents Resume Without Shipping Their Transcripts
September 1, 2026 — Kilo Code’s public migration endpoint lets a configured server rediscover Claude Code or Codex history it can read, create a Kilo session per source, and make a normal retry a skip instead of a duplicate. Kilo-Org/kilocode
Coding Agents Are Building Themselves—But Git Can Prove Only Part of ItAugust 11, 2026 — Across 40,345 unique commits in ten public agent codebases, coding-agent credit becomes sharply more visible in 2026—and the missing receipts matter as much as the names that appear. openai/codex, google-gemini/gemini-cli, anomalyco/opencode, QwenLM/qwen-code, cline/cline, aaif-goose/goose, OpenHands/OpenHands, charmbracelet/crush, mistralai/mistral-vibe, Kilo-Org/kilocode
The Agent Can Refile a Worktree, Not Rewrite the Filing CabinetAugust 4, 2026 — Kilo Code’s new Agent Manager move gives an agent a way to reorganize parallel work—only through a live inventory, a targeted command, and a hard boundary around the recovery file. Kilo-Org/kilocode
Kilo Code: from fork to agentic engineering platformJuly 23, 2026 — Kilo’s CLI still carries OpenCode in its source tree. Its newest code shows what a fork has to own once it starts routing work among editors, remote sessions, and a cloud service. Kilo-Org/kilocode, anomalyco/opencode
Open Questions
- Do IDE, CLI, cloud, and autonomous modes preserve one legible permission model?
Evidence state describes what this Atlas profile can support today. It is not a product score and it is not evidence that uninspected capabilities are absent.