Use Codex, Claude, or another MCP client
Launch an external AI client from a card so it works as a selected agent inside the same scope and work stream.
Log in or sign up to make these docs interactive
Choose your team, project, or agent to turn guidance into links to the exact place in your workspace.
Use MCP when you want Codex, Claude Code, or another compatible client to perform a specific Delegate card using that client's own execution environment and subscription.
Before you begin
Prepare the card as you would for an in-product agent: state the outcome, sources, constraints, and evidence. Assign an agent whose persona, tools, knowledge, and authority ceiling fit the work. Ensure your external client is installed and signed in.
Select the project above and open its board to choose the card you will hand off.
Quick steps
- Open the selected project's board and choose a card with a clear outcome, sources, constraints, and evidence.
- Assign an appropriate Delegate agent, then open Send to Codex / Claude on the card.
- Under Act as, select the agent the external client will represent and choose Codex, Claude Code, or Other.
- Follow the authorization flow in the external client and claim the single pending card.
- Perform the work through MCP and verify that messages, actions, artifacts, lifecycle events, and cost appear in the original card's work stream.
- Finish or return the work from the card, then revoke an abandoned launch and create a new one rather than reusing it.
1. Start from the card
Open Send to Codex / Claude on the card. Under Act as, choose the Delegate agent the external worker should represent. This choice determines the working identity and maximum configured capabilities; your own permissions still constrain the delegation.
Choose Codex, Claude Code, or Other for another compatible MCP client.
2. Authorize and claim the work
Delegate creates a short-lived, single-use launch reference. Follow the client flow to authorize and claim that card. The reference identifies a pending handoff; it is not a reusable team credential.
If the reference expires or has already been claimed, return to the card and create a new launch. Do not copy a launch reference into shared documentation.
3. Follow the external run
The client works as the selected agent for that card. Its activity appears in the card's work stream with the delegator, lifecycle, outputs, and relevant tool activity. The same project scope, effective authority, and guarded boundaries apply.
You can guide the work from the connected flow, pause or revoke the handoff, and review the returned result on the card. Resume only after resolving the reason a run was stopped or blocked.
4. Understand billing and configuration
The external client pays for its own model execution through the subscription or environment you already use. Delegate still records and governs the work it coordinates where applicable.
This is not a model-provider setting. A consumer subscription is not provider credentials, and the MCP handoff does not make its model available to ordinary in-product runs.
What good looks like
The external client receives exactly one card, acts as the intended agent, and returns evidence to the same visible work stream. Revoking the handoff stops that route without exposing a reusable credential.
MCP is the current external-agent interface. Delegate does not currently offer a general public API.