Documentation Overview
Explore technical guides, client integration instructions, safety invariants, and protocol specifications for the agentic-go developer platform.
Documentation Roadmap
Select a guide below to learn how to install, configure, verify, and extend your agentic Go workflow:
| Section | Topic | Coverage |
|---|---|---|
| Getting Started | Installation | Binary downloads, Homebrew tap instructions, curl installer, and environment validation via doctor. |
| MCP Client Setup | Configuration snippets for Claude Desktop, Cursor, Cline, and Claude Code over local stdio. | |
| Core Workflows | Verification Engine | Whole-package test execution, data race detection, touched statement coverage, and policy exit codes. |
| Safety & Containment | Filesystem boundary rules, symlink resolution, non-mutating Git guarantees, and recovery journaling. | |
| GitHub Action in CI | Continuous integration workflow configuration and automated pull request status commenting. | |
| Reference | Protocol Contracts | Formal specifications for 14 MCP tools, 7 resources, 6 prompts, and JSON schemas (context/v1, change/v1, verify/v1). |
| Frequently Asked Questions | Technical answers covering Go toolchain versions, sidecar architecture, and execution privileges. |
System Architecture Layers
Execution Model
agentic-go operates entirely on the local machine via standard input/output (stdio). It coordinates three distinct subsystems:
- Intelligence Subsystem: Communicates with a bundled
goplscompanion to parse ASTs, resolve symbols, and build compact Context Packs. - Continuity Subsystem: Anchors change sessions to content-addressed snapshot hashes (
sha256:...) to detect unexpected drift. - Assurance Subsystem: Executes impacted package test suites, detects concurrency races, and applies calibrated static analyzers.