[FEATURE] Feature request: expose a "rename session" tool to the agent (ccd_session_mgmt)

Open 💬 0 comments Opened Jul 8, 2026 by A-yea

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The cloud-synced session list is great for controlling multiple machines from the mobile app, but it does not indicate which machine each session belongs to. Titles are auto-generated from conversation content, so sessions from different machines look identical in the list.

I asked Claude to establish a naming convention — prefixing every session title with the machine's username, e.g. (g2950) Unity project — so I can tell my machines apart at a glance. However, Claude cannot apply it: the session management tools exposed to the agent (ccd_session_mgmt) only include list_sessions, search_session_transcripts, send_message, and archive_session. There is no rename/retitle tool, even though renaming already exists in the app UI (and is arguably lower-risk than archive_session, which is already exposed).

Proposed Solution

Add a rename_session (or set_session_title) tool to ccd_session_mgmt, accepting a session ID (or the literal "self" for the current session) and a new title string.

With that, users could set up automatic naming conventions in their CLAUDE.md (e.g. "always prefix the session title with $env:USERNAME") and the agent could enforce them without any manual steps.

Alternative Solutions

  • A user-level setting like sessionTitlePrefix that the app automatically prepends to auto-generated titles on each machine — this would solve my specific case without exposing a new agent tool.
  • Showing the origin machine (hostname) as metadata next to each session in the app's session list, so no naming convention is needed at all.
  • Current workaround: Claude generates the desired title as copyable text and I rename the session manually in the app UI — works, but defeats the point of an automated convention across many sessions and machines.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

I keep several Windows machines (home desktop, office PC, a remote standby workstation) running Claude Code desktop, and control them remotely from my phone via the cloud-synced session list. Every new session should be titled (<machine username>) <topic>, e.g. (g2950) Unity project.

Desired flow: a rule in CLAUDE.md says "on every new session, rename it with the machine-name prefix" → Claude calls rename_session("self", "(g2950) Unity project") at the start of the session → I can instantly tell my machines apart from my phone.

Today Claude can only print the suggested title and ask me to rename manually, for every single session.

Additional Context

  • Claude Code desktop on Windows 10 Pro, version 2.1.202
  • Multi-machine setup, sessions accessed remotely from mobile via cloud sync
  • This request came out of an actual conversation where Claude searched its available tools, confirmed no rename capability exists, and drafted this issue as the workaround. 🐀👨‍🍳

...
This request was actually made by my AI agent; I'm currently no different from a young chef being controlled by rats.

View original on GitHub ↗