Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Cowork: Projects silently fail to register on Linux after folder creation [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48421•Fetched 2026-04-16 07:00:37
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
CallumPoseidonCallumPoseidon
Participants
CallumPoseidonCallumPoseidon
Timeline (top)
labeled ×3

Error Message

The folder creation succeeds (logged as [info]), but the project never appears in the UI. No error is logged — the failure is silent. The rapid-fire duplicate creation confirms the app thinks each attempt failed. The trust check passes (isFolderTrusted: /home/user/Documents/Claude -> true) but the project still doesn't register. The bug appears to be in the step after folder creation — the project metadata/registration step fails silently in the renderer/client layer with no logged error.

Code Example

[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides
[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides (1)
[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides (2)
[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides (3)
[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides (4)
RAW_BUFFERClick to expand / collapse

Bug Description

On Linux (Ubuntu), Cowork's project creation silently fails. The Spaces API successfully creates the project folder on disk, but the project never registers in the UI. Cowork then reports "no projects" despite the folders existing.

Environment

  • OS: Ubuntu (Linux, case-sensitive filesystem)
  • Claude Desktop version: 2.1.64
  • Cowork mode: enabled

Steps to Reproduce

  1. Open Cowork mode
  2. Try to create a new project (e.g. "slides")
  3. The folder is created at ~/Documents/Claude/Projects/slides
  4. Cowork immediately reports failure / no projects exist
  5. Rapid duplicate folders are created (slides (1), slides (2), etc.) as it retries

What Happens

From ~/.config/Claude/logs/main.log:

[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides
[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides (1)
[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides (2)
[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides (3)
[Spaces API] createSpaceFolder: created /home/user/Documents/Claude/Projects/slides (4)

The folder creation succeeds (logged as [info]), but the project never appears in the UI. No error is logged — the failure is silent. The rapid-fire duplicate creation confirms the app thinks each attempt failed.

Additional Context

There was also an initial case-sensitivity mismatch: the Spaces API hardcodes ~/Documents/Claude/Projects/ (capital C) while claude_desktop_config.json had the trusted folder set to ~/Documents/claude (lowercase). On Linux these are different paths. Even after correcting this (renaming to capital Claude, updating config, symlinks, restarting), project creation still silently fails.

The trust check passes (isFolderTrusted: /home/user/Documents/Claude -> true) but the project still doesn't register. The bug appears to be in the step after folder creation — the project metadata/registration step fails silently in the renderer/client layer with no logged error.

Expected Behavior

Projects should be created and visible in the Cowork UI after folder creation succeeds.

extent analysis

TL;DR

The most likely fix is to investigate and resolve the issue with project metadata registration in the renderer/client layer, which is failing silently after successful folder creation.

Guidance

  • Verify that the claude_desktop_config.json file is correctly configured and the trusted folder path matches the actual folder path on the system.
  • Check the renderer/client layer code for any potential issues with project metadata registration, such as incorrect file paths or permissions.
  • Investigate the possibility of a timing issue, where the project metadata registration is happening before the folder creation is fully complete, causing the registration to fail.
  • Review the main.log file for any other potential clues or errors that may be related to the issue.

Example

No code snippet is provided as the issue is more related to configuration and potential timing issues rather than a specific code problem.

Notes

The issue seems to be specific to the Linux environment and the Cowork mode, and the fact that the folder creation succeeds but the project metadata registration fails silently suggests a complex issue that requires further investigation.

Recommendation

Apply workaround: Investigate and resolve the project metadata registration issue in the renderer/client layer, as it is the most likely cause of the problem. This may involve debugging the code, checking file paths and permissions, and ensuring that the registration process is happening correctly after folder creation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#authentication issue#prompt issue#agent setup#task chaining

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING