### Summary Renaming a Claude Code session is not reflected in the Android app. The app keeps showing the title the session had when it first synced. ### Steps to reproduce 1. Start a session on the desktop (local session, `sessionId: local_...`, `isRemote: false`). 2. Send a first message, then rename the session (session-management `set_session_title`, `session_id: "self"`). 3. `get_session` confirms the new title on the desktop side. 4. Open the same session in the Android app. ### Expect

Session title changes don't propagate to the Android app

Status Open

Maintainer reply None cached

Activity 0 comments · opened Sep 7, 2026

Summary

Renaming a Claude Code session is not reflected in the Android app. The app keeps showing the title the session had when it first synced.

Steps to reproduce

Start a session on the desktop (local session, sessionId: local_..., isRemote: false).
Send a first message, then rename the session (session-management set_session_title, session_id: "self").
get_session confirms the new title on the desktop side.
Open the same session in the Android app.

Expected

The app shows the current session title.

Actual

The app shows the title from the initial sync. Force-stopping the app and reloading does not update it. The desktop side is correct throughout.

Impact

Sessions are typically auto-renamed after the first message, because the title is derived from it. On Android this means essentially every session shows a stale or empty title.

Environment

Windows 11 Pro 26200, Claude Code desktop app
Android app, force-stop + reload attempted

View original on GitHub ↗