Go Guide
Go is the Forge surface for long-running services, operational backends, gateways, internal platforms, and Kubernetes-heavy deployments. Read this tab when the agent is part of service infrastructure rather than an app UI.
Language perspective
Go users should focus on service boundaries: request lifecycles, context propagation, provider credentials, deployment health, and clean integration with existing cloud systems.
Primary surfaces:
forge-go/coreforge-go/agentforge-go/identityforge-go/authforge-go/mcp- provider and deployment adapters
Follow this path
- Start with Architecture to understand runtime boundaries.
- Read Agents with Runtime State.
- Add Provider Contract and Settings.
- Read Telemetry before production service deployment.
- Use Container and Cloud for platform rollout.
go test ./...
python3 tools/release_gate.py --root .
Contract focus
| Contract | Go reading lens |
|---|---|
| Health | Model lifecycle and readiness in service terms. |
| Telemetry | Preserve trace context across queues, HTTP boundaries, and providers. |
| Providers | Keep credentials and provider selection outside business logic. |
| Tools | Treat Tier 2 tools as service integrations with scoped authority. |
| Deployment | Prefer explicit health, secrets, and config surfaces. |
What to read next
Runtime State →
How lifecycle maps to service readiness and execution state.
Telemetry →
Required spans, signed audit events, and export behavior.
Container and Cloud →
Production deployment patterns for service runtimes.
Provider Contract →
The shared provider boundary Go services should implement cleanly.
Current guidance
Use Go for operationally simple services and backends. Keep parity expectations anchored to conformance, not package shape.