How a False Health Signal Hid a Never-Registered Claude Remote Session
A developer running a persistent Claude Code remote-control session discovered that all system health indicators showed green — active process, fresh auth token, passing CloudWatch alarm — yet the session had never actually registered on claude.ai/code. The root cause was a two-part silent failure: a newer CLI version added an interactive confirmation prompt that blocked registration when no TTY was present, and the --continue flag failed because no prior session existed in the directory. The startup banner, which prints before registration completes, had been mistakenly used as the health check signal, making a hung process appear healthy. Restarting the service reproduced the banner and reset the heartbeat to green, but the session remained absent from the remote list each time. The fix required switching the monitoring signal from the pre-registration banner string to the actual post-registration session URL, which only appears after a successful handshake.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in