Delegate an issue to an Agent

Delegation routes one To Do issue to one reusable Agent. Quadratique chooses the Agent’s configured machine, Runtime, and model; the issue stores the Agent selection rather than a loose execution tuple.

Before delegating

Confirm that:

• the issue is in To Do;
• the Agent is active;
• its bound machine is online and its Runtime and model are available;
• you own the Agent or it is shared with the workspace; and
• the issue’s board is in the Agent’s allowlist.

Route the issue

1. Open the issue.
2. Open the Agent routing control.
3. Select an authorized Agent, such as Backend fixer.
4. Confirm the routing.

The issue shows the selected Agent and enters Queued. It remains queued until an eligible machine has capacity and claims the run.

You can clear or replace the routing before a machine claims it. Routing cannot change while a run is active.

What the Agent receives

At dispatch, Quadratique creates an immutable execution snapshot containing:

• the Agent identifier and revision;
• machine, Runtime, harness, and model;
• Agent instructions and execution policy;
• the allowed board;
• an issue-derived prompt; and
• the repository reference.

Edits to the Agent after dispatch do not alter that snapshot.

When execution begins

A machine first claims the queued attempt, then acknowledges that execution has started. Only after start acknowledgement does the issue move to In Progress.

The issue then exposes the Agent, machine, Runtime and model, Agent revision, and start time.

Authorization failures

Quadratique rejects routing when the member cannot invoke the Agent or the board is not allowed. If the configured Runtime or model is unavailable before claim, the run fails visibly and the issue stays To Do. Quadratique does not select a substitute Runtime, model, or Agent.

Continue the workflow

Monitor the run, review the pull request, and land the work →