claude-code - 💡(How to fix) Fix Dispatch shows desktop online but leaves requests on read (no response on target) [1 comments, 2 participants]

TL;DR

The most likely fix involves ensuring the Claude CLI is running and properly authenticated to enable dispatched requests to execute on the online target.

Guidance

• Verify that the ~/.claude/.credentials.json file is being updated correctly after re-authentication using claude setup-token, and check the expiresAt value to ensure it's in the future.
• Confirm that the Claude CLI is running and not terminated or paused, as it seems to be required for the Desktop app to function as a dispatch target.
• Investigate the request_id req_011Ca3yfi6e8RcKio546rbRr for any specific errors or logs that might indicate why the dispatched requests are not being executed.
• Consider implementing a periodic check for the OAuth token expiration and automatic refresh to prevent similar issues in the future.

Example

No code snippet is provided as it's not explicitly supported by the issue.

Notes

The provided information suggests a potential issue with the authentication and authorization flow between the Claude Desktop app and the CLI. The fact that the Desktop app shows as "online" after workarounds but dispatched requests produce no response indicates a possible miscommunication or missing step in the request execution process.

Recommendation

Apply workaround: Ensure the Claude CLI is running and properly authenticated, as this seems to be a requirement for the Desktop app to function correctly as a dispatch target. This is chosen because the issue description implies that the CLI's presence and authentication state directly impact the functionality of the Desktop app as a dispatch target.