/ai-implement comment trigger work identically for both.
- Linear
- Jira
Label overview
| Label | Applied by | When | Removed when |
|---|---|---|---|
AI-Implement | You | When you want a run to start | Not removed automatically |
AI-Working | Orchestrator (auto) | When a run is dispatched and in progress | When the run completes (success or failure) |
AI-Planning | Orchestrator (auto) | While the planning phase is running | When planning completes |
Plan-Complete | Orchestrator (auto) | When planning succeeds | Not removed automatically |
Ready for Review | Orchestrator (auto) | When a PR is opened after implementation | Not removed automatically |
Label details
AI-Implement
You apply this label manually to any Linear issue you want AI-Implement to implement. The orchestrator polls for issues with this label every 60 seconds and dispatches a run for each one that is eligible.An issue must be unblocked to be picked up. An issue is considered blocked if it has any open blocking issues linked to it in Linear. Blocked issues are skipped on each poll cycle until their blockers are resolved.AI-Working
The orchestrator appliesAI-Working as soon as it dispatches a run for an issue. It acts as a live indicator that a run is in progress. The label is removed at the end of the run — whether the run succeeds, fails, or times out.If
AI-Working remains on an issue after a run should have finished, the run may have stalled. Check the dispatch log in the admin UI at /api/log and the active sessions panel. You can destroy a stuck session from the sessions panel, which also removes AI-Working and clears the issue from the dedup window.AI-Planning
When the planning phase is enabled for a team/repo mapping (the default),AI-Planning is applied while the planning workflow is running. It is removed when planning completes and execution moves to the implementation phase.Plan-Complete
Plan-Complete is applied when the planning phase finishes successfully. It is not removed automatically. You can use it to filter issues that have been planned but not yet implemented.Ready for Review
Ready for Review is applied after the implementation workflow opens a PR. The orchestrator also posts a comment on the Linear issue with a link to the PR. The label signals that the AI’s work is ready for a human reviewer.Concurrency
ThemaxInProgressAiIssues setting on each team/repo mapping controls how many issues a team mapping can have in flight (AI-Working in Linear, or Implementing in Jira) simultaneously. The default is 3. The orchestrator counts in-progress issues before dispatching and skips teams that are at their limit.
You can change the concurrency cap for a team from the admin UI or by sending a PATCH /api/mappings/:teamKey request.
/ai-implement comment trigger
Commenting/ai-implement on a PR that was opened by AI-Implement triggers a gap-fill run — no label or status field is needed. The comment must be exactly /ai-implement (no extra text) and must be posted by a collaborator with write access to the repo.
The gap-fill run checks out the existing PR branch, reviews the gap analysis comment, and pushes additional commits to address any gaps identified. The issue link and PR metadata are preserved from the original run.