claude-code - 💡(How to fix) Fix [Bug] Remote-control bridge session returns not_found error, session not registered on server [1 comments, 2 participants]

Verify via curl: curl https://api.anthropic.com/v1/claude-code/bridge/sessions/session_01CcrTtsFbisnKXY7WEZdsQX → returns {"type":"error","error":{"type":"not_found_error","message":"Not Found"}} claude remote-control --verbose provides no additional output beyond the timeout error claude remote-control --name "zamtel" fails with Error: timeout of 15000ms exceeded

TL;DR

The issue may be related to the bridge session not being registered on the server side, and a potential fix could involve investigating the API request to register the session.

Guidance

• Verify the bridgeSessionId in the local ~/.claude/sessions/*.json file is correctly generated and matches the expected format.
• Check the network connection and API endpoint https://api.anthropic.com/v1/claude-code/bridge/sessions/ for any issues or errors that might prevent the session from being registered.
• Investigate the claude remote-control command's behavior when run with the --verbose flag to see if it provides any additional information about the registration process.
• Review the authentication method and ensure that the claude.ai OAuth authentication is correctly configured and authorized.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The issue may be related to a server-side problem or a configuration issue with the Claude Code version 2.1.109. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate alternative methods to register the bridge session, such as manually sending the API request to register the session, to see if it resolves the issue. This is because the issue seems to be related to the session registration process, and an alternative approach might help bypass the problem.