Skip to main content
This is preview documentation. The official release is not yet available.
Inbox brings together work updates, approvals and result reviews that concern you. Start with items that need a decision, then read informational updates. Handle feedback related to your console Issues here. Applications receive execution feedback through SSE and status APIs; work that requires human review still follows its acceptance policy.

Interface tour

Inbox review request with its linked issue

Current console UI with fixed demonstration data.

Select a notification in the message list, then read the linked issue and its result on the right. Reading a notification does not complete the review; inspect the deliverable before using the review actions.

Find actionable items

Open WORK → Inbox. Status filters include Needs attention, Needs action, Unread, All messages and Archived. Unread tracks reading; Needs action tracks unresolved decisions. Reading a message does not complete its work. Select a message to see its Issue or approval details. Use Open issue for the full record. If the list is empty, check filters, your account and scope before concluding that execution generated no events.

Review a deliverable

  1. Open a review request and confirm the Issue being reviewed.
  2. Compare the result and attachments with Acceptance criteria. Inspect child results when present.
  3. Select Accept result when the criteria are met, and confirm that the Issue becomes Done.
  4. Otherwise select Request changes, describe the missing work and expected outcome, then select Send review.
Requesting changes returns the Issue to In progress and records feedback. It does not start another execution automatically. Previewing a child Issue does not change the Issue addressed by this review. Resolving a comment thread is also separate from acceptance. If the work changed while you were reading, select Refresh review and inspect the current result before deciding. Your decision about an older result is not silently applied to a newer version.

Decide an approval

Review the requester, target operation, reason and linked work. Approve or reject the current request and add an explanation when useful. This can resume or fail a waiting execution; it is separate from deciding whether a final deliverable meets its acceptance criteria. Interactive tool confirmation in Chat belongs to that conversation and runtime. Do not assume that every such prompt also becomes an Inbox approval.

Organize notifications

Archive informational messages after reading them. Archive cannot replace a decision for a Needs action item. Archived messages remain available, and archiving does not delete their Issues or executions. For access failures, contact the scope or work owner. Administrative identity is not a substitute for authorization to private work. Next: Automations · Accounts and permissions. Practice with the engineering case: inspect the final commit, actual tests, GitHub review, and CI before accepting delivery. Service acceptance and GitHub approval remain separate records.