dot.git, branch master

pi compact-tools: let the forum tool draw its own rows

2026-11-06T11:58:14+00:00

Compacted, a forum send showed only its name; its own renderer shows the message, folded to 10 lines.

pi forum: give a fresh session its notice with the first run

2026-11-06T11:58:14+00:00

Appended to a session with no conversation yet -- a new pi, or just after /new -- the join notice sat ahead of the system message pi records at the first run, and pi then sent that message without its content: the provider refused every request with a 400. Queue it for the next turn instead, which pi places after the system message.

pi forum: fold long messages in the transcript, whole on expand

2026-11-06T11:58:14+00:00

A message of up to 4000 characters printed in full in both panes; show its first 10 lines, or 1000 characters, and how much more there is, as pi does for tool output. The model still gets the whole text.

pi forum: let agents the user puts in a forum find and message each other

2026-11-04T13:28:11+00:00

/forum puts this pi in a forum; its members can list each other, post to it (waking only those mentioned), read its history, set its pin, and send each other direct messages, delivered the way alarm.ts delivers alarms. Only the user adds an agent; any pane can remove one. Forums and their posts live in ~/.pi/forum until /forum delete; membership lasts as long as the pi process.

yubikey-git: three keys, one per YubiKey; any one of them will do

2026-11-02T11:09:27+00:00

pi alarm: keep pending alarms across /reload

2026-10-30T16:42:18+00:00

/reload dropped every pending alarm and stopped its when_done command, without a word. An agent that had ended its turn to wait for one was never woken -- nor a pi-goal goal_wait counting on it. The old copy of the extension now leaves what is pending on globalThis instead: each alarm as plain data, the due queue, the next id, and a when_done command's ChildProcess with its own listeners removed. The copy pi loads next arms fresh timers from each alarm's absolute time, listens on the command again (one that exited meanwhile still holds its status), and resumes polling PIDs. Nothing crosses that would reach the old, stale pi or ctx. A handoff from another session or another HANDOFF_VERSION is refused and its commands stopped, with a notice. If nothing takes it within 30s -- the file failed to load, or was removed -- the old copy stops its commands. Quitting, /new, /resume and /fork still drop everything.

pi: generate mcp.json from ~/.config/pi/mcp.d fragments

2026-10-29T21:40:43+00:00

pi reads user-level MCP servers from one file, and a private layer linked that file to the same copy on every host -- so every host got a server only one machine could run. Build it the way models.json is built, from fragments another layer or one machine drops in mcp.d; this repo ships none, and with none the file is left absent. pi-models.py becomes pi-merge.py, which takes the key to merge and an optional base file, and serves both.

sz-final-review-loop: wait with a wake armed, not blocked in sz-wait-for

2026-10-27T09:36:43+00:00

The loop's agents blocked in a foreground sz-wait-for because nothing could bring an agent back from a background one. Both harnesses now can: pi's alarm fires when a when_done command exits, and Claude Code starts a new turn when a run_in_background Bash task exits (checked on 2.1.310). So an agent arms sz-wait-for as a wake and ends its turn: no context resent every 30 minutes to re-arm, the human can talk to it while it waits, and "arm, then signal" becomes literal. The foreground wait stays for a harness with neither. The invariant is unchanged in substance: never idle, where idle now means the other side's turn with no wake armed. sz-wait-for stays the watcher, for its settle window. pi-subagent: §5 says how to be woken in Claude Code too.

pi alarm: fire when a command exits or when processes exit

2026-10-27T09:12:21+00:00

when_done runs a command (bash -c, in pi's cwd, output to a log file) and fires when it exits, with its exit status; cancelling the alarm or ending the session stops it. when_exits polls PIDs already running and fires once all are gone. Either takes an optional deadline, 24 hours by default, at which the alarm fires anyway and a still-running command is stopped. A process exiting is a signal any condition can be turned into -- gh run watch, sz-wait-for, an until-curl loop -- so the agent can start something long, end its turn and be woken, instead of blocking on it. The delivery path is the existing one, unchanged. pi-subagent: §5 sets an alarm on the runs' PIDs instead of waiting.

tmux: advertise OSC 8 hyperlinks so pi and other TUIs link under tmux

2026-10-27T09:07:27+00:00