claude-code - 💡(How to fix) Fix [BUG] Cowork: Session init fails to mount scheduled task config folder outside project mount after macOS Desktop upgrade [5 comments, 3 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#54744Fetched 2026-04-30 06:37:14
View on GitHub
Comments
5
Participants
3
Timeline
11
Reactions
0
Author
Timeline (top)
commented ×5labeled ×4cross-referenced ×2

Error Message

RPC error: failed to mount /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note as .scheduled/llm-wiki-weekly-note: source path is not accessible: /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note: stat /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note: operation not permitted

Root Cause

After upgrading Claude Desktop on macOS, initializing any Cowork project session fails with a VirtioFS mount error. The error appears to occur because Cowork attempts to mount the scheduled task config folder as part of session init, even though that folder is outside the project's mount point and unrelated to the current prompt.

Code Example

RPC error: failed to mount /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note as .scheduled/llm-wiki-weekly-note: source path is not accessible: /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note: stat /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note: operation not permitted
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

After upgrading Claude Desktop on macOS, initializing any Cowork project session fails with a VirtioFS mount error. The error appears to occur because Cowork attempts to mount the scheduled task config folder as part of session init, even though that folder is outside the project's mount point and unrelated to the current prompt.

Setup:

  • Project mount point: /Users/myusername/proj/llm-wiki
  • Scheduled task config (managed by Cowork, not user-configurable): /Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note/SKILL.md
  • These paths are entirely separate; the scheduled task config is outside the project folder

What Should Happen?

Cowork session initializes successfully. The scheduled task config folder should not require a separate VirtioFS mount at session init, particularly when it is outside the active project mount and the current prompt is unrelated to the scheduled task.

Error Messages/Logs

RPC error: failed to mount /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note as .scheduled/llm-wiki-weekly-note: source path is not accessible: /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note: stat /mnt/.virtiofs-root/shared/Users/myusername/Documents/Claude/Scheduled/llm-wiki-weekly-note: operation not permitted

Steps to Reproduce

  1. Have a Cowork project configured with a scheduled task
  2. Upgrade Claude Desktop on macOS
  3. Attempt to initialize a session in the Cowork project
  4. Session init fails immediately with the above RPC error

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.5354.0 (9a9e3d) 2026-04-29T01:14:34.000Z (Claude Desktop for Mac)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can likely be fixed by modifying Cowork to exclude the scheduled task config folder from VirtioFS mounting when it's outside the project mount point.

Guidance

  • Verify that the scheduled task config folder is indeed outside the project mount point and not required for the current prompt.
  • Check the Cowork configuration to see if there's an option to exclude certain folders from VirtioFS mounting.
  • Consider modifying the Cowork code to add a check for the scheduled task config folder's location before attempting to mount it.
  • Test the session initialization with a different project or prompt to see if the issue is specific to this particular setup.

Example

No code snippet is provided as the issue does not contain enough information about the Cowork codebase.

Notes

The issue seems to be a regression introduced in a recent version of Claude Desktop, and the exact cause may require further investigation into the Cowork code and its interaction with VirtioFS.

Recommendation

Apply a workaround by modifying the Cowork configuration or code to exclude the scheduled task config folder from VirtioFS mounting when it's outside the project mount point, as this is likely to resolve the issue without requiring an upgrade to a fixed version.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Cowork: Session init fails to mount scheduled task config folder outside project mount after macOS Desktop upgrade [5 comments, 3 participants]