Conductor for AI agents

Agents read Conductor at once. Changes and sends are held for a person's approval by default.

About Conductor

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

What an agent can do in Conductor

Every Conductor action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.

Runs at once (reads)

Looks things up in Conductor without asking first. 10 actions.

  • Get Current UserReturn the user and organization represented by the connected Conductor API key. Use this to verify which account the connection acts as.
  • Get MessageGet one transcript message by id. The content may contain sensitive prompts, agent output, configuration, or provider-specific events.
  • Get ProjectGet one Conductor project and its repository remote by project id.
  • Get SessionGet 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 WorkspaceGet 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 MessagesRead 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; req
  • List ProjectsList repositories available to the connected account for creating Conductor workspaces.
  • List SessionsList one page of agent chat sessions in a Conductor workspace.
  • List WorkspacesList one page of workspaces belonging to a Conductor project, including deep links and recent activity.
  • Query TranscriptsRun 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

Held for approval by default (changes and sends)

Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 7 actions.

  • Change Workspace StatePut 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 SessionCreate 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 WorkspaceCreate 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.
  • Rename SessionChange an existing Conductor session's display name without stopping its agent.
  • Rename WorkspaceChange the display name of an existing Conductor workspace without changing its lifecycle state.
  • Send MessageSend 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 SessionCancel 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 actio

Changes wait in Needs you

Changes and sends in Conductor are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

How approvals work

Conductor questions

Can an agent change data in Conductor on its own?

Not by default. Changes and sends in Conductor are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

What can an agent read in Conductor?

This connector lists 10 read actions. Reads run at once, without waiting for approval.

How does Conductor connect?

It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.

Bring Conductor to your agents.