← Triage

Integrations

Triage exposes a Streamable HTTP MCP endpoint for supported AI agents. In the public external-agent configuration, the host agent is the builder and Triage is the control plane.

Typical flow

1. Start a Triage run with a task and a level.
2. Submit the agent plan against the current specification version.
3. Submit complete artifacts as work progresses.
4. Send human changes through triage_send_message; requirements invalidate stale work.
5. Finalize only after verification and review gates pass.

Security boundary

The public endpoint is rate-limited and uses request idempotency. High-risk production runs can require explicit approval. The MCP endpoint does not expose raw operator secrets.

For deployment instructions, see the repository's DEPLOYMENT.md and SECURITY.md.