Feature Request: `claude -c` should gracefully start a new session when no previous conversation exists
Status Open
Maintainer reply None cached
Activity 0 comments · opened Jul 18, 2026
Motivation
I often use claude -c as my default way to launch Claude, expecting it to pick up where I left off or just start fresh if there's nothing to continue. On a new machine or after clearing sessions, this workflow breaks with a hard error, forcing me to re-run without -c.
Current Behavior
claude -c errors out with "No conversation found to continue" when there are no previous sessions. This is a hard stop.
Desired Behavior
Warn and fall back to a fresh session instead of erroring:
⚠ No previous conversation found. Starting a new session.
Why
- Scripting/aliases:
alias cc="claude -c"shouldn't break on a clean state. - Fresh installs: No prior session isn't an error, it's just nothing to continue.
- Least surprise: Starting fresh is the obvious, safe fallback.