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>
988 B
988 B
id, title, theme, status, created, date_source, order
| id | title | theme | status | created | date_source | order |
|---|---|---|---|---|---|---|
| sudo-terminal-modal/a-modal-carrying-a-terminal-emulator-for | A modal carrying a terminal emulator, for anything that needs `sudo` | sudo-terminal-modal | open | 2026-08-21 | stated | 1 |
A modal carrying a terminal emulator, for anything that needs sudo. Wanted 2026-08-21.
Anywhere a command needs sudo, the modal opens with a live terminal session, the command runs
in it, and the user types his password into the terminal himself — the password goes to the pty,
never through the platform or an agent. Plumbing exists: the pty sidecar already serves ad-hoc
sessions, and xterm.js is already in the terminal panel; the new part is the modal surface and
an entry point ("run this with sudo") that other surfaces can invoke.
Needs an affordance (capabilities/affordances/) so chat agents know the mechanism exists
and reach for it instead of attempting sudo non-interactively or asking the owner to paste a
command.