Talk runs the captain: hourly check-ins, the friends watch and owner instructions as routines in a thread, with memory and resume #11011

Owner, 2026-11-10: "i also want to close this [Claude Code] and fully start using Talk… its not a good experience. look at https://vercel.com/templates/ai/v0-clone. this is basically what i want."

Today (/talk, signed in): the newest chat is from 11-02. The thread is a wall of raw mcp__forge__merge {"repo":…,"dryRun":true} JSON lines. There is no preview, and nothing says what happened. P10 shows 0 open, but the experience is not done.

The target is a v0-style builder: chat on the left, the thing being built live on the right, and every turn a version you can go back to.

This slice: Talk replaces the Claude Code captain session. He wants to close Claude Code. What it does for him today has to run in the forge:

• Routines that post into a Talk thread, each with an editable schedule:

- the hourly forge check-in: health, releases, pillar movement, what each crew member holds, red trunk, grokbot pulls; - the friends watch: new sign-ups and child forges stuck; - the morning paper. Each posts at most 3 lines and pushes to his phone only when something needs him.

• His message in Talk is an instruction acted on right away, with the same powers the captain has here: file issues under the right pillar, assign, steer, reopen parked pulls, merge, lend credit. Anything with real money, DNS or a dark roll asks first with an Allow button.
• Memory: durable owner facts and decisions, readable and editable in Settings, loaded into every Talk session. These are the rules this session runs on today: never rm, tokens off argv, the forge is never dark without his go, and so on.
• Sessions resume where they stopped (#10457). One thread can run for days without losing context, summarising itself when it fills.
• Proof: for one full day, every check-in and every owner instruction is handled in Talk with no Claude Code session. The thread is linked in the pull.