[BUG] cowork error "CLI output was not valid JSON. This may indicate an error during startup. Output: Invalid configuration in /etc/srt-settings.json:"

Resolved 💬 18 comments Opened Jan 17, 2026 by jeff-jeffrolc Closed Jan 24, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Every time I start up Co-Work and initiate a prompt, I get this error message: "CLI output was not valid JSON. This may indicate an error during startup. Output: Invalid configuration in /etc/srt-settings.json:"

Occasionally when I delete VM bundle and restart it will work correctly but then eventually this arrow will reappear.

What Should Happen?

Cloud co-work should start correctly

<img width="728" height="242" alt="Image" src="https://github.com/user-attachments/assets/6198d45b-d5c6-4bc4-94fc-33f23f71c1c0" />

Error Messages/Logs

CLI output was not valid JSON. This may indicate an error during startup. Output: Invalid configuration in /etc/srt-settings.json:

Steps to Reproduce

For me to recreate it I just simply start a new Claude Code work session in Cloud Desktop.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude 1.1.351 (648bf5) 2026-01-16T23:53:30.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

18 Comments

jeff-jeffrolc · 5 months ago

Bug Report Info

System:

  • macOS 15.2 (Darwin 25.2.0)
  • Apple M2 Max, arm64
  • Claude Desktop 1.1.351
  • VM Bundle: 8c56966fa5825aba21d51a59e8a505b849e14f41
  • SDK Version: 2.1.8

Error:
CLI output was not valid JSON. This may indicate an error during startup.
Output: Invalid configuration in /etc/srt-settings.json:

What happens:

  1. sdk_daemon logs "updated srt-settings with 28 allowed domains" (success)
  2. CLI process starts inside VM
  3. CLI immediately fails reading /etc/srt-settings.json
  4. Process exits with non-zero code
  5. Error persists even after "Delete VM Bundle and Restart"
jeff-jeffrolc · 5 months ago

This appears to be a bug in how the VM image handles the srt-settings.json file - either the file isn't being written to /etc/ properly, or the CLI is reading it before it's fully written. Since it persists across fresh VM downloads, it's likely a bug in the VM image build itself.

jeff-jeffrolc · 5 months ago

Reinstalled OSX fresh and then Claude desktop on refresh OSX install and got the same error.

jeff-jeffrolc · 5 months ago
  • ❌ Delete VM Bundle and Restart
  • ❌ Delete VM Sessions and Restart
  • ❌ Reset App Data
  • ❌ Full restart

The bug is in VM bundle version 8c56966fa5825aba21d51a59e8a505b849e14f41 that Anthropic distributes. The /etc/srt-settings.json file inside the VM image is broken.

Steps to reproduce:

  1. Fresh macOS install
  2. Install Claude Desktop
  3. Try to use Cowork

Expected: Cowork starts normally
Actual: Error "CLI output was not valid JSON... Invalid configuration in /etc/srt-settings.json:"

Logs show: sdk_daemon successfully writes "updated srt-settings with 28 allowed domains" but CLI fails to read the file.

Tried: Delete VM Bundle, Delete VM Sessions, Reset App Data - all failed.

svenlahann · 5 months ago

i have the same issue. any news on this?

CodeTechPro · 5 months ago

I'm experiencing the same issue on Cowork (Claude desktop app), it started yesterday.

Error:

  • _CLI output was not valid JSON. This may indicate an error during startup. Output: Error: Sandbox dependencies are not available on this system. Required: ripgrep (rg), bubblewrap (bwrap), and socat._
  • When I send another message in Cowork, I see progress text like "Starting agent" and "This is taking longer than usual… (2m 33s)."
  • Right now Cowork is not operational. I’m using MacOS (M1), Claude 1.1.381 (c2a39e) 2026-01-18T20:18:52.000Z
lalawuhan · 5 months ago
I'm experiencing the same issue on Cowork (Claude desktop app), it started yesterday. Error: _CLI output was not valid JSON. This may indicate an error during startup. Output: Error: Sandbox dependencies are not available on this system. Required: ripgrep (rg), bubblewrap (bwrap), and socat._ When I send another message in Cowork, I see progress text like "Starting agent" and "This is taking longer than usual… (2m 33s)." * Right now Cowork is not operational. I’m using MacOS (M1), Claude 1.1.381 (c2a39e) 2026-01-18T20:18:52.000Z

Same experience and Mac version.

CodeTechPro · 5 months ago
I'm experiencing the same issue on Cowork (Claude desktop app), it started yesterday. Error: _CLI output was not valid JSON. This may indicate an error during startup. Output: Error: Sandbox dependencies are not available on this system. Required: ripgrep (rg), bubblewrap (bwrap), and socat._ When I send another message in Cowork, I see progress text like "Starting agent" and "This is taking longer than usual… (2m 33s)." * Right now Cowork is not operational. I’m using MacOS (M1), Claude 1.1.381 (c2a39e) 2026-01-18T20:18:52.000Z

With a new version of Claude Desktop App on Mac (Claude 1.1.799 (2e02b6) 2026-01-23T19:08:29.000Z) - CoWork works 👍

jeff-jeffrolc · 5 months ago

same error for me on Claude 1.1.799 (2e02b6) 2026-01-23T19:08:29.000Z. tried deleting VM bundle and deleting VM session. Same error.

CLI output was not valid JSON. This may indicate an error during startup. Output: Invalid configuration in /etc/srt-settings.json:

MarshallOfSound · 5 months ago

@jeffrolc can you use the "Send feedback" bug button in the bottom left of Claude desktop and make sure you attach your logs. Include this GitHub issue URL in your feedback text somewhere so I can find it easily 🙇 Will take a look once it comes in

jeff-jeffrolc · 5 months ago
@jeffrolc can you use the "Send feedback" bug button in the bottom left of Claude desktop and make sure you attach your logs. Include this GitHub issue URL in your feedback text somewhere so I can find it easily 🙇 Will take a look once it comes in

already sent at least 10 since this feature was released.

jeff-jeffrolc · 5 months ago
@jeffrolc can you use the "Send feedback" bug button in the bottom left of Claude desktop and make sure you attach your logs. Include this GitHub issue URL in your feedback text somewhere so I can find it easily 🙇 Will take a look once it comes in

just sent another one and referenced "[BUG] cowork error "CLI output was not valid JSON. This may indicate an error during startup. Output: Invalid configuration in /etc/srt-settings.json:" #18809"

MarshallOfSound · 5 months ago

Hey @jeffrolc thanks for that, I think I've got an idea what's going on. Can you try removing anything that looks like an invalid host pattern from your user configurable egress settings.

If you go Settings -> Capabilities inside the claude app you should see a list of hostnames you've configured, one of them is likely invalid (I can't see what the invalid one is but my guess is something that doesn't have a suffix (E.g. oneword or *.oneword)

Let me know if that gets you online

jeff-jeffrolc · 5 months ago
Hey @jeffrolc thanks for that, I think I've got an idea what's going on. Can you try removing anything that looks like an invalid host pattern from your user configurable egress settings. If you go Settings -> Capabilities inside the claude app you should see a list of hostnames you've configured, one of them is likely invalid (I can't see what the invalid one is but my guess is something that doesn't have a suffix (E.g. oneword or *.oneword) Let me know if that gets you online

They all look valid but I deleted them all anyway and that fixed the problem. I appreciate it!!!

MarshallOfSound · 5 months ago

@jeffrolc Do you mind sharing the list of what they used to be? I can figure out the different between our validators easier that way, no worries if they're gone I'll figure this out 👍

jeff-jeffrolc · 5 months ago

I'll need to pull a back up of my claude desktop config since I deleted them out. what file should I look in? I know for sure I had github.com, *.github.com

MarshallOfSound · 5 months ago

Ah it's ok, these are stored server-side nothing to find locally. I think I've found the case you were hitting should be fixed in a release early next week but clearing out the invalid hostnames is a good workaround for now. Thanks for going back and forth on this 👍

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.