Forge file hand-off · the plan
The agent hands the reader a document, and it opens here: the client's own viewer, on every surface the client runs. The sheet is one wide centred page; prose runs its width while code and tables take its content width.
A press on a target's + comments on that exact source line, the line first in its captured context - so a revision can re-find the thread by it.
name which document this is
named at the top, and the address follows
The ask, and the answer
- The hand-off arrives as the dock's ask - Open or Not now - and Open lands here, at the document's resolved path.
- The answer is approve or send feedback: feedback means revise the document and hand it off again, and keep handing it off until approval; a bare done is not an answer.
- The parked call waits until one is chosen: a reader who presses neither leaves it parked, and nothing on the page releases it.
Approval is the one signal to proceed; feedback is never read as it.
A fence takes the chat's own code panel:
[documents] max_size_mib = 10
| surface | the PDF rides |
|---|---|
| desktop app | WKWebView's own viewer (measured) |
| a browser | its own viewer (Chromium measured) |
| the phone | pdf.js, in the page |
The document sits on the app as one centred page on a desk, its scroller wearing the theme's bar, corner included, so no white block shows at the bottom-right.
the address belongs in this paragraph
moved it above; the anchor did not survive the rewrite
cannot be placed in this version of the document
line 42 is past this version's 21 lines
state the 10 MiB default here