**Feature Description** Add /new command to start a fresh session in the same terminal tab ## Feature Request ### Problem Currently there's no way to start a new Claude Code session from within an active session. The options are: - `/clear` — resets context but stays in the same session - Exit and re-run `claude` — works but is clunky in the CLI - `--resume` picker — for resuming old sessions, not starting fresh ### Proposed Solution Add a `/new` slash command that closes the current session

[Feature Request] Add `/new` command to start fresh session in same terminal

Status Fixed / completed

Reported on v2.1.185

Maintainer reply None cached

Activity 3 comments · opened Jul 1, 2026 · closed Jul 2, 2026

Feature Description
Add /new command to start a fresh session in the same terminal tab

Feature Request

Problem

Currently there's no way to start a new Claude Code session from within an
active session. The options are:

/clear — resets context but stays in the same session
Exit and re-run claude — works but is clunky in the CLI
--resume picker — for resuming old sessions, not starting fresh

Proposed Solution

Add a /new slash command that closes the current session and starts a
fresh one in the same terminal tab (equivalent to exec claude but
accessible as a first-class command).

Expected Behavior

/new ends the current session
A new Claude Code session starts immediately in the same terminal tab
No context or history carried over (truly fresh session)

Environment Info

Platform: darwin
Terminal: ghostty
Version: 2.1.185
Feedback ID: b500d57d-6ecd-411b-827c-50ca9c2f4031

View original on GitHub ↗

3 Comments

github-actions[bot] · 3 months ago

Found 2 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

shivaprasadrb · 3 months ago

Duplicate

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.