[Bug] Dispatch: Cannot register Cowork agent - stuck 409 conflict on same device (DESKTOP-HOME)

Resolved 💬 3 comments Opened Apr 15, 2026 by Vampact Closed May 26, 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?

Desktop app version: Claude 1.2581.0 (MSIX)
OS: Windows 11 Pro 10.0.26200
Error: A Cowork agent is already registered on DESKTOP-HOME. Disconnect it there before registering this device. (HTTP 409 Conflict)
Request ID: req_011Ca64pboiBBMtz8PuiUtRA

Description

The Dispatch feature cannot connect because a ghost Cowork session is stuck on the server for device "DESKTOP-HOME". This IS the same computer — there is no other device to disconnect from.

What I've tried

  • Signed out and back in (multiple times)
  • Killed all Claude processes via Task Manager
  • Cleared bridge-state.json, Local Storage, IndexedDB
  • Revoked all Claude Code OAuth tokens

None of the above resolved the issue. The ghost session persists server-side.

What Should Happen?

Expected behavior

When the only registered device is the same machine attempting to reconnect, the server should allow re-registration or provide a self-serve way to clear the stuck session.

Error Messages/Logs

## Log entry
2026-04-16 03:56:14 [error] [sessions-bridge] Registration conflict (409):
A Cowork agent is already registered on DESKTOP-HOME.
Disconnect it there before registering this device.
[request-id: req_011Ca64pboiBBMtz8PuiUtRA]

Steps to Reproduce

Steps to reproduce

  1. Claude Desktop loses connection (app crash / network drop)
  2. Restart the app
  3. Attempt to connect Dispatch
  4. 409 Conflict error appears permanently

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.2581.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗