claude-code - 💡(How to fix) Fix [Bug] Dispatch: Cannot register Cowork agent - stuck 409 conflict on same device (DESKTOP-HOME) [1 comments, 2 participants]

Error: A Cowork agent is already registered on DESKTOP-HOME. Disconnect it there before registering this device. (HTTP 409 Conflict)

Error Messages/Logs

2026-04-16 03:56:14 [error] [sessions-bridge] Registration conflict (409): 4. 409 Conflict error appears permanently

TL;DR

The issue can be resolved by finding a way to clear the stuck Cowork session on the server-side for the device "DESKTOP-HOME", possibly through a self-serve mechanism or direct server intervention.

Guidance

• Investigate server-side session management to understand how stuck sessions are handled and if there's an API or interface to manually clear them.
• Check if there are any server logs or monitoring tools that can provide more insight into the stuck session and why it persists despite client-side attempts to clear it.
• Consider reaching out to the server administration or support team to report the issue and request assistance in clearing the stuck session, as the error message suggests a server-side resolution.
• Review the application's documentation and support resources for any guidance on handling registration conflicts or stuck sessions.

Example

No specific code example can be provided without more details on the server-side implementation, but a potential approach might involve using an API call to clear the session, if such an API exists:

DELETE /sessions/{sessionId}

However, this is speculative and would depend on the actual server-side API design.

Notes

The exact solution depends on the specifics of the server-side implementation and its management interfaces. Without direct access to server documentation or support, the best course of action is to seek assistance from the server administration team.

Recommendation

Apply workaround: Given the lack of information on how to directly clear the stuck session through the client, the best immediate action is to seek server-side assistance to resolve the conflict. This approach is necessary because the issue is identified as a regression, suggesting that the expected behavior of allowing re-registration or providing a self-serve way to clear stuck sessions is not currently functioning as intended.