From 7584260842f7e5d7ac7afe377ee66bc1deca7946 Mon Sep 17 00:00:00 2001 From: Brooklyn Nicholson Date: Fri, 28 Aug 2026 12:02:23 -0500 Subject: [PATCH] docs(bots): name the room budget as the seam the limits PRs hook MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit GROUP_CHAT_MAX_ROUNDS and its four siblings carry over at the values plugin.js shipped, so no rebase inherits a behavior change on top of a rewrite. Making them configurable is live contributor work — #92213 for per-room limits, #96842 for config plus a token budget — and both want the same single seam, so say so where the constants are instead of adding a config hook this PR has no consumer for. --- apps/desktop/src/plugins/hermes-bots/group-chat.ts | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/apps/desktop/src/plugins/hermes-bots/group-chat.ts b/apps/desktop/src/plugins/hermes-bots/group-chat.ts index 5faa02afcd..9949c57824 100644 --- a/apps/desktop/src/plugins/hermes-bots/group-chat.ts +++ b/apps/desktop/src/plugins/hermes-bots/group-chat.ts @@ -1197,6 +1197,14 @@ export function setGroupChatSyncDisposed(disposed: boolean) { groupChatSyncDisposed = disposed } +// ── one room's budget ──────────────────────────────────────────────────────── +// Every ceiling a single user send can spend, in one block on purpose: making +// them configurable (per room, or model-aware from config.yaml) is live +// contributor work — #92213 (per-room limits) and #96842 (config + token +// budget) — and both need exactly one seam to hook. Carried over at the same +// values the old plugin.js shipped so neither rebase inherits a behavior +// change on top of a rewrite; deciding the shape of the override belongs to +// those PRs, not to a design-system pass. export const GROUP_CHAT_MAX_ROUNDS = 3 // #94478 review: continuation rounds are bounded independently of the message cap so a pathological mention chain can't consume the room's whole budget on handoffs.