Skip to main content

The issue detail page

Click any card and its detail page opens: a breadcrumb, up to one contextual banner, a main content column, and a right-hand sidebar. Here is what each part does.

What are the contextual banners?​

At most one of these appears, right under the breadcrumb, depending on the card's state:

  • Ready to run (blue): shown on a Backlog or Todo parent card if you have issue:run. It reads "Ready to run — dispatch this card to start the agent," with a Start button (same action as dragging it into In Progress).
  • Save & ship (green): shown on a Done card that has no repository attached yet, is not rejected, and where you have delivery:ship. The work is sitting in a scratch sandbox, and Save & ship pushes it to a real repository. Without an active GitHub connection on the project, the button is disabled and the text asks you to connect one first.
  • A Stop banner (yellow): shown while a parent card is In Progress and its run is actually live, next to a Stop action. What it says and does depends on what kind of run is active; see Card review and human input for the normal-run vs. chat-run distinction. If the run has just ended but the card has not finalized yet, you instead see a neutral "The run has ended — finalizing this card…" strip.

The title area​

Below the banner: the card's id, and, if it is a subtask, a chip reading ↳ subtask of {PARENT-ID} that links back to the parent. The title shows a small lock icon once the card has left Backlog (its request text is frozen from then on). If you have environment:manage and this is not a subtask, an Open Local Environment button sits next to the title, opening the card's sandbox workspace in VS Code in a new tab.

Also in this area, on a parent card:

  • Open remote control: links the card's conversation to a Slack or Microsoft Teams thread, so a team can follow and reply from chat instead of this page. The dialog offers Open in Slack / Open in Microsoft Teams and Get link, plus Close (or Reopen, if it was closed) once a thread is linked. It is explicit about the boundary: "Messages join the card conversation; they do not become turns in the chat that created it. Closing a remote control never stops the card."
  • Follow card updates: subscribes you to the card. The first time you interact with a followed card, a dismissible banner appears: "Following this card. Milestones will appear in Updates. Want to keep working from Slack?" with its own Open remote control button.
  • A Work run / Chat run badge next to the run status, showing whether the current run was started as a direct dispatch or from a message in Chat.

Request​

The card's description, labelled "Request." While the card is still in Backlog and you have issue:write, an Edit button switches it into the same rich-text editor used at creation, with Save / Cancel. Once the card leaves Backlog, the Request is locked: a small "Locked" tag replaces Edit, and the text becomes read-only.

Two things can appear directly below the Request, only when relevant:

  • "Issue rejected": a red note with the rejection reason (if given) and when it happened, shown permanently once a card is terminally rejected.
  • "Request changes history": an amber panel listing every time a human sent the card back for rework, each entry timestamped with the feedback given at the time. If there is more than one, only the latest shows by default, with a "Show all N" toggle.

Plan (subtask list)​

If the card has children, a "Plan · N/M tasks done" section lists each subtask as its own row (id, title, and a status pill). Clicking a row opens that subtask's own detail page. See Subtasks, agents, and finishing work.

What do the tabs show?​

A parent card gets four tabs; a subtask only ever gets one (Activity), and its detail page is deliberately stripped down.

  • Conversation: the human and agent communication rail. A running timeline of the agent's progress messages (grouped under an "ACE" avatar when back-to-back) interleaved with any comments a person added, newest-first by default (toggle to oldest-first). With issue:run, a message box at the bottom ("Message ACE…", Enter to send, Shift+Enter for a new line) lets you add to the conversation, and the reply tells you whether it went to the live run, started a new run, or was saved because a review is pending. When there is nothing yet: "No conversation yet. Messages from the agent will appear here."
  • Activity: this card's own slice of the project Activity feed, showing the first 3 entries with a "View all activity (N)" expander.
  • Artifacts: reserved for files, diagrams, and other agent outputs. It always shows "No artifacts yet" today, as this delivery has not been wired up.
  • Technical details (wrench icon, parent cards only): the execution trace. Every agent run appears as an expandable tree of "agents" (an orchestrator plus any sub-agents it spawned, such as Planning, Implementation, and Triage), each with its own turns, tool calls (plain labels like "Read card," "Create subcards," "Run command," "Notify user"), token and tool-call counts, and, expandable per call, the arguments and result exchanged. This is the closest thing to a "show me exactly what the agent did" view.

Top to bottom:

  • Project: click to jump back to the project.
  • Repo: the repository name(s) associated with the card, or "—" if none yet.
  • Status: a coloured pill matching the board's column colours. While the card is Backlog or Todo it is an interactive dropdown; once In Progress, Review, or Done, it has no dropdown, and the position is system-owned from that point on.
  • Created / Updated: relative timestamps.
  • Metrics (tokens, tool calls, duration, runs): a reserved section with a "View breakdown →" link into a per-run metrics modal. Cards do not report these numbers yet, so in practice this section does not appear.
  • Pull Requests: every pull request linked to the card: repository, PR number, title, and a state badge (open/merged/closed). While loading it shows "Loading…"; with none yet, "No PRs linked yet." Clicking a listed PR opens it in a new tab; the actual review workflow (approve, reject, merge) happens on the Pull Requests screen. This section does not appear on a subtask's detail page; only parent cards show it.
  • Delete issue: with issue:delete, at the bottom of the sidebar. It opens a confirmation ("This issue and all its history will be permanently deleted. This cannot be undone.") before removing the card for good.
On this page