cursor-bridge

Delegate bounded light-to-medium implementation, limited investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns the direction and risk boundaries. Use proactively when a bounded Cursor pass can save primary-agent time, reduce omissions, or run alongside non-conflicting work; the task needs a clear purpose, allowed scope, invariants, and checkable outcome, but not a fully pre-solved implementation. Follow the current manual, auto, active, or eager mode, collect work by task_id or agent_id, and verify it in the primary agent. Do not use when the user opts out, cursor_do is unavailable or administrator-disabled, or for product direction, architecture decisions, exclusive GUI operations, formal verification verdicts, governance state decisions, or unbounded investigation.

Help the user choose, inspect, or change how readily the primary agent delegates work to Cursor through cursor_policy. Use when the user asks when Cursor will be used, wants more or less Cursor involvement, asks which of manual, auto, active, or eager fits their workflow, wants to view the current mode, or asks for a delegation frequency control. Explain the choice with concrete examples rather than a numeric call frequency, and do not promise an unsupported slash command.