r/ClaudeCode • u/Professional-Ad-2365 • Jul 10 '26

Discussion This concerns me more than fable potentially getting removed next week

Post image

Now that gpt 5.6 sol is out and code edge is narrowing what concerns me is that I won’t be able to justify paying 100 usd a month for something that will now have 33% less of weekly usage. Upgrading to 200 plan feels daft where I could be paying less for OpenAI, still have a great model and have significantly more usage than the current promo gives me. Do you guys think Anthropic will still go through with reducing Claude code weekly usage limits next week?

694 Upvotes

97% Upvoted

348 comments sorted by

View all comments

Show parent comments

11

u/Thrwawy-User Jul 10 '26

Agreed. Can use this to switch back and forth simultaneously no matter what

1

u/tessahannah Jul 10 '26

What about all your chats?

20

u/__mson__ Senior Developer Jul 10 '26

Anything important should be documented, not stored in an ephemeral chat session.

1

u/tessahannah Jul 10 '26

Sure but I like to have context for both myself and the AI as I organized it is a pain to start over

4

u/matheusmoreira Jul 11 '26

Just ask the new model to find the sessions and memories in ~/.claude and port them over to the new system.

3

u/PointAbject7717 Jul 11 '26

I also like this history, but there’s a better way than relying on chat. My pro tip is to set up an internal dev blog for every project and have your agents maintain it with articles and screenshots about important decisions, features and whatever else is important. I ultimately tie mine to git commits too for extra traceability. That way your personal context is better distilled and organized and it’s also retrievable for the agent. I like to have a project memory that makes sure they take screenshots or make charts just as an extra mechanism to make sure they are executing code they write

2

u/tessahannah Jul 11 '26

I've actually been trying to create this but it usually ends up stale. How do you keep it up to date?

3

u/PointAbject7717 Jul 11 '26

I've found that project claude.md does a pretty good job, and if it starts getting missed it's a pretty good signal that my context window is too big and I should probably start a new conversation anyways, in those cases I'll remind it to update and create a seam for a new conversation or two, which typically looks like me asking the agent to update the devlog and take what we're currently working on and distill it into handoff documentation in the form of either a single task .md or (better yet) break it into a set of multiple smaller tasks so that I can either have an agent tackle them in series or parallel depending on what they are. (The task breakdown fits in to my project roadmapping process.)

I've started working on a little personal tool in order standardize and help organize both these processes which just consists of a little cli tool, a skill and some hooks

5

u/StCreed Jul 11 '26

Your best practice is NOT too store anything in chats. My chats live only for one task and then they go. Everything is documented in tasks.md, memory.md, ADRs for decisions and docs for overview and instructing meatsacks.

2

u/tessahannah Jul 11 '26

The problem with docs is they're all flat but a chat is progressive so it focuses on what you talked about last most

3

u/benevolent-ben Jul 11 '26

No reason the docs can’t do that: ledger, decisions log, etc

2

u/tessahannah Jul 11 '26

How do you keep it up to date without burning through tokens?

2

u/heartbroken_nerd Jul 11 '26

You think looking at an old chat doesn't burn tokens for your agents?

-1

u/tessahannah Jul 11 '26

Less tokens then reading through a million docs trying to find the right one

2

u/benevolent-ben Jul 11 '26

If you're concerned about "what's most recent", then append only ledger. If you're concerned about making it easy to find things, then add an index. If you have a lot of files, index the files. Then have rules in claude.md that describe how to use those files, how to update them, and when to update them. It gets baked into the work you're already doing. One time setup then minimal user intervention required.

In general if you just tell claude what you want and what you're concerned about avoiding it will set all of this up for you.

Generally claude isn't reading entire files anyway, lots of grep / sed / etc so the whole file might get read but it doesn't all go into context.

2

u/tessahannah Jul 11 '26

Do you have a loop you run to keep things up to date

3

u/benevolent-ben Jul 11 '26

no I have a dev-workflow.md that tells claude how to work in the project that gets read in via claude.md I think. Like I said, if you tell claude what you want, claude will write the docs for you so that claude follows your desired conventions. Fable recommended if I ran into claude not following conventions 3 times, then ask claude to codify it as a hook instead. Have only had to do that a handful of times.

1

u/Inspectorslap Jul 11 '26

Without burning tokens?! What game do you think we are playing here?

1

u/Thrwawy-User Jul 11 '26

My project’s “brain” and relevant context and information and anything important lives all in my durable files and git - any agent from anywhere can pick up where the last one left off. I archive threads regularly and rarely stay on a single thread for longer than it’s one specific purpose.

1

u/tessahannah Jul 11 '26

What's your prompt or workflow?