How to Delete Claude Code Sessions Properly

Claude Code users are running into a frustrating housekeeping problem: there is no straightforward way to delete old conversation sessions, and they keep piling up. As the AI-powered coding assistant gains traction among developers worldwide, this session management gap is becoming a significant pain point that Anthropic has yet to address with a built-in solution.

The issue is deceptively simple. Every time you start a new conversation in Claude Code, the tool creates a session record. Over weeks of heavy use, these sessions accumulate — sometimes numbering in the hundreds — with no obvious way to clean them up.

Key Takeaways

• The /clear command in Claude Code does not delete sessions — it creates a new one
• Session data is stored in the .claude directory on your local machine
• Folder names inside .claude do not match session names, making manual deletion risky
• There is currently no built-in command to delete or archive old sessions
• Developers have found workarounds, but none are officially supported
• Anthropic has not publicly addressed this session management limitation

The /clear Command Does Not Do What You Think

Many developers assume the /clear command is the answer to session cleanup. It is not. When you type /clear in Claude Code, the tool does not remove the current session from storage. Instead, it simply starts a fresh conversation context while leaving the old session data intact on your filesystem.

This behavior is similar to how clearing your terminal with clear or Ctrl+L does not actually delete your command history. The visual slate is wiped clean, but the underlying data persists. For developers who run dozens of Claude Code sessions daily — debugging, refactoring, writing tests — this means the .claude directory quietly balloons in size over time.

Unlike tools such as GitHub Copilot Chat in VS Code, which manages conversation history through a GUI with clear delete options, Claude Code operates primarily in the terminal. This terminal-first design philosophy offers speed and flexibility but currently lacks basic session lifecycle management.

Navigating the .claude Directory Manually

The only current workaround involves manually navigating to the .claude directory and deleting session folders. On most systems, this directory is located in your home folder:

• macOS/Linux: ~/.claude/
• Windows: C:\Users\YourName\.claude\

Inside this directory, you will find folders corresponding to individual sessions. Here is where the real frustration begins: the folder names are not human-readable. Instead of being named after your session topics or timestamps in a recognizable format, they use internal identifiers — typically long hash strings or UUIDs.

This means if you want to delete a specific old session about, say, a React component refactor from last Tuesday, you have no easy way to identify which folder contains that conversation. Deleting the wrong folder could remove a session you still need.

Developers have reported several strategies for working around this limitation:

• Sort folders by modification date using ls -lt to identify the oldest sessions
• Use du -sh * to find the largest session folders consuming the most disk space
• Open individual session files to peek at content before deleting
• Write a simple bash script to purge sessions older than a certain number of days
• Back up the entire .claude directory before any manual cleanup

A Simple Cleanup Script for Power Users

For developers comfortable with the command line, a basic cleanup approach involves using standard Unix tools to manage the session directory. Here is a general strategy that several community members have adopted:

First, inspect what you are working with by checking the total size of your .claude directory. On macOS or Linux, running du -sh ~/.claude/ reveals how much disk space sessions are consuming. Some heavy users report this directory growing to several hundred megabytes or even gigabytes over months of use.

To remove sessions older than 30 days, developers have used variations of the find command targeting the .claude directory with -mtime +30 flags. However, proceed with extreme caution — this approach is not officially documented, and Anthropic could change the directory structure in any update.

It is also worth noting that Claude Code stores more than just conversation logs in the .claude directory. Configuration files, project-specific settings through CLAUDE.md files, and other metadata may reside there. Blindly deleting everything is a recipe for broken configurations.

How This Compares to Other AI Coding Tools

Session management is a solved problem in most competing AI coding assistants. Here is how other tools handle it:

• GitHub Copilot Chat: Offers a sidebar with full conversation history, individual delete buttons, and automatic cleanup options
• Cursor: Provides a conversation panel where users can rename, delete, or search through past sessions
• Cody by Sourcegraph: Includes conversation management with clear archive and delete functionality
• Amazon Q Developer: Manages sessions through the IDE interface with standard CRUD operations
• Windsurf by Codeium: Features a chat history panel with delete and export capabilities

Claude Code's terminal-native approach is intentionally minimalist, and many developers appreciate that philosophy. But basic session hygiene should not require filesystem surgery. The gap is particularly notable given that Anthropic positions Claude Code as a premium tool, currently priced through the Claude Pro subscription at $20/month or the Max plan at $100-200/month.

Why Session Management Actually Matters

This is not just an aesthetic issue. Accumulated sessions create several practical problems for developers:

Disk space consumption is the most obvious concern. Each session stores the full conversation history, including code snippets, file references, and Claude's responses. For developers working on large codebases, individual sessions can be substantial.

Performance is another factor. While Claude Code does not appear to load all historical sessions into memory, a bloated .claude directory could theoretically impact startup times or file-watching processes, particularly on systems with slower storage.

There is also a security consideration. Old sessions may contain sensitive information — API keys accidentally pasted into conversations, proprietary code discussions, or infrastructure details. Without easy deletion, this data lingers on disk longer than necessary, potentially violating organizational security policies.

Finally, for developers who use Claude Code across multiple projects, the inability to organize or filter sessions by project makes it harder to revisit useful past conversations. A session from a Python backend project gets mixed in with React frontend work and DevOps scripting, creating a cluttered and unsearchable history.

What Anthropic Should Build Next

The developer community has been vocal about wanting proper session management in Claude Code. Based on forum discussions and community feedback, the most requested features include:

• A /sessions command to list all sessions with dates and preview text
• A /delete command to remove specific sessions by ID or date range
• A /prune command to automatically clean up sessions older than a configurable threshold
• Session naming or tagging support for better organization
• Project-based session grouping to keep conversations organized by codebase
• An --export flag to save important sessions before cleanup

Anthopic has been shipping Claude Code updates at a rapid pace throughout 2025, adding features like background agents, GitHub integration, and custom slash commands. Session management seems like a natural addition to the roadmap, though the company has not publicly committed to a timeline.

Looking Ahead: Expect Improvements Soon

Claude Code is still evolving rapidly. Anthropic released it as a beta product and has been iterating based on developer feedback. The session management gap, while frustrating, is the kind of quality-of-life issue that typically gets addressed as a tool matures.

In the meantime, developers should adopt a regular cleanup routine. Set a weekly reminder to check your .claude directory size. Consider writing a simple maintenance script tailored to your workflow. And always back up before deleting — until Anthropic provides official tools, manual cleanup carries inherent risk.

The broader lesson here applies beyond Claude Code. As AI coding assistants become integral to daily development workflows, the unglamorous details of data management, session hygiene, and local storage become critical user experience factors. The tool that solves the 'boring' problems best often wins the long-term adoption battle.

For now, Claude Code remains one of the most powerful terminal-based AI coding assistants available. Its session management just needs to catch up with the rest of the experience.