Feature request: expose a `rename_session` tool to Claude in Code Cloud / Desktop

Resolved 💬 1 comment Opened Apr 28, 2026 by renatonapel-arch Closed May 29, 2026

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

Feature request: expose a rename_session tool to Claude in Code Cloud / Desktop

Currently the assistant cannot rename the session it's running in. The only
session-affecting tool exposed is mark_chapter, which adds a divider in
the timeline but doesn't change the title shown at the top of the page.

This blocks integrations where an external system (e.g. an internal ticket
tracker, CRM, project tool) wants to feed Claude a context prompt and have
the session adopt a deterministic name like #1007 Issue title for later
retrieval.

Workaround today: the prompt asks Claude to call mark_chapter with the
desired name, then asks the user to manually click the session title and
type it in. This works but adds a step for every session.

Proposed:

A tool rename_session(name: string) available to Claude in Code Cloud
(and ideally Desktop), that updates the session's display title.

Use cases:

  • Ticket tracker → "open Claude session for ticket #1007" button copies

a prompt; pasted prompt makes the session self-name

  • CRM → similar (lead/account ID)
  • PM tool → similar (issue key)

Why now: integrations like the above are easy to build with
navigator.clipboard.writeText() from any web app, but the rename step
is the only thing that breaks the loop. Adding the tool unblocks the
whole pattern with zero infra on either side.

Thanks!

Proposed Solution

Feature request: expose a rename_session tool to Claude in Code Cloud / Desktop

Currently the assistant cannot rename the session it's running in. The only
session-affecting tool exposed is mark_chapter, which adds a divider in
the timeline but doesn't change the title shown at the top of the page.

This blocks integrations where an external system (e.g. an internal ticket
tracker, CRM, project tool) wants to feed Claude a context prompt and have
the session adopt a deterministic name like #1007 Issue title for later
retrieval.

Workaround today: the prompt asks Claude to call mark_chapter with the
desired name, then asks the user to manually click the session title and
type it in. This works but adds a step for every session.

Proposed:

A tool rename_session(name: string) available to Claude in Code Cloud
(and ideally Desktop), that updates the session's display title.

Use cases:

  • Ticket tracker → "open Claude session for ticket #1007" button copies

a prompt; pasted prompt makes the session self-name

  • CRM → similar (lead/account ID)
  • PM tool → similar (issue key)

Why now: integrations like the above are easy to build with
navigator.clipboard.writeText() from any web app, but the rename step
is the only thing that breaks the loop. Adding the tool unblocks the
whole pattern with zero infra on either side.

Thanks!

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗