Follow a run

A run is Condux’s record of one delegated piece of work. Open it from Linear or from the Condux dashboard.

While work is running

The run page shows the current stage and retains the output of completed stages. Depending on the change, you may see:

• Implementation progress and logs
• Test and validation results
• Preview links
• Browser QA evidence
• Review findings and fixes
• The final GitHub pull request

Not every run needs every stage. Condux skips stages that do not apply to the repository or change.

If Condux asks a question

Answer the focused question in Linear. The run is waiting for a product decision, not stuck. It continues after your answer is received.

If a stage fails

Open the failed stage and read its summary before digging through raw logs. Condux preserves the evidence that led to the failure so you can distinguish a product question, repository setup problem, test failure, or external service problem.

See Troubleshooting for common next steps.

Review the pull request

Condux opens a normal GitHub pull request. Review it using your existing team process:

1. Confirm the change matches the intended product outcome.
2. Review the code and any generated reports or screenshots.
3. Open preview links when the change produced them.
4. Let your normal GitHub checks complete.
5. Request changes from Condux or merge when satisfied.

Condux prepares the work for review, but your team controls the final merge.

Ask Condux to revise the pull request

To trigger another Condux implementation turn, add your feedback to a GitHub review and submit the review using Request changes. Condux temporarily marks the pull request as a draft while it works through the requested changes, updates the branch, marks the pull request ready, and requests your review again.

An ordinary pull request comment does not trigger revisions, and neither does an @mention. GitHub’s mention picker does not list Condux, so typing @co on a Condux pull request usually offers another agent instead. If a comment on a Condux pull request mentions any coding agent, Condux replies once to point you back to Request changes; it never starts work from a mention. Approvals, required checks, and merge behavior continue to follow the codebase’s configured GitHub and Condux policies.