chore(#2358): disable claude dynamic workflows via managed settings

This commit is contained in:
damocles 2026-07-10 17:10:48 +02:00 committed by mara
commit 342f6ab55b
2 changed files with 7 additions and 3 deletions

View file

@ -74,9 +74,12 @@ context (it won't carry our title). claude stores sessions in
`--name` writes the title into the file as a `custom-title` event, which `--name` writes the title into the file as a `custom-title` event, which
is what `--resume <title>` resolves against. We never pass bare is what `--resume <title>` resolves against. We never pass bare
`--continue` (it resumes the *latest* session in the cwd — the hijack `--continue` (it resumes the *latest* session in the cwd — the hijack
vector). Auto-compact and auto-memory are disabled via the managed vector). Auto-compact, auto-memory, and dynamic workflows (the `/workflows`
settings at `/etc/claude-code/managed-settings.json` because hyperhive feature) are disabled via the managed settings at
owns compaction — see [Compaction](#compaction) below. `/etc/claude-code/managed-settings.json`: hyperhive owns compaction
(see [Compaction](#compaction) below), and `disableWorkflows` keeps the
`/workflows` machinery from spawning sub-runs that burn usage on the
harness's autonomous turns.
**Session reset** is available via `POST /api/new-session` (or **Session reset** is available via `POST /api/new-session` (or
`/new-session` slash command). It does *not* touch the session inline — `/new-session` slash command). It does *not* touch the session inline —

View file

@ -1,6 +1,7 @@
{ {
"autoCompactEnabled": false, "autoCompactEnabled": false,
"autoMemoryEnabled": false, "autoMemoryEnabled": false,
"disableWorkflows": true,
"permissions": { "permissions": {
"deny": ["Task", "TodoWrite"] "deny": ["Task", "TodoWrite"]
} }