CLI Flags
This page is the exhaustive flag and subcommand reference for every binary in the go-code suite: harnessd, harnesscli, go-code, cronctl, cronsd, symphd, trainerd, forensics, and install.sh.
HTTP Routes
harnessd exposes a REST + Server-Sent Events (SSE) API over a single TCP port (default the definition-based workflow routes (/v1/workflows, /v1/workflow-runs/) are registered but not yet fully documented here.
Event Catalog
Every agent run produces a real-time stream of events — typed, JSON-structured messages delivered over Server-Sent Events (SSE) from GET /v1/runs//events. Each event tells you exactly what the harness is doing: when the LLM sends a token, when a tool starts, how much a step cost, why the run failed.
Environment Variables
Environment variables are the primary way to configure harnessd and its companion programs without editing files. They form layer 5 of the 6-layer configuration cascade — higher priority than any TOML file and lower priority than future cloud/team constraints (not yet implemented). This page lists every recognized variable, its default, and its effect.
Providers & Models
This page is the complete static lookup for every provider and model in the go-code catalog. Use it to find a provider's base URL and API key variable, compare model capabilities side by side, decode short alias names, and check the catalog pricing rates before you set a cost ceiling.
Tool Catalog
The tool catalog is the complete set of capabilities the coding agent can call during a run. Every tool is a Go function registered into a Registry and exposed to the LLM via JSON-schema definitions. Understanding the catalog lets you predict which tools an agent will see, enable optional tool groups by satisfying their dependencies, and scope a run to only the tools a task actually needs.
Troubleshooting
Troubleshooting is a symptom-first guide to the most common problems you will encounter with go-code. For each symptom you will find the real cause and the exact fix — drawn from documented gotchas in the server, HTTP API, workspace, cron, Slack, MCP, TUI, and CLI layers.
Glossary
This page is a plain-language lookup for every term used across the go-code documentation. If you hit an unfamiliar word in a guide or error message, find it here, get a one-sentence definition, and follow the cross-link for the full story.
Exit Codes
This page is the exit-code contract for headless harnesscli usage — the one-shot streaming mode (harnesscli -prompt ...) and the streaming continue subcommand. It exists so shell scripts and CI pipelines can branch on a run's outcome via $? instead of parsing stdout.