Sanaf AI
Start free
AI Agents

Conductor, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Conductor account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Agents
  • Connects with a key
  • 17 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Conductor is

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

You paste in a key from your own Conductor account. It is kept encrypted, and you can withdraw it from inside Conductor whenever you like.

How a run works

One message in, the work done in Conductor.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Conductor. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Conductor account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

17 tools it already has

What it can do in Conductor

These are the ready-made tools your AI employee already has in Conductor. It is not limited to them, but it never has to be taught these.

  • 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 st
  • 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 workspa
  • 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
  • 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
  • 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 sessiontranscriptsview. Results can expose sensitive transcript text across many sessions: select only necessary columns, co
  • 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
  • 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. Confir
Access, and who is in charge of it

You stay the boss of your Conductor account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Conductor account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Conductor is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Conductor and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Conductor

Can an AI employee really work inside Conductor?
Yes. It signs in to your own Conductor account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Conductor?
No. Nothing moves and nothing is replaced. Your records stay in Conductor, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Conductor account?
You paste in a key from your own Conductor account. It is kept encrypted, and you can withdraw it from inside Conductor whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Conductor?
It has 17 ready-made tools in Conductor today, among them Change Workspace State, Create Session and Create Workspace. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Conductor and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Conductor and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Conductor?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Conductor is written down with what it did and when.