feat(integration): Conductor as a connectable code agent - #48
Conversation
The API and catalog have carried conductor as a full peer executor (comingSoon: false, handoffToConductor action) but the CLI picker never offered it. Adds the picker entry, API-key instructions, and skill doc mention. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM: clean, minimal wiring of an already-live server contract — the CLI payload {type:'conductor', workspaceId, apiKey} matches the production OpenAPI spec exactly (the codegen'd client union includes that variant verbatim).
Verified server-side in nominal: the conductor catalog entry exists with comingSoon: false (packages/integrations-catalog/index.ts:792), the connect route accepts and handles it (api-integrations .../connect.ts:721, validating the key via ConductorClient.getMe()), the executor union includes conductor (durable-autofixes/schemas/autofixes.ts:30), and handoffToConductor is dispatched (workflows/automations/actions/index.ts:194). Every claim in the PR body checks out.
Ran locally at head ebf6307: codegen, typecheck, lint all clean; 268/268 tests pass; clean-env build + --version smoke OK (SKILL.md is compiled into the bundle); integration connect --help from the built bundle shows Conductor in the picker, description, and --api-key help. CI is 3/3 green at this head.
Nit (non-blocking): the Conductor instructions don't mention the API-key prefix, while the Devin/Cursor/Factory instructions each state theirs — Polylane's docs say Conductor keys are user-scoped and start with sk_, so consider appending "The key starts with sk_." to CODE_AGENTS.conductor.instructions (fine as a follow-up).
Generated by Claude Code
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Auto-approved: Claude reviewed this PR and posted an LGTM verdict (see its review). A repo admin enabled this via the auto-approve workflow.
Generated by Claude Code
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 participant
The server treats
conductoras a full peer code-agent executor — it is in the public catalog (comingSoon: false), theAutofix.executorunion, and has ahandoffToConductorautomation action — butpolylane integration connectnever offered it, so it was only reachable via a rawapi call.conductorto the connectable types and the picker (code-agent category), with API-key instructions pointing atapp.conductor.build/users/api-keys--api-keyflag helphandoffToConductorinskill/SKILL.mdconductor, cursor, devin, factory🤖 Generated with Claude Code