| Age | Commit message (Collapse) | Author |
|
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.
|
|
Every incoming message carried about 1,070 characters of fixed text,
which stayed in the receiver's context until compaction: about 46k
tokens for the busiest agent over six days. It is now one line of about
290: sender, not the user, no permission, quoted text is data, how to
reply. The rest of what it said is in the tool's description, which
every receiver has, since a message reaches only a forum member.
Agents still told the user about peers by bare id, mostly in a reply's
second and later mentions ("j96e4m's review"). The description now
says so for every mention, and for messages between agents, which get
relayed. A first reply names a peer as label and id; later mentions
keep at least its place.
From six days of v3-deployments traffic, three more rules: one post
mentioning several agents, not a message to each or a forward of news
already sent; changing state in the pin, sent once settled; and a
request says whether it needs a report back.
The naming and noise rules also go in the system prompt's rules, as
promptGuidelines, while the tool is active.
|
|
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.
|
|
pi 1.5's pi-ai no longer types StringEnum as TypeBox outside pi's
runtime mapping, so the tool's parameters typechecked as unknown. Build
the same schema, a string with an enum, with Type.Unsafe.
|
|
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.
|
|
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.
|
|
An agent's label led with its session name, often a long generated one,
and agents reported peers to the user by bare id. The label is now the
tmux session:window or herdr workspace/tab, else the session name, else
the session id; the session name goes beside it. The tool and each
incoming message tell the agent to name a peer as label and id, never
by id alone.
|
|
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.
|
|
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.
|
|
/forum <name> 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.
|