Configure AI implementer lanes for delegated coding work

Delegate Setup prepares configuration that assigns kinds of work to installed implementer CLIs. It discovers capabilities, loads the effective lane map, establishes how allocation decisions should be grounded, proposes lanes, confirms scope, and writes only after explicit approval. It does not dispatch coding work or edit user instruction files. Node 18+ is required, but no particular implementer must already be installed.

Discovery distinguishes installed and missing CLIs, authentication as true, false, or unknown, and model results as reported, curated aliases, unsupported, or failed. Unknown authentication for agy and Pi can mean no status probe exists. A false Claude result inside a macOS sandbox can reflect blocked Keychain access; verify authentication outside that sandbox before rejecting the CLI. Capability is separate from task suitability. Existing lanes display their global or project origin; unapproved project content is marked untrusted and cannot dispatch.

The grounding menu offers quick defaults, an interview, a usage scan, or the latter two together. Quick defaults permit opinion-based proposals, visibly labeled as such. Interview and usage modes leave optional model and effort choices unset unless the user supplied them or the schema requires them. Unknown answers shrink the proposal rather than justify assumptions. The interview covers work types, subscriptions to use or spare, scoped trust, and speed versus thoroughness.

Usage scanning counts session files and dates without reading conversations. Counts are lifetime metadata rather than current-month activity; null means unknown rather than unused. Large usage differences can prompt a role question but do not establish task fit, cost, available quota, or permission to spend. Low-usage tools are candidates only when capable, authenticated, reliable, and appropriate for the user's allocation policy. Security, concurrency, migrations, and work whose output is the product need stronger judgment than spare capacity alone supplies.

Use the skill to configure or revise which CLI handles a kind of work. Implementation requests belong to the matching delegation skill; a single dispatch's model or effort override does not require rewriting the lane map. The catalog import is documentation-only: executable helper scripts are not bundled, so actual discovery and writes require the upstream runtime.

Every proposal shows a human-readable table and complete JSON, including after tweaks. Each lane carries a Basis such as user answer, usage data, repository evidence, schema requirement, or opinion; implementer and dial choices receive separate labels when their evidence differs. Prefer a small useful map. Approval must be explicit, and scope must be established before writing. An unanswered question never authorizes a substitution.

Inputs include installed-tool discovery, existing configuration, user allocation preferences, and optional usage metadata or repository signals. The output is a delegate-fleet.v1 document whose lanes each require an implementer. Optional dials must be supported by that implementer. OpenCode requires a provider/model identifier and uses variant for intensity; Oh My Pi maps effort to its thinking flag. ZCode supports permissionMode values plan and yolo, has no model dial, and can be discovered through its installed desktop bundle.

Boolean dials include readOnly and force; other dials are nonempty strings. Timeouts use duration suffixes and must fit the relay watchdog ceiling. Read-only settings cannot be combined with write-capable permission settings, and identifiers must satisfy each relay's token rules.

Global configuration uses the XDG configuration directory or the home configuration directory. Project lanes replace whole global lanes of the same name. A project approval hash binds trust to exact content; later edits require renewed approval. Writes are built from the chosen scope's raw configuration, validated through an exact approved temporary payload, and followed by a reload confirming paths and active lanes. Use a unique file in the platform temporary directory and remove it after the attempt, including on failure. The documented validation command is:

node <skill-dir>/scripts/config.mjs validate <file>

The registry covers Claude, Cline, Codex, Command Code, OpenCode, agy, Grok, Kimi, Qoder, Vibe, Cursor, Pi, Oh My Pi, aider, copilot, warp, and zcode implementers. Each has its own supported fields. Later delegation reads the lane's implementer and uses the matching relay; this setup stops after confirming the configuration.