[FEATURE] Incognito mode in Claude Code

[benjaminjackson]

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

When I run Claude code in --print mode, I usually don't need to refer to that conversation later.

For example, I often use it to automatically commit changes to my code.

These conversations aren't something I'll ever refer back to, BUT they end up cluttering up the conversation history when I try to find an earlier session using /resume.

Proposed Solution

I'd like to be able to run claude --print --incognito. This would prevent the conversation history from being stored in ~/.claude/projects.

Alternative Solutions

I can't think of any other way to accomplish this other than a native flag.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Example:

1. I make some changes with Claude Code.
2. I leave the session and run claude -p "/dev:commit" --incognito
3. Claude Code commits the files
4. I run claude -c
5. Claude resumes the previous session where I made the changes
6. The conversation history for the commit workflow is not stored

Additional Context

No response

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[risenowrise]

id still love that feature for tons of haiku microagents doing their work without having to script-cleanup after them!

[superjax]

I'd still prefer a proper command-line arg, but I found a workaround where you can capture the conversation id via the --output-format json argument and then clear out the conversation right away. Here is a bash wrapper in the meantime:

https://gist.github.com/superjax/5e4b9c78d42458d0c6b1d5a05aa66288

[github-actions]

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

[marcindulak]

This issue was closed incorrectly despite recent human comments. This behavior of the bot is reported at #16497. Please upvote that issue, so maybe it gets noticed.

[github-actions]

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.