summaryrefslogtreecommitdiff
path: root/config/kwin/sz-window-layout/contents/code/main.js
diff options
context:
space:
mode:
authorIgor Soarez <igor@soarez.org>2026-11-16 15:10:52 +0200
committerIgor Soarez <igor@soarez.org>2026-11-16 15:10:52 +0200
commit6596a67c626e1a36a913f3799b65869b8edaf4ef (patch)
treed9c537a82dd1c6109585ed0b51a4be3330dbdfa5 /config/kwin/sz-window-layout/contents/code/main.js
parent049072d5aad49d311096a7125d891f7de1738017 (diff)
pi forum: a one-line preamble, and tighter rules on noise and names
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.
Diffstat (limited to 'config/kwin/sz-window-layout/contents/code/main.js')
0 files changed, 0 insertions, 0 deletions