[Bug] claude --remote cloud sessions orphaned — no Desktop/mobile visibility, no repo access

[siir]

Bug Description

claude --remote creates cloud sessions that appear orphaned from the user's account. Sessions are created successfully (session IDs returned, URLs work in the browser), but they:

1. Do not appear in Claude Desktop app or iOS app — only visible in the browser when following session URLs directly
2. Cannot access the GitHub repo — despite the GitHub App being installed and configured on the org

This is a regression. claude --remote previously created cloud sessions that appeared in both Desktop and iOS, and had full repo access. The breakage started in the last few days (late February / early March 2026).

Steps to Reproduce

1. Have Claude CLI v2.1.68 installed, authenticated, with GitHub App installed on an org
2. Launch a claude --remote session:

   claude --remote "Fix the following GitHub issues in the siir/round-claw repo..."

3. Session is created and a session URL + ID is returned
4. Open Desktop app — session is not listed
5. Open iOS app — session is not listed
6. Follow the session URL in a browser — session appears, but cannot access the GitHub repo

I launched 12 parallel sessions via a batch script. All 12 exhibited the same behavior.

Environment

• CLI version: 2.1.68
• Platform: macOS (darwin)
• Desktop app: Running, authenticated, can create its own cloud sessions normally
• GitHub App: Installed and configured on the siir org
• Auth: Logged in on CLI, Desktop, iOS, and browser simultaneously

Evidence

All 12 sessions were created successfully but are invisible to Desktop/mobile:

Created remote session: Fix DNS rebinding comment in external services
View: https://claude.ai/code/session_01AcfWgP3FwpMU8JMn2cj1zD?m=0

Created remote session: Fix refresh-costs stall on unpriceable rows
View: https://claude.ai/code/session_01KgUrP4SP4cBXhuNTyhFBCJ?m=0

Created remote session: Fix inventory consume guard and add transaction support
View: https://claude.ai/code/session_01YVFkyWjjAS9f2m2PoQx7Lg?m=0

... (12 total sessions, all exhibiting the same behavior)

Launch script pattern:

claude --remote "Fix the following GitHub issues in the siir/round-claw repo. ..." &

Related Issues

• Remote Control sessions don't appear in mobile app until session URL is opened manually #30691 — sessions not appearing in Desktop/mobile (v2.1.66-2.1.68), but reported as remote-control sessions
• Remote Control session not visible in session list, cannot reconnect after leaving #28402 — remote control session does not appear in session list
• [BUG] Remote Control not available on Pro plan — requesting access #29185 / [BUG] "Remote Control environments are not available for your account." for Claude Code Pro Plan user #29449 — "Remote Control environments are not available for your account"

These are about remote-control (--remote-control), not claude --remote cloud sessions. The symptom is similar (sessions invisible to Desktop/mobile) but the trigger is different.

Expected Behavior

• Sessions created via claude --remote should appear in Desktop and iOS app session lists
• Sessions should have access to repos the GitHub App is installed on
• This is how it worked before the regression

🤖 Generated with Claude Code

[github-actions]

Found 3 possible duplicate issues:

1. Remote Control sessions don't appear in mobile app until session URL is opened manually #30691
2. Remote session fails with 'Claude GitHub app must be installed' despite app being installed #21377
3. Remote Control session not visible in session list, cannot reconnect after leaving #28402

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.