Public: anyone can read this; the crew can change it.
/talk is a chat you'd expect: streaming, history, stop, retry, attachments and tool cards, clean and fast #8752
2 earlier comments
Reviewed pull #8755 at its head: left open: Conversations: new, list, search, rename, archive; a stable URL for each; survives reload and moves between devices mid-reply. — Needs a migration; not in this slice.; Messages: streaming markdown that doesn't jump, code blocks with copy and highlighting, tables, links; copy a message; edit and resend; regenerate; a clear time and who. — Copy and who/when are done; highlighting, tables, edit and regenerate are not.; Composer: autosizing, Enter sends and Shift-Enter breaks a line, draft kept on reload, Stop mid-turn, queue or steer while it's working, paste or drop files and images, suggestions on an empty chat. — Stop, queue and attachments are not done.; The agent's work: tool calls as quiet collapsed cards with status and result, thinking collapsed, a plan or steps line, links to what it opened or changed, and Confirm and Cancel in place for writes. — Cards and Confirm/Cancel exist; thinking, the plan line and links to what changed do not.; Errors say what happened and offer Retry, never a raw message. Stick to bottom while reading the end, with a jump button if you've scrolled up; show what a turn cost and how much context is left. — Stick-to-bottom and the jump button are done; Retry and cost/context are not.; Keyboard all the way, screen reader announcements, phone layout, light and dark. Follows #8719's rules. Page budget is held by a test. — No page-budget test, and the 360px layout is unchecked.; Before and after screenshots, and a cold reader can start a chat in 10 seconds. — No screenshots or cold-start check..
Left open after pull #8755 landed: 7 unticked items remain (Conversations: new, list, search, rename, archive; a stable URL for each; survives reload and moves between devices mid-reply.; Messages: streaming markdown that doesn't jump, code blocks with copy and highlighting, tables, links; copy a message; edit and resend; regenerate; a clear time and who.; Composer: autosizing, Enter sends and Shift-Enter breaks a line, draft kept on reload, Stop mid-turn, queue or steer while it's working, paste or drop files and images, suggestions on an empty chat.; …). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Split by the planner, one small pull each, from what pull #8755's review left: conversation list, new, rename, archive and stable URLs #8814, then search #8823; a reply surviving reload and other devices #8815; highlighted code and tables #8816; edit, regenerate and Retry #8817; Stop #8818, then queue or steer #8819; attachments #8820; thinking, the steps line and links #8821; cost and context #8822; the phone, keyboard and screen-reader pass, the byte budget and looks #8824 (after #8812 makes signed-in looks possible).
The owner, 2026-11-02: "the ai-elements components might be what we want to pull from for this. there is much prior art to building this and i want it done right and cleanly with all the features a user would expect to have in a chatbot". Depends on #8751 for reliability.
Vercel's AI Elements (https://elements.ai-sdk.dev/docs) is React on shadcn. The forge is server rendered, so port its anatomy and behaviour to our components and a small script; keep
src/web/pages/talk.ts's server-drawn history and streaming. Read it, the AI SDK UI docs, and two or three leading chat apps first, and put a short feature table on the first pull: have, adding, not adding, each with why. Don't add React for this unless that table proves it's needed, and say so if it does. Check the licence before copying any code.Done when, in small pulls: