Get started

Conductor for AI agents

Conductor is a cloud platform for running coding-agent sessions, letting a team spin up workspaces and track agent conversations across projects. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect ConductorSee the 17 actions ↓
AI and modelsAPI keyMCP + RESTconductor.build
AUDIT LOG · CONDUCTORPOLICY: acme-support
09:41:07 · claude · u_8f2read
conductor.list_messages
List Messages✓ allowed · 212ms
09:41:08 · claude · u_8f2read
conductor.get_message
Get Message✓ allowed · 164ms
09:41:09 · claude · u_8f2write
conductor.create_session
Create Session✓ approved · approved by user
EVERY CONDUCTOR CALL, ON THE RECORD
01 · USE CASES

What agents do in Conductor.

01

Create a new coding session

Create a new session in a workspace to start an agent working on a task.

02

Check a session's messages

List a session's messages to review what an agent has done so far.

03

Confirm before stopping a session

Stop a running session once its work is confirmed complete or no longer needed.

02 · ACTIONS

17 Conductor actions, graded by risk.

Every Conductor action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

10

Look things up. Allowed by default.

  • conductor.get_message
    Get Message
  • conductor.get_project
    Get Project
  • conductor.get_session
    Get Session
  • conductor.get_workspace
    Get Workspace
  • conductor.list_messages
    List Messages
  • conductor.list_projects
    List Projects
  • conductor.list_sessions
    List Sessions
  • conductor.list_workspaces
    List Workspaces
  • conductor.get_current_user
    Get Current User
  • conductor.query_transcripts
    Query Transcripts

write

7

Create and change things. Allow, or ask the user first.

  • conductor.send_message
    Send Message
  • conductor.create_session
    Create Session
  • conductor.create_workspace
    Create Workspace
  • conductor.stop_session
    Stop Session
  • conductor.rename_session
    Rename Session
  • conductor.rename_workspace
    Rename Workspace
  • conductor.change_workspace_state
    Change Workspace State

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Conductor in three steps.

  1. 01Your users connect ConductorThey add their Conductor api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “create Session” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Conductor through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('conductor', {
  read: 'allow',
  write: 'ask',        // create_session
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Conductor connects.

Users add their Conductor api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Conductor connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Conductor from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More ai and models apps.

Perplexity AI9 actionsAffinda119 actionsAgent Mail5 actionsAI/ML API30 actionsAivoov1 actionsAll Images AI7 actionsAltText.ai10 actionsAltTextLab2 actions
ALL AI AND MODELS APPS →
07 · FAQ

Conductor and Arc0, answered.

Q01

Can I use Conductor with Claude, ChatGPT or Cursor?

Yes. Connect Conductor to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Conductor actions you allow.

Q02

How do users connect Conductor?

Users add their Conductor api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Conductor actions can my agent take?

17 in total: 10 read, 7 write and 0 destructive, such as “create Session”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Conductor?

Yes. Allow read actions and deny writes in the Conductor policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Conductor too?

Yes. The same Conductor connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Conductor into your agent.

Your users connect Conductor once, under your brand. Your agent gets 17 actions behind your policies, with every call on the record.

Connect ConductorBrowse all apps →

Free to build · MCP + REST · Audit log on every plan