dingger.git/ROADMAP.md, branch master

show what pi agents cost today, this week and this month, counting forked replies once

2026-11-01T08:22:01+00:00

mark forgotten drafts in pi agents' input boxes, and keep them across a crash or restore

2026-10-30T16:59:43+00:00

reload pi agents on an old extension: versioned extension, control socket, menu item and reload-agents

2026-10-30T15:27:21+00:00

roadmap: cost, extension version, conversation search, uncommitted work, drafts

2026-10-30T14:31:03+00:00

roadmap: park 'say what happened' with its mockup's design

2026-10-30T13:15:36+00:00

roadmap: ideas beyond the current list

2026-10-29T17:47:56+00:00

docs: mark as unread does not work from inside claude code

2026-10-27T12:20:08+00:00

roadmap: the extended-keys warning is gone

2026-10-27T10:15:11+00:00

roadmap: pi's status reports, dialogs, cancelled and failed runs, extended-keys

2026-10-25T04:43:25+00:00

items from pi 1.0.4 to 1.4.0 worth using, and from testing pi 1.4. preview in agent search moves last.

raise the terminal window that holds the tmux client

2026-10-23T16:11:23+00:00

a jump (any click, a shortcut, search) activated the terminal app, which raised whichever window was used last. now: - the client: the named one (a status-line click), else one already on a session holding the agent's window (several terminal windows can show one session; it shows the agent without switching, and keeps its own session in a session group), else any; the focused one first, then the one used last (its last input or focus). - Ghostty (1.3+, scriptable by terminal id, not by tty): dingger learns which terminal holds each client when it gains focus. tmux's client-focus-in hook runs `dingger terminal focused`, which asks Ghostty for its focused terminal and records it in @dingger_terminal_, but only if the client is still focused once Ghostty answered (a fast switch must not pair the wrong terminal); a terminal holds one client, so an older pairing with it is dropped. `focus` raises the exact terminal (window, tab, split) through `tmux run-shell`: Apple Events from the tmux server count as Ghostty's own, so no permission prompt. a terminal that is gone is forgotten and the app activated, as without a pairing. - in a hook, #{client_name} can be another client (the previous event's); the snippet's hook uses #{hook_client}. e2e step 20: two nested clients on one session, focused by typing focus reports into their outer panes, a fake osascript as Ghostty, a fake open (tests never activate a real app); it loads the snippet's own hook line. each rule has a negative control that fails.