[BUG] Error on opening coworkers session and posting a new prompt

Status Fixed / completed
Reported on v2.1.6
Maintainer reply None cached
Activity 15 comments · opened Feb 8, 2026 · closed Aug 25, 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?

For the last 24 hours I have been getting this error on existing coworkers sessions. 'This task didn't load properly
RPC error: ensure user: user confident-fervent-rubin should already exist but does not, and recovery failed: home directory /sessions/confident-fervent-rubin does not exist: stat /sessions/confident-fervent-rubin: no such file or directory' - I have restarted the Mac, I have deleted cache files, I have deleted and re-installed Claude desktop

What Should Happen?

It should accept a new prompt without error

Error Messages/Logs

This task didn't load properly
RPC error: ensure user: user confident-fervent-rubin should already exist but does not, and recovery failed: home directory /sessions/confident-fervent-rubin does not exist: stat /sessions/confident-fervent-rubin: no such file or directory

Steps to Reproduce

Open CoWork
Click on an existing session
Type in prompt
Get Error

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.6 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

15 Comments

adamkdean · 6 months ago

I'm seeing this too. My Claude crashed (MacOS) and I had to remove vm-bundles to get it to open again but existing sessions are broken. New sessions work though!

Anakin008 · 6 months ago

same error, Windows 11, Max Plan, Claude Cowork

Vladosur · 6 months ago

Same problem here on Windows 11, Max Plan, Claude Cowork

altarapid · 6 months ago

same

athithyai · 6 months ago

Same issue
RPC error -1: failed to ensure virtiofs mount: Plan9 mount failed: bad address
win11/Claude cowork/ pro plan

bdesilva4 · 6 months ago

Having two related issues.
This task didn't load properly
failed to write length: An established connection was aborted by the software in your host machine.
AND
RPC error -1: process with name "sweet-busy-darwin" already running (id: 2c215821-66fc-4be2-afb7-c83dd656d4cc)

mrswitters · 6 months ago

I'm also getting this error with very simple prompts. No files or folders attached, no project attached, nothing that could consume context. Any ideas? I've contacted Anthropic support multiple times and they haven't responded.

Catholically · 6 months ago

RPC error -1: failed to ensure virtiofs mount: Plan9 mount failed: bad address
win11/Claude cowork/ max plan

Audible83 · 6 months ago

Yeah, i get the same. Windows 11 pro.

RPC error -1: failed to ensure virtiofs mount: Plan9 mount failed: bad address

rcbevans · 6 months ago

Same issue, claude cowork is totally busted right now. Not sure if it's after a recent update, but it worked this morning, crashed, and now no amount of reinstalling, rebooting, updating has got it back into a working state.

RPC error -1: failed to ensure virtiofs mount: Plan9 mount failed: bad address

danchiron · 6 months ago

I am having the same issue in all cowork,

leemaen · 6 months ago

Same here. Win 11. Pro Plan

RPC error -1: failed to ensure virtiofs mount: Plan9 mount failed: bad address

threedbook · 5 months ago

Same - can't get cursor cowork at all, just buggy and crashes, tried troubleshooting, reinstalling, restarting... just unusable. Back to cursor and antigravity I guess.

pixelloop · 5 months ago

I also have the same error on Windows 11, running 1.1.5368

AlexHutchings92 · 5 months ago

Same.
RPC error -1: failed to ensure virtiofs mount: Plan9 mount failed: bad address

This happens frequently and out of nowhere. No clear cause, all models, no clear solution. Cowork seems to restore itself back to working condition whenever it feels like.

Reinstall does nothing. Restarting VMWP does nothing. Obviously restarting Claude or my computer does nothing (that seems to be everyone's brilliant advice). Asking a software engineer if they've tried restarting their computer is mind boggling.