Quickstart

Get an agent connected to Conductor in under 5 minutes. Conductor is a knowledge base with a minimal MCP transport (setup only) — the compiler is archived.

Prerequisites

1. secret-gate (Python CLI) — see connect/bootstrap.md
2. Bitwarden access so secret-gate can resolve CONDUCTOR_MCP_AUTH_TOKEN
3. On Windows: PowerShell 7.2+ (pwsh), not Windows PowerShell 5.1

secret-gate status

Step 1: Export the auth token

secret-gate auth   # if needed; visible terminal / zenity — never paste password in chat
eval "$(secret-gate refresh --set ci --print-env)"
printf 'token present (%s chars)\n' "${#CONDUCTOR_MCP_AUTH_TOKEN}"

PowerShell (pwsh only):

Invoke-Expression (& secret-gate refresh --set ci --print-env --shell pwsh)
Write-Host "token present ($($env:CONDUCTOR_MCP_AUTH_TOKEN.Length) chars)"

Never echo the token value into an agent transcript.

Step 2: Connect your agent

Use the client-specific guide (env-var references only):

Client	Guide
OpenCode	connect/opencode.md
Cursor	connect/cursor.md
Codex	connect/codex.md
Claude Code	connect/claude-code.md
Others	connect/others.md

Hub: connecting.md

Step 3: Verify

./scripts/mcp-smoke.sh

Then in your agent, call:

setup("engineering-lead", "opencode")

Expected: JSON with agent_config, clone, and mcp_auth. Only tool available is setup — there is no list_business_lines / list_stages on the live server.

Where to go next

You want to...	Read
Understand what Conductor is	about/product.md
Understand the org model	about/organization.md
See the stage contracts	reference/contracts/stage-contracts.md
Orchestrate CLI onboarding tests	guides/agent-cli-orchestration.md
Troubleshoot connect	guides/connect/troubleshooting.md

Troubleshooting

Problem	Check
setup missing / 401	Token exported in parent shell? Client restarted?
secret-gate fails on Windows	Are you in pwsh 7.2+?
Looking for list_business_lines	Archived — use docs + setup only
Codex cannot reach URL	Need --sandbox danger-full-access or offline docs/guides/connect/