Structured Comments

Any task, blocking, question or suggestion comment can be moved to its own job by using the Move button.

Inside a job

Blocking issues

Opening a blocking issue on a job does the following

• If not already there, job changes stage to Blocked
• Removes notifications that no longer apply like the notification to approve
• Everyone except the creator receives a persistent notification.

A blocking issue can also record a dependency on another job — type # in the issue text to choose the job being waited on and link it. When a job completes, AI agents sweep the workspace for blocking issues that link it and recommend which ones to resolve, so dependent jobs re-enter the flow without anyone having to remember them.

Questions

Similar to blocking issues, but additionally, the ‘Add Option’ button on the created question can be used to gather approvals on possible answers.

Clicking an approvable option allows voting or commenting.

An open AI-authored question interrupts a Doable or Reviewable job by moving it to Requires Input. The job’s current human assignees are its primary responders. A clear reply or option vote from one of them makes the question answerable for the AI workflow; the AI then resolves the answered question, which restores the job’s previous executable stage. Other people’s replies and votes remain visible as advisory context but do not answer or unblock the job. Reassigning the job changes who is primary.

Resolve has a separate meaning for an AI-authored question: any human Resolve delegates the choice to the AI and unblocks the job without selecting an option or implying that the current behavior should remain.

Suggestions

Suggestions can be moved to tasks and support voting for or against the suggestion. When a suggestion qualifies as assistance the job must wait on, it also moves the job to Requires Input.

Reports

An assignee creating a new report resolves all previous reports. The previous reports will still show in the resolved section of the job.

An AI implementation review names the current intent/design capsule R-code and reports only behavior omitted, changed, or added relative to that contract. When nothing differs, it says so directly instead of repeating the capsule. Only one AI review is open per job, including when separate top-level tasks have their own capsules. Revising a capsule makes its former review obsolete; the installed agent resolves its matching review before continuing affected implementation.

Additionally, using a mention in a report sends a notification that remains until the mentioned person replies or opens a comment.

Notes

Notes record decisions and context without interrupting anyone — a note sends no notification unless you @ mention someone in it.

The current intent/design capsule is a protected pinned note shown in a separate zone above the dated notes. A job capsule and independently executable task capsules have explicit target labels. Each capsule stands alone; task work does not combine it with the job capsule. Collaborators may edit the body and reply, but cannot resolve, delete, move, retype, use Show AI, make it a task, pin, or unpin the current capsule. An AI create or revision puts an inbox item in front of the current human assignees without email or Slack; explicit mentions retain their ordinary delivery behavior.

When a capsule body changes, its previous body appears shortly afterward as an ordinary unpinned note with a source label. That archive is history, not the current contract. It follows the ordinary note rules below and is not automatically supplied to an agent.

A job’s Notes tab collects the job level notes and the notes on its tasks, grouped by day with the newest day on top; a note added on a task displays under that task’s header. Add one with the Add note button or Ctrl+Alt+n.

The Show AI checkbox on a note controls whether AI agents receive it as part of the job’s context. A note that has a reply is always sent to AI, so its checkbox displays checked and locked.

Replying to your own note adds another note to the thread, and a note can be converted to a task with the Add task button.

Tasks

Opening a task prevents moving the job to Reviewable until the task is resolved. You can also move a task out of the job and into its own bug.

Grouped Tasks

Add a grouped task with the Group button and it displays underneath the task from which it was created.

At the view level

Bugs are basically tasks that are not associated with a job. Similarly in the view Notes / Discussion section questions, suggestions, and notes can be entered.

When an AI needs answer options before it can work a view-level bug, its ask_question action creates a human-owned Bugs job in that view, moves the original bug and its reply thread into the job as a task, and creates the optioned question there. Open-ended requests for facts stay as replies on the original bug.

Unlike a job note, a view level note can be resolved — resolved notes, questions, and suggestions display in the Resolved tab and can be dragged back to Open. When a workspace has more than one view, a view level comment can also be moved to a different view.