Skip to content

[Bug] Buzz/Windows 11: Agents have stopped responding after the first couple messages #2450

Open

Description

@mwherman2000

Describe the bug
Agents have stopped responding after the first couple messages

Image

To Reproduce:
Steps to reproduce the behavior:

  1. Create a workspace on Buzz/Windows 11 using Claude Code
  2. Send a couple messages
  3. You get a couple responses
  4. Send a couple more message
  5. Wait several minutes ...like 10+ minutes
  6. No responses come back

Expected behavior:
I expect a response for every message

Supporting Material
See above

Environment (please complete the following information):

Image

Additional context
Add any other context that you feel is relevant about the problem here.

Activity

  1. mwherman2000 commented on Jul 23, 2026

    @mwherman2000
    Author

    I restarted Buzz the next morning and still appears to be hung

  2. mwherman2000 commented on Jul 23, 2026

    @mwherman2000
    Author

    Looks like node maybe missing or not in the path:

    �[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
    
  3. mwherman2000 commented on Jul 23, 2026

    @mwherman2000
    Author

    I think the most likely culprit is C:\Users\mwher\AppData\Roaming\npm\claude-agent-acp.cmd:

    @ECHO off
    GOTO start
    :find_dp0
    SET dp0=%~dp0
    EXIT /b
    :start
    SETLOCAL
    CALL :find_dp0
    
    IF EXIST "%dp0%\node.exe" (
      SET "_prog=%dp0%\node.exe"
    ) ELSE (
      SET "_prog=node.exe"
      SET PATHEXT=%PATHEXT:;.JS;=;%
    )
    
    endLocal & goto #_undefined_# 2>NUL || title %COMSPEC% & "%_prog%"  "%dp0%\node_modules\@agentclientprotocol\claude-agent-acp\dist\index.js" %*
    
  4. siddhartpai commented on Jul 23, 2026

    @siddhartpai

    Same issue on mac as well. But i can see this error if i open up the activity for Fizz.

    Image
  5. siddhartpai commented on Jul 23, 2026

    @siddhartpai

    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:

    • ~/.claude/settings.json contains "model": "fable".
    • ~/.claude/settings.json contains "model": "fable".
    • 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:

    1. Change the alias to the full model ID in ~/.claude/settings.json, which the SDK passes through verbatim:
      "model": "claude-fable-5"
    2. 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.)

    ✻ 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.

  6. mwherman2000 commented on Jul 24, 2026

    @mwherman2000
    Author

    My original issue is different

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions