pastilhasandClaude Fable 5
6071ded175
TODO.md had reached 1050 lines and 72 open items across 28 sections, read mostly on a phone. It is now a directory: todo/<theme>/<item>.md, one card per file, with frontmatter carrying id, status, created date and order, and the prose body copied across verbatim. TODO.md becomes a generated index (bun run todo:index). Dates: where an item's prose stated one it is used; otherwise its old section's; otherwise 2026-08-20, floored at the day before the split rather than invented. date_source records which. Shaped for a two-way Kanban board, filed as todo/tooling — a card is a file, id is the identity, frontmatter is the machine's half and the body is the owner's. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
15 lines
770 B
Markdown
15 lines
770 B
Markdown
---
|
|
theme: agent-delivery
|
|
heading: "Speaking into a session from the backend"
|
|
kind: theme
|
|
---
|
|
|
|
**Correction, 2026-08-21: the door exists, and three entries in this file said it did not.** The claim
|
|
that `pushTurn` has exactly one caller (the chat websocket) is **stale**. `api/chat/nudger.ts:102` calls
|
|
`startClaudeTurn({ ws: null, … })` — a turn started server-side, with no browser attached, into a live
|
|
session. Whoever is watching the chat sees it arrive the same way they would see a turn typed in another
|
|
tab. `startNudger()` is wired at `server.tsx:182` and ticks once a minute against a `nudges` table.
|
|
|
|
So **both** "missing" pieces are built: a recurring trigger, and a way to put a prompt into a running
|
|
session. What remains is narrower, and worth doing.
|