ForgeCode is a model-agnostic coding agent runtime written in Go.

The project aims to implement the core control plane of a coding agent runtime from first principles, instead of wrapping a single provider SDK or delegating the runtime model to an existing agent framework.

ForgeCode is designed to be:

• Model agnostic, with provider adapters for OpenAI, Anthropic, OpenAI-compatible APIs, and mock providers.
• Tool oriented, with built-in coding tools such as ReadFile, WriteFile, EditFile, Bash, Glob, and Grep.
• Safe by default, with explicit permission checks, approval flows, sandboxing, checkpoints, and audit logs.
• Recoverable, using an explicit agent state machine and append-only event records.
• Extensible, with MCP client support, lifecycle hooks, slash commands, and skill packages.
• Parallel-capable, with SubAgents, Git worktree isolation, and Agent Teams.

ForgeCode has moved from architecture planning into the first P0 implementation batch.

The active master plan is maintained in docs/master-plan.md. Implementation work is scoped by the Ready/P0 tasks in docs/tasks/MASTER_TASKS.md and the two-person ownership split in docs/planning/TWO_PERSON_WORK_SPLIT.md.

• Agent runtime and autonomous tool-use loop
• Model provider abstraction
• Built-in tool registry and executor
• MCP client integration
• Permission engine and approval policy
• Context compression and token budget management
• Cross-session memory
• Skill package system
• Slash command framework
• Hook lifecycle system
• SubAgent orchestration
• Git worktree-based parallel isolation
• Agent Team coordination
• PR, SQL, and Kubernetes change review scenarios

The master plan calls for the repository to grow a planning document set that includes:

• Project overview and system architecture specs
• Module-level specs, tasks, and checklists
• Cross-module dependency graph and implementation order
• Architecture Decision Records
• Requirement-to-module-to-task traceability matrix
• 12-week implementation roadmap
• Risk register and open validation questions

Initial Go code exists for the Runtime Owner first batch. Each completed task records Evidence in its module TASKS.md and CHECKLIST.md.