goose integration
Connect goose to MC-1 with evidence-aware release boundaries.
Status
Tracked version: registry-tested. Declarative provider configuration is tracked; production remains pending.
Install and configure
Install and pin the named host through its official release channel. Configure its supported OpenAI-compatible provider with MC1_BASE_URL, model colomboai/mc-1, and an MC1_API_KEY supplied through its secret mechanism. Exact setting names vary by host release.
MC1_BASE_URL=https://api.colomboai.com/v1
MC1_MODEL=colomboai/mc-1
# Set MC1_API_KEY in the host's secret store.Tools
Use the smallest supported owned read-only tool first. Preserve assistant tool-call IDs and matching tool-result continuation. A configuration recipe is not proof that every built-in tool is safe or compatible.
Streaming
Verify fragmented text, tool arguments, terminal events, usage, cancellation, and error behavior against the exact pinned release.
Reasoning
Reasoning fields and visibility vary by host and upstream provider. Do not require or claim a reasoning channel unless the pinned host preserves it through the compatible contract.
Agent Identity
This host is not recorded as natively supporting MC-1 Agent Identity. Identity and Guard must remain enforced at the MC-1/tool boundary; host metadata is not verified authority.
Known limitations
- Authenticated production verification remains deployment-specific.
- Compatibility evidence is version-bound.
- Broader tools, sessions, cancellation, errors, and usage may remain pending.
- No official partnership or native provider status is implied.
Troubleshooting
- Confirm the exact released host version.
- Confirm MC1_BASE_URL includes /v1 exactly once.
- Confirm the host sends colomboai/mc-1 on the wire.
- Check role, tool-call ID, and tool-result continuation shape.
- Re-run with one harmless owned fixture and inspect credential redaction.