Quadratique Docs
Monitor, review, and land Agent work
After delegation, the issue becomes the place to follow execution, inspect the result, and decide whether the work may merge.
Understand the run states
| State | Meaning |
|---|---|
| Queued | Routed to an Agent and waiting for execution capacity |
| In Progress | The machine acknowledged that the Agent run started |
| Human Review | The run completed and produced a pull request for review |
| Merging | A member approved and merge execution is underway |
| Done | The merge completed successfully |
| Failed | Execution could not complete and requires a visible member action |
| Interrupted | The active lease or machine presence was lost; manual redispatch is required |
Inspect a running attempt
The issue shows the immutable execution context:
- Agent name and revision;
- machine;
- Runtime and model;
- start time;
- lifecycle state;
- streamed transcript; and
- failure or interruption details when applicable.
Transcripts are retained for 30 days and limited to 25 MiB per run. When the limit is reached, Quadratique marks the transcript as truncated rather than accepting additional chunks.
Review successful work
Successful execution moves the issue to Human Review and attaches the pull request. Review the code, checks, run summary, transcript, and the Agent revision that produced it.
Approve
Approve the result to move the issue into Merging. When merge completes, the issue moves to Done.
Reject with feedback
Rejecting requires nonblank feedback. Quadratique creates a fresh run using:
- the current Agent revision; and
- the review feedback.
The previous run remains an immutable record of what was reviewed.
Merge failure
If merging fails, the issue returns to Human Review with the reason. Resolve the problem and approve again when the pull request is ready.