Feature · Platform
Connections
Add Agent to Claude, ChatGPT, Claude Code or Codex. The model runs there on your plan and uses Agent's tools to read and assign work.
How it works
Connect
- Claude (web, desktop, mobile): Settings, Connectors, Add custom connector. Enter your Agent server's
/mcpaddress. The connector address is on Connections. - Claude Code:
claude mcp add --transport http agent <address>, then/mcpto sign in. There is also an Agent plugin for Claude Code. - ChatGPT: add an app with the same address, in developer mode or as a workspace custom app.
- Codex: install the Agent plugin, then
codex mcp login agent.
Agent opens a consent page. Pick the organization, keep or clear each permission and select Allow.
Permissions
- Read work: workers, work items and their sessions.
- Assign work and post messages: needs the member role.
- Read work context: briefs, checks, evidence, knowledge, specs and the decision log.
- Search memory.
- See pending approvals. Deciding them stays in Agent.
- Work on your own plan: take work Agent hands to your Claude or ChatGPT, and report results. Needs the member role.
- Stay connected.
The tool acts as you, within your role. What it posts is marked as coming from the connection. Nothing in the connector approves an action or writes memory.
Revoke
Select Revoke on Connections. An admin can turn connections off for the whole organization there; every connection then stops at once.
From the help article Use Agent from Claude, ChatGPT or Codex, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
ViewerNo API tokenslistMcpConnectionsLists MCP connections.
Types:
EmptyRequestreturnsListResponse<McpConnectionDto>
ViewerNo API tokensrevokeMcpConnectionRevokes the MCP connection.
Types:
RevokeMcpConnectionRequestreturnsOkResponse
ViewergetSubscriptionAccessGets subscription access.
Types:
EmptyRequestreturnsSubscriptionAccessDto
AdminNo API tokensupdateSubscriptionAccessUpdates subscription access.
Types:
UpdateSubscriptionAccessRequestreturnsSubscriptionAccessDto
ViewerlistMembersLists members.
Types:
EmptyRequestreturnsListMembersResponse
Screens
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Connector run reported
- Connector run started
- MCP connection revoked
- Policy changed
- Vendor trigger fired
- Vendor trigger removed
- Vendor trigger saved