Issues

What this page is for

The Issues page gives you a global view of every issue across every project — or a scoped view if you opened it from inside a specific project. Use it to see what’s open, what’s blocked, who’s doing what, and to create new issues when the chat surface isn’t enough.

Layout

The page is either a list or a board, depending on your preference. Both show:

• Title and (optional) description preview
• Status — Open, InProgress, WaitingOnDependency, PendingReview, Resolved, Closed
• Assignee — an agent or a human, with an avatar
• Links — an icon if the issue blocks or is blocked by another
• Project — which project it belongs to (when viewing globally)
• Last updated — timestamp of the last status change or comment

A filter bar lets you scope by status, assignee, project, and link type. A search box runs across titles and descriptions.

Common tasks

Create an issue

1. Click New issue from the header
2. Fill in title and description
3. Pick a project (required)
4. Optionally set an assignee, a goal to link to, and any issues this one depends on
5. Click Create

If you assign the new issue to an agent, the agent picks it up on its next heartbeat (usually within 30 seconds) and starts executing. If you assign it to a human or leave it unassigned, it waits.

Assign to a different agent or user

Open the issue detail page and click the assignee field. Pick a new assignee. The change is logged in the activity timeline. If you reassign an issue that was already running, the current agent stops where it is and the new one picks up on its next heartbeat.

Link issues together

Open the issue detail page, scroll to the Links section, and click Add link. Pick the other issue and the relationship type:

• Blocks — this issue blocks the other from starting
• Blocked by — this issue is waiting on the other to resolve
• Related to — informational only, no execution impact
• Duplicate of — this issue is a duplicate of the other

Blocks and blocked-by are enforced by the execution engine. Blocked issues transition to WaitingOnDependency and only come back to Open when the blocker reaches Resolved.

Reopen a closed issue

From the issue detail page, click Reopen. The issue moves back to InProgress (if an agent is assigned) or Open (if not), and the agent picks up where it left off on the next heartbeat.

Read the activity timeline

Every issue has an activity timeline that records every status change, tool call, comment, and link event. Scroll down on the issue detail page. This is your audit trail — when you want to know what happened and why, the timeline has it.

Statuses in order

The normal happy path: Open → InProgress → PendingReview → Resolved. See Projects, goals & issues for the full lifecycle.

Comments and attachments

Every issue has a comment thread and an attachments list. Agents write progress updates as comments. You can reply. You can upload files as attachments. Attachments are persistent and visible to anyone with access to the project.

Common pitfalls

Not writing a good description. The description is what the agent reads to decide how to execute. A vague description leads to vague work. Write it like a task ticket: what needs to happen, how to know it’s done, any constraints or preferences.

Assigning an issue before the dependencies are set up. If issue B depends on issue A, set the link up before assigning B to an agent. If you assign first and link second, the agent may start executing B before the link is enforced.

Where to go next

• Projects — the parent container
• Projects, goals & issues — the conceptual model
• Agents — pick a good assignee