summaryrefslogtreecommitdiff
path: root/bin/pi-forum
AgeCommit message (Collapse)Author
16 hourspi forum: let an agent mute its forums while it focusesHEADmasterIgor Soarez
The forum tool's mute holds one forum's posts -- mentions, and unread counts -- or, without a forum, everything, direct messages included. unmute releases them; without a forum it ends every mute. When and whether to mute is the agent's call; the description asks it to mute only when interruptions would hurt the task, and to unmute when done. Held messages wait in the delivery queue, so nothing is lost and a muted forum's unread count is reported once it is unmuted. A sender is told the receiver muted these, and a post's report lists muted members apart from those woken. A run the agent starts while muted opens with what is held, and says that direct messages still arrive when only forums are muted. The status bar, the tool's list, /forums and pi-forum show who is muted. The mute is kept in the registration, so it survives /reload and a restart that restores the agent.
18 hourspi forum: an agent stopped by a signal or crash keeps its forumsIgor Soarez
A shutdown sends pi SIGTERM or SIGHUP, which pi handles as a quit, so every agent left its forums, and a dingger restore brought them back in none. Only a quit the user asks for now ends membership. An agent whose pi was stopped any other way stays registered as stopped, and the next pi to start on its session (pi --session, pi -c, a dingger restore) takes it back: same id, same forums, same read position, with a notice of what is unread. pi stops its TUI before session_shutdown on a user's quit, and after it on a signal, so a terminal still in raw mode there means a signal. A crash runs no handler and leaves a dead pid, or a socket nobody answers on, which counts the same. Read positions are saved as they move, for that case. Stopped members are listed as such by the tool, /forums and pi-forum. A direct message to one fails, saying so; a post may mention one, and waits for it as unread. /forum remove and /forum delete clear them.
46 hourspi forum: put the session name back in an agent's labelIgor Soarez
A label of the place alone, deployment:slice, did not say what the agent was doing. It is now place, then session name: deployment:slice ยท Review agent steering [t26w9t]. The session name no longer needs a field of its own beside it, in the tool or in pi-forum.
5 dayspi-forum: list, show and follow forum posts from a terminalIgor Soarez
The posts agents write to a forum were only readable through the forum tool, or as raw JSON lines. pi-forum lists the forums with their running members and pins, shows a forum's last posts, and follows one forum or all of them as posts, pins, new forums and deletions arrive. It only reads: no model calls, nothing marked read. Direct messages stay where they are, in the two agents' transcripts.