Connect Conductor to your AI agent

AI Tools 17 actions available

Conductor is a cloud development platform for creating workspaces, running coding-agent sessions, exchanging messages, and searching session transcripts.

We set up the connection using your own Conductor account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.

Book a setup call → See pricing
Actions

What your agent can do in Conductor

Each one is a real action the agent can take on its own, the same things a person clicking around Conductor could do. Read-only by default; write actions are confirmed against your policy.

  • Change Workspace State Put a workspace to sleep or archive it. Both actions stop active workspace use; archive is a stronger transition but is documented as restorable. Confirm the intended target and state before calling.
  • Create Session Create another agent chat session in an existing workspace. This may start agent/model resources and incur charges; call only when the user explicitly intends a new session.
  • Create Workspace Create a cloud workspace and its first agent session. This launches compute and may incur cloud or model charges; call only when the user explicitly intends to create a new workspace.
  • Get Current User Return the user and organization represented by the connected Conductor API key. Use this to verify which account the connection acts as.
  • Get Message Get one transcript message by id. The content may contain sensitive prompts, agent output, configuration, or provider-specific events.
  • Get Project Get one Conductor project and its repository remote by project id.
  • Get Session Get one agent session's configuration and current idle, working, or error status in one read. The tool fails unless both records are retrieved and refer to the requested session.
  • Get Workspace Get a workspace's metadata and current lifecycle status in one read, including initialization progress or errors. The tool fails unless both records are retrieved and refer to the requested workspace.
  • List Messages Read one page of a session transcript or incrementally read messages after a known message ID. Returned content may contain sensitive user prompts, agent output, configuration, or provider events; request and expose it…
  • List Projects List repositories available to the connected account for creating Conductor workspaces.
  • List Sessions List one page of agent chat sessions in a Conductor workspace.
  • List Workspaces List one page of workspaces belonging to a Conductor project, including deep links and recent activity.
  • Query Transcripts Run one read-only SQL SELECT against the organization's session_transcripts_view. Results can expose sensitive transcript text across many sessions: select only necessary columns, constrain rows with LIMIT, and use this…
  • Rename Session Change an existing Conductor session's display name without stopping its agent.
  • Rename Workspace Change the display name of an existing Conductor workspace without changing its lifecycle state.
  • Send Message Send a prompt to a Conductor session agent. This can start external agent/model execution and incur charges; it is not a passive transcript append. Call only when the user intends the agent to act.
  • Stop Session Cancel only the current turn and queued messages, or archive the entire session. Both can discard queued work; archive also stops the agent and leaves the session read-only. Confirm the intended action before calling.
Setup

How we connect it

  1. 1

    Connect your account

    You create a key in Conductor, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.

  2. 2

    Set the guardrails

    Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.

  3. 3

    We keep it running

    Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.

FAQ

Conductor questions, answered.

With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions Conductor's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.

Ready to put Conductor to work?

Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.

Book a setup call → Browse all connections

All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by Conductor.