Skip to content

Missions ​

A Mission turns a feature into a staged workflow with an approved brief, repository-owned tickets, implementation evidence, review findings, and delivery tracking.

Use a direct agent conversation for a focused fix or investigation. Use a Mission when you want explicit requirements and ticket approval before implementation, especially when the feature spans repositories. Mission workers are separate Korus agents; they are not simply native subagents of the conversation where you started.

Prepare the workspace ​

Connect the providers the workspace will use. Add at least one repository-backed agent to the workspace before creating a Mission. For a feature spanning an API and a frontend, add an agent for each repository to that same workspace. Tickets can only target repositories represented in the Mission's workspace.

Check those repositories have Git history and can create worktrees. Have their setup instructions, dependency requirements, and verification commands available to the agents.

Create the Mission ​

  1. Select the workspace where the feature belongs.
  2. Click New mission in the sidebar. If the workspace already has Missions, use the + beside Missions.
  3. In the Mission conversation, describe the desired outcome, constraints, and how you will know it works. During Requirements, you can also use Choose an issue… to supply an issue from a connected GitHub, GitLab, or Linear integration. Choose the provider first, then its repository, GitLab project, or Linear Team / project, and select the issue.
  4. Work with the Mission lead until the Requirements artifact is specific enough to approve.

To start from a conversation, type /mission, optionally followed by instructions, or choose + → Mission. The current agent writes the brief from the conversation and your instructions, Korus creates the Mission, sends the brief to the Mission lead as the first message and opens the Mission.

For example:

Add CSV export to the reporting page. The API and web repositories are in this workspace. Only authorized users can export; preserve the current filters; escape spreadsheet formulas. Success means a browser download with the expected rows plus API authorization and escaping tests. Do not add scheduled exports.

A selected issue supplies context for Requirements. A Linear team or project does not select an execution repository, and Mission tickets are not automatically exported as Linear issues. Review the code-repository assignment on each Mission ticket before approving implementation. Ship uses the code repository's provider: pull requests on GitHub or merge requests on GitLab.

Follow the stages ​

StageWhat you do
RequirementsReview the problem, scope, and acceptance criteria. Request changes, then approve the brief.
TicketsInspect each ticket's repository, acceptance criteria, verification, and dependencies. Approve the backlog to start implementation.
ImplementationFollow ticket progress and inspect worker conversations and evidence. Continue to Review when all tickets are done.
ReviewInspect the review summary, repository diffs, and structured findings. Remediate selected findings, then approve the review.
ShipDeliver each affected repository through a pull request or local merge.

The stages run across the top of the Mission workbench, with the conversation beside the requirements, tickets, and implementation work. Drag the divider to resize the conversation. Select an earlier stage to inspect its accepted artifact; viewing approved requirements does not restart planning or move the workflow backward.

Use Expand workbench to focus on the stage's artifacts, or Expand conversation to focus on the agent. Restore split view brings both back. Each Mission remembers its expanded pane when you return.

Use the agent tabs to switch between the Mission lead and repository workers. Repository icons and ticket selection help identify whose conversation you are reading. Blue indicators mean input is needed; orange means work is running. Red unread dots appear on the lead. ⌘K lists each Mission once and returns to its last selected agent. Mission documents open in a centered dialog; choose whether to open an agent's document request without leaving the workflow.

In the composer's teammate mentions, Mission agents appear under their Mission's name, with the current Mission first. Choose Mission lead or the relevant repository worker to direct your message to the right teammate.

To change accepted requirements or tickets, ask the Mission lead to return to the relevant stage. Stop active repository workers first. Completed work and tickets are preserved; revising a ticket makes that ticket eligible for implementation again, while unchanged completed tickets stay complete. Advancing through Requirements, Tickets, and Review still requires your approval.

Approve Requirements and Tickets ​

Wait for a proposal, read it, and give feedback before choosing Approve and continue. In Requirements, select text to leave inline comments and send them to the lead. In Tickets, open a ticket card to inspect its details and comment on the relevant text. You can also request changes directly in chat.

Approving Requirements starts ticket shaping. When the tickets are ready, the Start implementation dialog lets you choose the coding agent, model, and reasoning effort for implementation independently of the Mission lead. Inspect repository assignments and dependencies, then confirm to create isolated Mission worktrees and start the workers. This is the point where code work begins.

Mission startup shows provisioning progress. Run in background lets you return to other conversations while it prepares the workspaces and workers.

Follow implementation ​

Korus creates one Mission worktree per affected repository. Tickets in the same repository run sequentially with a repository worker; ready tickets in different repositories can run concurrently. Dependencies can keep a ticket waiting even when its repository worker is idle.

In Start implementation, enable Allow parallel agents in the same repository when you want independent, ready tickets to run together. Those agents share the repository's Mission worktree, files, and Git state. Use this only when the tickets can safely coexist; if their edits conflict, they stop for guidance.

Open a ticket to inspect its evidence or select its worker conversation for clarification. Workers record changes and verification as they complete their tickets. Implementation results advance automatically; there is no separate manual approval for every completed ticket. The explicit human review follows the completed implementation.

To start another conversation in a Mission repository worktree, right-click the Mission and choose New agent in mission worktree. This uses the existing worktree, so coordinate any edits with the Mission's workers.

Use Stop ticket when a running task needs to halt, or Retry ticket after a failed or stopped task's blocker is resolved. Stopping does not undo files already changed. Once every ticket has completed and evidence is available, choose Continue to Review.

A completed ticket needs a local commit as well as its implementation evidence. If a worker fails before committing, inspect its existing changes and resolve the reported error before retrying; preserve useful work rather than starting a duplicate implementation. During parallel implementation, Korus reuses available workers for ready tickets.

Review and remediate ​

The Mission Review stage assesses the implemented feature against the approved requirements. Its Changes tab lets you select a repository and inspect its branch or uncommitted diff, with files grouped by code, tests, documentation, and other files (use the folder button to turn grouping off). Its Review tab holds the summary and structured findings.

  1. Inspect each finding's repository, location, impact, and priority. Use Chat about finding when you need clarification.
  2. Select the findings to fix, then choose Fix N selected. The affected repository workers apply and verify the fixes in the Mission worktrees. Unselected findings are skipped during this remediation batch.
  3. Read the recorded fix evidence. Once remediation finishes, use Re-run review if you want another assessment.
  4. When the result is acceptable, choose Approve and continue to reach Ship.

This review is part of the Mission. The separate conversation command /review has its own reviewer and rounds and does not approve a Mission stage.

Ship each repository ​

Ship shows a delivery card for each affected repository. Commit any remaining intended changes, then use its Git controls to create a GitHub pull request, a draft GitLab merge request, or a local merge. Check the branch, destination, title/message, and cleanup choices before confirming. Follow Worktrees for merge prerequisites and cleanup behavior.

When the destination has advanced, use Update from main in the delivery card's Git controls; the label follows the repository's base branch name. Korus merges the base into the Mission branch. Resolve any conflicts in the Mission worktree and rerun the relevant checks, then return to Ship and refresh the Git state before merging. Updating the branch does not itself deliver the Mission.

The Mission completes when every affected repository has a recorded pull request, merge request, or local merge. A created request can still need review and merging. Mission completion does not mean the code was deployed.

Resume or clean up ​

Mission stages, accepted artifacts, run status, worktree mappings, and delivery results are saved. Return to the Mission from its workspace's sidebar to continue. Read a failure's error and fix the underlying setup, provider, or Git issue before retrying. If a stage has no active run or proposal, Continue mission can resume it when offered.

To remove a Mission, open its sidebar context menu and choose delete. The confirmation explains that Mission conversations and artifacts will be removed. Keep worktrees removes the Mission while preserving its checkouts. Delete mission and worktrees also removes the Mission worktrees and local branches and discards uncommitted changes. Preserve anything you still need before choosing that option.