Introducing Conductor Cloud →Skip to docs content
Conductor

Agent modes

Understand Plan Mode, Fast Mode, reasoning controls, and agent-specific session controls

Conductor lets you change how an agent approaches a task before or during a chat. These controls affect the current session, not the repository itself.

Use Claude Code, Codex, or Cursor when you want a coding agent in a Conductor workspace. You can run one agent by itself, or run multiple agents in separate tabs or workspaces.

For setup, billing, and provider-specific limits, see Harnesses.

For workflow-level differences, see Compare Conductor vs Claude Code, Compare Conductor vs Codex, and Compare Conductor vs Cursor.

Supported controls

ControlClaude CodeCodexCursor
Plan ModeSupportedSupportedNot supported
Fast ModeSupportedSupportedNot supported
Thinking or reasoning levelSupported when the selected model exposes itSupported when the selected model exposes itNot supported
PersonalitiesNot supportedSupportedNot supported
CheckpointsSupportedSupportedNot supported
SkillsSupportedSupportedNot supported

Open the model picker to choose a Claude Code, Codex, or Cursor model. If Cursor cannot start, check that CURSOR_API_KEY is configured in Settings -> Providers -> Cursor. If Codex cannot start, check your OpenAI authentication or subscription setup.

Cursor sessions support Composer 2.5 in Conductor.

Plan Mode

Plan Mode asks the agent to make a plan before editing files. Use it when the task is ambiguous, risky, or broad enough that you want to review the approach first.

Plan Mode is useful for:

  • Refactors with unclear boundaries
  • Migrations
  • Multi-file product changes
  • Debugging where the root cause is not known yet
  • Work that should be split across multiple agents or workspaces

When the plan looks right, approve it or give feedback. If you exit Plan Mode, the agent can move from planning into implementation.

Fast Mode

Fast Mode prioritizes speed. Use it for narrow edits, simple fixes, and quick follow-up work.

Avoid Fast Mode when the task needs careful codebase analysis, large refactors, or high-stakes reasoning.

Thinking and reasoning controls

Some models expose thinking or reasoning controls. Higher settings give the agent more room to reason before answering, but may take longer or use more credits.

Use higher reasoning for architecture, debugging, migrations, and code review. Use lower reasoning for straightforward edits and short questions.

Codex personalities

Codex sessions can use personalities to change how Codex approaches work. Personalities are session-level controls. Use them when you want a different working style without changing repository instructions.

Skills

Codex and Claude Code can use skills in Conductor. If you already have repo or user skills for one agent, you can often reuse them so both agents follow the same project conventions.

Run agents together

Use separate tabs when you want Claude Code, Codex, or Cursor to work in the same workspace. Use separate workspaces when the work should happen on different branches.

Repository guidance

Mode controls are temporary. For durable guidance, use Repository Settings or checked-in instruction files such as AGENTS.md, CLAUDE.md, or skills.

On this page