claude-code - 💡(How to fix) Fix [FEATURE] Add ability to delete individual sessions from claude.ai/code web UI [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47758Fetched 2026-04-15 06:43:04
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×3closed ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

Currently, there is no way to delete individual Claude Code sessions from the web UI at claude.ai/code. When I use /clear or delete local session history through Claude Code CLI, those sessions remain visible and accessible on the web at claude.ai/code. This is a privacy and organization concern — I cannot manage or clean up my cloud-stored session history without contacting Anthropic support directly.

<img width="926" height="797" alt="Image" src="https://github.com/user-attachments/assets/c7bfd02b-bd82-48d7-aa11-9161b5b2cd1d" />

Proposed Solution

Add a delete button (or trash icon) next to each session listed on the claude.ai/code sessions page. Ideally:

  1. A per-session delete option visible on hover or via a "..." menu
  2. A confirmation prompt before deletion to prevent accidental removal
  3. Optionally, a "Delete all sessions" bulk action

The experience should mirror how other tools (e.g., ChatGPT, Gemini) allow users to delete individual conversation history entries.

Alternative Solutions

  • Contacting Anthropic support to request manual deletion — not scalable or user-friendly for routine session management
  • Using account-level data deletion — too broad, removes everything rather than specific sessions
  • Local /clear command — only removes local history, does not affect cloud-stored sessions at claude.ai/code

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

  1. I finish working on a client project and want to remove that session from my cloud history for privacy
  2. I go to claude.ai/code and find the session
  3. Currently there is no delete button — I am stuck with it permanently in my session list
  4. With this feature, I could click delete on that specific session and confirm removal
  5. This would give users control over their own data without needing to contact support

Additional Context

The local CLI command /clear does not sync with the web — this creates a confusing disconnect where users believe they've deleted their history but it remains visible on the web. A delete option on claude.ai/code would close this gap.

extent analysis

TL;DR

Implementing a delete button next to each session on the claude.ai/code sessions page would allow users to manage their cloud-stored session history directly.

Guidance

  • Add a per-session delete option visible on hover or via a "..." menu to provide users with a straightforward way to remove individual sessions.
  • Include a confirmation prompt before deletion to prevent accidental removal and ensure users intentionally delete sessions.
  • Consider adding a "Delete all sessions" bulk action for users who want to clear their entire session history at once.
  • Ensure the delete functionality syncs with the local CLI command /clear to maintain consistency between the web and local interfaces.

Example

No specific code example can be provided without more context on the implementation details, but the solution should involve adding a delete button or icon to the session list UI and implementing the necessary backend logic to handle session deletion.

Notes

The proposed solution should be designed with user experience and privacy in mind, ensuring that users have control over their data without needing to contact support. The implementation should also consider the potential impact on user productivity and the importance of maintaining a clean and organized session history.

Recommendation

Apply the proposed solution of adding a delete button next to each session, as it directly addresses the user's need for managing their cloud-stored session history and aligns with the privacy and organization concerns mentioned.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING