Decide on the task page

Open the task page#

Every approval card links the task page (Open review). Sign in if asked. The page’s first line says what you can do:

• You’re the task owner. Answer the plan’s decisions, comment, and press Approve or Request changes.
• You can read and comment on this task. You are in the task’s channel and can use its project. Comment, reply and press Suggest this on a decision option. Only owners decide.
• You don’t have access to this task. Also what a link to a task that does not exist says.

Answer the plan’s decisions#

Each decision shows its options with AgentX’s recommendation already picked. Pick another option to change the answer. The bar at the bottom counts the decisions you have not looked at yet; press it to jump to the next one.

You do not have to answer every decision: any you leave keep AgentX’s answer. Teammates’ suggestions show under each decision, for example “Priya and Sam suggest: Above”. The Approve and Request changes buttons name the document they act on, such as “Approve coding plan v1”.

Comment and reply#

Press Comment under a claim, a decision, a check or the whole document, and Reply under a comment. Comments are plain text and can be edited or deleted until they are sent with a decision.

When a new version arrives, each comment stays on the same claim, decision or check if it is still there, marked “from v1”; otherwise it moves under “Removed claims”. While open, the page checks for new comments and versions every 20 seconds and offers Show it.

Approve or request changes#

Both buttons open a short summary before anything is sent: your answers that differ from AgentX’s, the decisions left to AgentX, and the open comments to send (all ticked; untick any to keep for later). You can add a note of up to 500 characters.

• Approve and start coding (or Approve and continue for requirements and design) moves the task on. Comments sent with it are answered by the next document.
• Request changes needs at least one comment or a note. AgentX writes the next version and answers each comment “Done:” or “Not changed because:”.

Your answers and comments go to the next step as part of the plan. Comments are passed on as teammates’ quoted words, never as instructions that override your answers. Nothing is coded until the owner approves.

Slack and the page stay in step#

A decision on the page edits the Slack card the same way a button press does, for example “Approved by @Maya · 1 answer changed · 2 comments included”. Approve in Slack uses AgentX’s answers and includes the page’s open comments (up to 25, oldest first). Request changes in Slack sends no comments.

Exactly one decision is recorded however many places it is pressed: the second place says “Already approved by …” and keeps what you typed. A teammate who comments triggers at most one Slack message every 10 minutes, without the comment text.

Ask AgentX about a comment#

Tick Ask AgentX to reply to this comment when you post. AgentX replies under it from what it knows about the task, marked “AgentX (AI) · answering” and the asker’s name. It cannot change code, choose answers or decide.

This works only on tasks started in Slack. If no answer comes within 10 minutes, the comment says “AgentX couldn’t answer this one.” An answer to a comment edited or deleted in the meantime is not shown.

Limits#

Phones and no JavaScript#

The page is built for Slack’s in-app browser: nothing scrolls sideways, buttons are large enough to tap and the summary opens full screen. Without JavaScript the page still shows the plan, every comment and AgentX’s answers; the buttons that need JavaScript stay hidden. Unsent answers and comment text survive a refresh, but not closing the tab or the end of the sign-in.