Read `custom-title` entries from session JSONL so Claude Code `/rename` is reflected in the sidebar

[felipemeres]

Summary

Sessions renamed in Claude Code (via the /rename command) are not reflected in the CloudCLI sidebar. The Claude session synchronizer builds its name map only from ~/.claude/history.jsonl (which holds first-prompt-per-session entries), but /rename writes the new title into the session's own JSONL transcript instead. The rename is durable on disk, but invisible to CloudCLI — so a user juggling several parallel sessions has no way to surface their per-session labels in the UI.

Reproduce

• CloudCLI UI v1.31.5 (npm install)
• Claude Code v2.1.131
• Node v24.14.1, Ubuntu 24.04

1. Start a session in claude, send a message, then run /rename Foo.

2. grep custom-title ~/.claude/projects/<encoded-cwd>/<sessionId>.jsonl shows the rename was persisted:

   {"type":"custom-title","customTitle":"Foo","sessionId":"…"}
   {"type":"agent-name","agentName":"Foo","sessionId":"…"}

3. grep "Foo" ~/.claude/history.jsonl returns nothing — /rename does not append to history.jsonl.

4. Open CloudCLI — the session shows either the first user prompt or Untitled Claude Session. Never Foo.

Root cause

server/modules/providers/list/claude/claude-session-synchronizer.provider.ts:31:

const nameMap = await buildLookupMap(
  path.join(this.claudeHome, 'history.jsonl'),
  'sessionId',
  'display',
);

history.jsonl is a per-prompt log written by the CLI as the user types. /rename does not touch it. The actual rename lives in the session JSONL as a {"type":"custom-title", "customTitle":"…"} entry (and a redundant agent-name entry).

This is the same architectural seam called out in #731 — the synchronizer is built around history.jsonl as the only name source, and gaps appear whenever Claude Code persists a name through some other path.

Suggested fix

processSessionFile() already iterates the session JSONL. It can pick up the custom-title entry (preferring the latest one if multiple exist, since users can rename more than once) and prefer it over the history.jsonl-derived first-prompt fallback.

Suggested precedence for the displayed session name:

1. CloudCLI UI rename (sessions.custom_name in CloudCLI's SQLite) — already wins, unchanged
2. NEW: Claude Code /rename → most-recent customTitle from session JSONL
3. First user prompt from history.jsonl — current default
4. Untitled Claude Session

Why this matters

The renaming-many-tabs workflow is exactly what brings users to a session-management UI like CloudCLI in the first place — they have lots of parallel Claude Code sessions and they label them so they don't get lost. Today CloudCLI shows the same generic title for all of them regardless of how thoroughly the user has renamed in the CLI.

Happy to send a PR if useful.

[coderabbitai]

🔗 Related PRs

#275 - fix: navigate to the correct session ID when updating session state [merged]
#318 - Fix/session streamed to another chat [merged]
#413 - feat: implement session rename with SQLite storage [merged]
#451 - fix(claude): correct project encoded path [merged]
#738 - Fix codex websocket issue [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[ngophuong]

Look forward to next release to fix this soon ..

[sincerelamb]

Yes, I can reproduce this issue as well.

Environment:

OS: Windows 10
CloudCLI: v1.31.5
Provider/session: Claude Code session

Reproduction steps:

Open an existing Claude session in CloudCLI.
Rename the session in the UI, for example to NewShader.
The title at the top of the session page updates correctly.
Send a new message or refresh/sync the session list.
The sidebar title changes back to Untitled Claude Session.

Observed behavior:

The main session header still shows the renamed title.
The sidebar session list shows Untitled Claude Session.
I did not see a rename-related PUT/PATCH/POST request in DevTools Network when checking the sidebar behavior.

Expected behavior:

The sidebar should keep showing the custom title.
CloudCLI should prioritize the custom title from the session JSONL / CloudCLI custom name over history.jsonl, ai-title, or fallback Untitled Claude Session.

This makes it difficult to manage multiple sessions, because renamed sessions become indistinguishable again after new messages.

[blackmammoth]

Hey @sincerelamb, thanks for the detailed report! I tried your reproduction steps, but it's working fine on my end. Can you verify that you are on the latest main branch?

[sincerelamb]

@blackmammoth Hello, I checked my environment: CloudCLI shown in UI: v1.31.5. The issue still happens after clearing browser cache and restarting CloudCLI.

Hey @sincerelamb, thanks for the detailed report! I tried your reproduction steps, but it's working fine on my end. Can you verify that you are on the latest main branch?