Skip to main content
The Inbox is where agent-proposed documentation waits for your decision. When a tracked commit changes something your docs describe, or an agent sweep finds an undocumented area, the resulting drafts land here — you accept or reject each one, then ship everything you accepted in a single step. You stay in control: nothing an agent proposes reaches your docs without a human decision.

​
Layout

The Inbox has three panes:

Requests

One request per commit or agent sweep — “Commit abc1234” or “N suggested docs” — each showing its origin and review progress.

Files

Every proposed doc in the request, with Accepted/Rejected tags, per-row accept/reject buttons, and batch actions.

Detail

The selected proposal — why it exists, and exactly what it changes.
Requests come from two origins, and each row says which: User commit — a commit on a tracked branch touched something your docs describe — or Agent sweep — the Coverage Auditor proposed docs with no commit involved.

​
Understanding a proposal

The detail pane leads with a provenance card that explains why the doc was proposed — for example, “Commit abc1234 changed Flow Discount_Approval, which this doc describes” or “The agent’s coverage sweep found ApexClass InvoiceService undocumented”. You never have to guess where a draft came from. New docs are tagged New document; updates are marked Required update or Suggested. Below it, a Preview/Changes toggle shows the proposal two ways:
  • Preview — rendered markdown, best for brand-new docs.
  • Changes — a diff against the current doc, best for updates.
Diagrams render live in the preview, so a proposed Mermaid or Excalidraw change is judged as a picture, not a wall of syntax. See Diagrams.

​
Triage

Work through a request with the keyboard: Accepting or rejecting auto-advances to the next undecided file, so a batch of ten proposals takes seconds. Every decision offers Undo, so a slip of the finger costs nothing. Batch actions sit at the bottom of the file list when you want to move faster:
  • Accept all / Reject all
  • Create PR with the accepted files — open the pull request immediately
  • Open as a change request instead — polish the drafts in LivingContext first

​
Shipping accepted files

When every file has a decision, the reading pane becomes a summary — Queue clear — with a Ship accepted files action. It rolls all accepted docs into one unit for your workflow:
  • A pull request in your docs repository, if you review in GitHub or GitLab.
  • A change request, if you want to refine the drafts in LivingContext before merging.
Shipped requests link straight to the resulting PR or CR, so you can follow the work to the finish.
Shipping as a CR is the right choice when a draft is close but not perfect — you can refine it with the doc agent before it merges, instead of rejecting it outright.

​
Where proposals come from

  • Tracked commits — branches you track are swept automatically, and each relevant commit produces a request. See Commits.
  • Agent sweeps — the Coverage Auditor proposes brand-new docs for undocumented areas of your Salesforce org.
  • Drifted API specs — when your org’s API surface changes, updated OpenAPI specs are proposed rather than overwritten. See API reference.
The Inbox is the single front door for agent output. If an agent generated it, you’ll find it — and decide on it — here. An empty Inbox greets you with Inbox zero and pointers to review a commit or head back Home.