Deep links

Conductor registers the conductor:// URL scheme. Clicking a deep link (or opening it via open conductor://...) will activate Conductor and trigger the corresponding action.

Supported links

Prompt

conductor://prompt=<encoded prompt>

Creates a new workspace in the first available repository with the given prompt pre-filled.

Prompt + repository path

conductor://prompt=<encoded prompt>&path=<repo path>

Same as above, but targets the repository at the given path. Falls back to the first repo if the path doesn't match.

The path is the absolute path to the repository's root directory on your machine — the directory you picked when adding the repository to Conductor. To find it, open the repository's settings in Conductor and look for Root path under the Misc tab.

The path must match exactly (no trailing slash), and should be URL-encoded. For example, for a repository at /Users/jane/code/my-app:

conductor://prompt=Fix%20the%20login%20bug&path=%2FUsers%2Fjane%2Fcode%2Fmy-app

Linear issue

conductor://linear_id=<issue ID>&prompt=<optional prompt>

Fetches the Linear issue, auto-detects the matching repository, and either navigates to an existing workspace on that issue's branch or creates a new one. Requires a connected Linear account.

Async plan

conductor://async?repo=<repo name>&plan=<base64 plan>

Creates a new workspace with a base64-encoded plan attached as a markdown file. The repo parameter is optional and defaults to the first repository.

Notes

All parameter values should be URL-encoded.
The generic links (prompt, path, linear_id) use a flat key=value&key=value format directly after conductor://, without a hostname or path.
The async link uses standard URL structure with a hostname (conductor://async?...).