"Why this is more than an inconvenience. For paying users who treat their sessions as intellectual property — design reasoning, prompt history, hard-won context — this is silent, unconsented destruction of user-owned data. The transcripts are the user's record of their own thinking and work; deleting them by default, silently, with no recovery, inverts the expected ownership relationship. A 30-day default that quietly discards months of accumulated reasoning is a poor default for that audience, however reasonable it is for disk hygiene in the general case."
Those users would be wise to back those files up if they consider them valuable intellectual property. If they're important enough that you'd miss them after a disk failure, then they should have been being backed up already.
>if they consider them valuable intellectual property [...]
It's hard to take any of what's written seriously, given that it's all AI generated. Did the user actually lose "valuable intellectual property", or did they tell claude to write as dire of a justification as possible?
Isn’t “Anthropic won’t fix it” a little sensational for barely month old issue with little activity(two upvotes, one of which is me), in backlog of 5k+? Agree that it’s a real issue that need fixing however
I just noticed that it’s a config option. Weird that it’s so short though, I can understand why it may be needed for users who spawn hundreds of sessions a day
Wow good timing, I’ve been working on a session hub of sorts for devs. Check it out, you can store your sessions on here. https://joe-store-frontend.onrender.com
This is clearly shown in the settings/config (or at least was last time I looked), if people are surprised by this I recommend asking claude code what settings you can tweak
The best mitigation I've found against this is training Claude to collate what it does within the project dir, specifically a CLAUDE.md vision file and .claude/changelog that documents the changes it makes. The biggest pain point though is remembering to force it to do that between sessions (man is that contextual memory unreliable sometimes).
Oh yeah - it commonly doesn't update my BACKLOG.md after shipping something. It tends to catch itself on the next set of work, but sometimes I have it clean up based on recent commits.
Except that those customers can access the traces for 30 days, and freely copy them at any point during that period? It's a usability issue at worst, not some anti-customer conspiracy.
"Why this is more than an inconvenience. For paying users who treat their sessions as intellectual property — design reasoning, prompt history, hard-won context — this is silent, unconsented destruction of user-owned data. The transcripts are the user's record of their own thinking and work; deleting them by default, silently, with no recovery, inverts the expected ownership relationship. A 30-day default that quietly discards months of accumulated reasoning is a poor default for that audience, however reasonable it is for disk hygiene in the general case."
Those users would be wise to back those files up if they consider them valuable intellectual property. If they're important enough that you'd miss them after a disk failure, then they should have been being backed up already.
>if they consider them valuable intellectual property [...]
It's hard to take any of what's written seriously, given that it's all AI generated. Did the user actually lose "valuable intellectual property", or did they tell claude to write as dire of a justification as possible?
Isn’t “Anthropic won’t fix it” a little sensational for barely month old issue with little activity(two upvotes, one of which is me), in backlog of 5k+? Agree that it’s a real issue that need fixing however
They claim that they can automate development, so their backlog should really be ~0. /hj
"fix it" here is reverting their bad change
I just noticed that it’s a config option. Weird that it’s so short though, I can understand why it may be needed for users who spawn hundreds of sessions a day
There are several third party tools which can assist with transparently aggregating and archiving sessions across projects
Ccrider is the one I use: https://github.com/neilberkman/ccrider
Session backups live outside of ~.claude so are not deleted and can be resumed.
ha ha brilliant name!
So it's a config setting you can change? What would you expect them to fix, that sounds like a feature?
There's nothing in claude code onboarding that tells you about this config setting. So most people don't discover it until it's bitten them.
Well they want the default to change. But yeah, it’s not really a bug.
It says that raising the config setting still causes things to be inappropriately deleted.
Wow good timing, I’ve been working on a session hub of sorts for devs. Check it out, you can store your sessions on here. https://joe-store-frontend.onrender.com
This is clearly shown in the settings/config (or at least was last time I looked), if people are surprised by this I recommend asking claude code what settings you can tweak
The best mitigation I've found against this is training Claude to collate what it does within the project dir, specifically a CLAUDE.md vision file and .claude/changelog that documents the changes it makes. The biggest pain point though is remembering to force it to do that between sessions (man is that contextual memory unreliable sometimes).
Oh yeah - it commonly doesn't update my BACKLOG.md after shipping something. It tends to catch itself on the next set of work, but sometimes I have it clean up based on recent commits.
I thought this was a feature that they tidied up your data
It's on your computer you can literally just make a crontab to copy them somewhere else.
Or tell claude to do it /s
idk if it's broken.
I think it's more like, "We don't want our harness to need to be able to interpret every version of our conversation format indefinitely."
i think more of a "we need to delete thinking traces off of customers devices, so our customers cant use them"
which makes anthropic on the whole a lot less trustworthy to have access to any machine
Except that those customers can access the traces for 30 days, and freely copy them at any point during that period? It's a usability issue at worst, not some anti-customer conspiracy.
"Evil Anthropic implements rolling log files."
Film at 11.
[flagged]
That Claude can't retain and reference these in the future, SQLite could do this trivially, is wild.
Who said "can't"?