vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

check-issue-refs: blanket-ban tracker tags in markdown too, no exceptions

Browse source
This commit is contained in:
damocles 2026-09-09 21:02:48 +02:00
commit e1e913015d
24 changed files with 81 additions and 89 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/turn-loop/claude-invocation.md
View file

@ -133,8 +133,9 @@ the reactive path only fires once claude-code has already refused a whole
turn as too long. Neither can see context growth happening _inside_ a
single long turn's own tool-calling before it returns — a turn whose tool
calls alone blow past the window hits the reactive path with no preceding
checkpoint, losing whatever wasn't already persisted (#2707, root-caused in
#3727).
checkpoint, losing whatever wasn't already persisted
(`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/2707`, root-caused in
`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/3727`).
**Safety net for that gap: claude-code's own native autocompact is on**,
via the managed settings (`"autoCompactEnabled": true`,

2
docs/turn-loop/mcp.md
View file

@ -222,7 +222,7 @@ operator-driven `hivectl choom` session — which passes neither `--tools`
nor `--allowedTools` — gets claude's built-in synchronous `Bash` tool
(inline, human-approved). That sidesteps the async `mcp__bash__run`
completion wake landing in the wrong session (the harness inbox) for a
choom-started task (#2356); `choom` is an operator (root) action, so
choom-started task (`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/2356`); `choom` is an operator (root) action, so
built-in shell there stays within the existing trust boundary. The bash MCP server
(`run` / `status` / `kill`) uses `allowedTools = ["*"]` so all
`mcp__bash__*` tools are always available regardless of tool groups.