cursor-delegate

Cursor Delegate

Use Cursor as an execution partner. Keep direction, scope decisions, risk ownership, result review, and final verification with the primary agent.

Respect execution controls

• Do not call cursor_do when the user explicitly says not to use Cursor or not to delegate. A direct user opt-out always wins.
• If cursor_do is unavailable, or cursor_status reports delegation as disabled, do not bypass the setting, repeatedly retry, or ask Cursor to re-enable itself. Complete the work in the primary agent.
• Treat CURSOR_BRIDGE_DELEGATION=off as an administrator-level host switch. It disables delegated execution but does not by itself disable cursor_context_engine, cursor_init, or cursor_status.
• Cursor Bridge exposes one fixed delegation contract. Do not invent participation levels, call-frequency controls, or slash commands.
• cursor_model owns persistent model and reasoning-effort defaults. Call its set or reset action only when the user explicitly asks to change those defaults; ordinary delegation must inherit the stored cursor_do choice without silently changing it.

Follow the default workflow

Use this responsibility chain:

primary agent defines purpose, invariants, and risk boundaries -> form a bounded task envelope -> Cursor investigates locally and executes within the envelope -> collect by task_id -> primary agent inspects the real changes and verifies them

• Decide what should be achieved, why it matters, what must not change, where Cursor may work, and what evidence makes the result acceptable. Do not delegate product direction, architecture boundaries, or state verdicts.
• Allow Cursor to locate relevant implementation, compare local approaches, and complete code, documentation, configuration, scripts, tests, and tooling inside those boundaries. Do not require the primary agent to pre-solve the task line by line.
• Once a task has been selected for delegation, normally call cursor_do once with background=true, then continue non-conflicting primary-agent work. Bridge starts FIFO work in a clean chat automatically.
• Prefer execution=fifo unless the parallel contract is clearly satisfied.
• Do not inject a unique completion marker or impose a minimum response length. Rely on task state, stable task_id or agent_id, and the actual result.