<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dot.git/bin/pi-forum, branch master</title>
<subtitle>Shell, editor and terminal configuration, and the tools that go with them
</subtitle>
<id>https://git.soarez.net/sz/dot.git/atom?h=master</id>
<link rel='self' href='https://git.soarez.net/sz/dot.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/dot.git/'/>
<updated>2026-11-16T14:21:44+00:00</updated>
<entry>
<title>pi forum: let an agent mute its forums while it focuses</title>
<updated>2026-11-16T14:21:44+00:00</updated>
<author>
<name>Igor Soarez</name>
<email>igor@soarez.org</email>
</author>
<published>2026-11-16T14:21:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/dot.git/commit/?id=75aa62d5920f4adf717ae780d7032c105cceb899'/>
<id>urn:sha1:75aa62d5920f4adf717ae780d7032c105cceb899</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>pi forum: an agent stopped by a signal or crash keeps its forums</title>
<updated>2026-11-16T12:32:29+00:00</updated>
<author>
<name>Igor Soarez</name>
<email>igor@soarez.org</email>
</author>
<published>2026-11-16T12:32:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/dot.git/commit/?id=049072d5aad49d311096a7125d891f7de1738017'/>
<id>urn:sha1:049072d5aad49d311096a7125d891f7de1738017</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>pi forum: put the session name back in an agent's label</title>
<updated>2026-11-15T08:19:14+00:00</updated>
<author>
<name>Igor Soarez</name>
<email>igor@soarez.org</email>
</author>
<published>2026-11-15T08:19:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/dot.git/commit/?id=7396d213b38ace3858ce651468aade72e98144bc'/>
<id>urn:sha1:7396d213b38ace3858ce651468aade72e98144bc</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>pi-forum: list, show and follow forum posts from a terminal</title>
<updated>2026-11-12T08:20:35+00:00</updated>
<author>
<name>Igor Soarez</name>
<email>igor@soarez.org</email>
</author>
<published>2026-11-12T08:20:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/dot.git/commit/?id=5cde8b0f37321f88b7e0b18510100bf4f9b0614b'/>
<id>urn:sha1:5cde8b0f37321f88b7e0b18510100bf4f9b0614b</id>
<content type='text'>
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.
</content>
</entry>
</feed>
