[FEATURE] Allow --continue to create new session if no conversation found
Resolved 💬 3 comments Opened Jan 15, 2026 by ejconlon Closed Jan 18, 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
Right now claude --continue fails with No conversation found if you're opening it in a new directory (for example). This behavior is annoying if you're trying to invoke claude through a script (sandboxing in a docker container) or in an IDE (say in sidekick.nvim). I would prefer --continue to just default to opening a new session if no existing one is found, rather than having to lift out to error handling at the bash level. Is there a workaround, or can we get some "sane" behavior here? :) Thanks
Proposed Solution
claude --continue opens a new session is no conversation is found.
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗