You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Buzz/Windows 11: Agents have stopped responding after the first couple messages #2450
�[2m2026-07-23T09:53:10.721727Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m15
'"node"' is not recognized as an internal or external command,
operable program or batch file.
�[2m2026-07-23T09:53:10.823248Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m16
'"node"' is not recognized as an internal or external command,
operable program or batch file.
�[2m2026-07-23T09:53:10.961382Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m17
'"node"' is not recognized as an internal or external command,
operable program or batch file.
�[2m2026-07-23T09:53:11.053146Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m18
'"node"' is not recognized as an internal or external command,
operable program or batch file.
�[2m2026-07-23T09:53:11.144040Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m19
'"node"' is not recognized as an internal or external command,
operable program or batch file.
�[2m2026-07-23T09:53:11.223014Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m20
'"node"' is not recognized as an internal or external command,
operable program or batch file.
�[2m2026-07-23T09:53:11.301552Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m21
'"node"' is not recognized as an internal or external command,
operable program or batch file.
�[2m2026-07-23T09:53:11.378510Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m22
'"node"' is not recognized as an internal or external command,
operable program or batch file.
�[2m2026-07-23T09:53:11.451203Z�[0m �[31mERROR�[0m �[2mbuzz_acp�[0m�[2m:�[0m agent initialize failed: Agent process exited unexpectedly �[3magent�[0m�[2m=�[0m23
Buzz spawns its agents through the bundled @agentclientprotocol/claude-agent-acp v0.60.0 (with its own pinned copy of @anthropic-ai/claude-agent-sdk under ~/Library/Application Support/Buzz/node-tools/). That SDK reads your global settings.json, and
the model setting there overrides the model Buzz configured for the agent — the logs even show configured_model=haiku while the error complains about fable.
The bundled SDK version doesn't recognize the short alias fable (it's newer than that SDK's alias table), so every turn fails with "model (fable) may not exist".
Your interactive claude CLI (2.1.218) knows the alias, which is why you only see this inside Buzz.
Fix — either of these:
Change the alias to the full model ID in ~/.claude/settings.json, which the SDK passes through verbatim:
"model": "claude-fable-5"
Or remove the model line from settings.json entirely — then Buzz's per-agent model choice (haiku, in the current config) actually takes effect.
Option 1 is what I'd do since it keeps Fable as your CLI default and fixes Buzz at the same time. Want me to make that edit? (Note: if the bundled SDK is old enough that its API auth path also lacks Fable access, updating Buzz / the claude-agent-acp
package to a current version is the longer-term fix.)
⏺ Removed the "model": "fable" line from ~/.claude/settings.json.
Now the Buzz-spawned agents will use the model Buzz itself configures per agent (currently haiku, per its logs) instead of being overridden by the global setting. Restart the agents in Buzz Desktop (or just send them a new message so a fresh session
spawns) and the "fable may not exist" error should be gone.
Two side effects to be aware of: your interactive claude CLI no longer defaults to Fable — pick it per-session with /model or claude --model fable if you want it back. And if you later want the Buzz agents on something stronger than haiku, set the model
in each agent's config in Buzz rather than in the global settings file.
Activity
mwherman2000 commentedon Jul 23, 2026
I restarted Buzz the next morning and still appears to be hung
mwherman2000 commentedon Jul 23, 2026
Looks like
nodemaybe missing or not in the path:mwherman2000 commentedon Jul 23, 2026
I think the most likely culprit is
C:\Users\mwher\AppData\Roaming\npm\claude-agent-acp.cmd:siddhartpai commentedon Jul 23, 2026
Same issue on mac as well. But i can see this error if i open up the activity for Fizz.
siddhartpai commentedon Jul 23, 2026
I got it fixed using claude:
The error isn't coming from Buzz's own agent config — it's coming from your global Claude settings.
What's happening:
the model setting there overrides the model Buzz configured for the agent — the logs even show configured_model=haiku while the error complains about fable.
Your interactive claude CLI (2.1.218) knows the alias, which is why you only see this inside Buzz.
Fix — either of these:
"model": "claude-fable-5"
Option 1 is what I'd do since it keeps Fable as your CLI default and fixes Buzz at the same time. Want me to make that edit? (Note: if the bundled SDK is old enough that its API auth path also lacks Fable access, updating Buzz / the claude-agent-acp
package to a current version is the longer-term fix.)
✻ Sautéed for 1m 22s
❯ yes, let's remove it entirely.
Read 1 file
⏺ Update(~/.claude/settings.json)
⎿ Removed 1 line
1 {
2 - "model": "fable",
2 "hooks": {
3 "Notification": [
4 {
⏺ Removed the "model": "fable" line from ~/.claude/settings.json.
Now the Buzz-spawned agents will use the model Buzz itself configures per agent (currently haiku, per its logs) instead of being overridden by the global setting. Restart the agents in Buzz Desktop (or just send them a new message so a fresh session
spawns) and the "fable may not exist" error should be gone.
Two side effects to be aware of: your interactive claude CLI no longer defaults to Fable — pick it per-session with /model or claude --model fable if you want it back. And if you later want the Buzz agents on something stronger than haiku, set the model
in each agent's config in Buzz rather than in the global settings file.
mwherman2000 commentedon Jul 24, 2026
My original issue is different