For the love of god fix bugs and write some fricken tests instead of dropping new shiny things It is absolutely wild to me you guys broke `--continue` from `-p` TWO WEEKS AGO and it is still not fixed.
--resume works fine?
Claude Code Routines
261–270 of 451 posts
Re: Claude Code Routines
#262LLMs and LLM providers are massive black boxes. I get a lot of value from them and so I can put up with that to a certain extent, but these new "products"/features that Anthropic are shipping are very unappealing to me. Not because I can't see a use-case for them, but because I have 0 trust in them: - No trust that they won't nerf the tool/model behind the feature - No trust they won't sunset the feature (the graveya…
Right you are! We aren‘t even in the real squeezing phase yet and everyone‘s already crying about plan limits and model nerfing.
Re: Claude Code Routines
#263Earlier quoted context omitted.
They can’t allow third party software because the third parties save the outputs of Claude responses and distill them into new models to compete with Claude.
This distilling sounds wonderful to me as an end user. Is there some place we can donate our chats and output?
There's https://github.com/badlogic/pi-share-hf by the creator of pi-coding-agent, to redact session data and publish on Huggingface. You can find others of the same idea for Claude Code/Codex on Github, though of varying redaction quality. Or have your LLM fork pi-share-hf to work for your preferred coding agent.
Clem Delangue (HF CEO) tweeted about this[1] and mentioned https://traces.com/ for exporting Claude sessions
Edit: It looks like HF now supports importing your agent's session directory directly[2] (I hope they're redacting PII?)
[1] https://x.com/ClementDelangue/status/2041189872556269697
Re: Claude Code Routines
#264For the love of god fix bugs and write some fricken tests instead of dropping new shiny things It is absolutely wild to me you guys broke `--continue` from `-p` TWO WEEKS AGO and it is still not fixed.
--resume works fine?
That's why I mentioned `-p`.
`--continue` and `--resume` are broken from `-p` sessions for the last 2 weeks. The use case is:
1. Do autonomous claudey thing (claude -p 'hey do this thing')
2. Do a deterministic thing
3. Reinvoke claude with `--continue`
This no longer works. I've had this workflow in GitHub actions for months and all of a sudden they broke it.
They constantly break stuff I rely on.
Skill script loading was broken for weeks a couple months ago. Hooks have been broken numerous times.
So tired of their lack of testing.
Re: Claude Code Routines
#265how did they not call this OpenClaude?
Re: Claude Code Routines
#266LLMs and LLM providers are massive black boxes. I get a lot of value from them and so I can put up with that to a certain extent, but these new "products"/features that Anthropic are shipping are very unappealing to me. Not because I can't see a use-case for them, but because I have 0 trust in them: - No trust that they won't nerf the tool/model behind the feature - No trust they won't sunset the feature (the graveya…
> Not because I can't see a use-case for them, but because I have 0 trust in them > […] > Put another way, LLM companies are trying to climb the ladder to be a platform, I have zero interest in that, I was a "dumb pipe", I want a commodity, I want a provider, not a platform. That is my sentiment precisely, and a big reason why I’ve started moving away from Claude Code in the past few weeks when I realised how much of…
> Claude Code’s "Memory" feature was the tipping point for me
My standing orders are the default MEMORY.md must be a stub directing Claude to another MEMORY.md file in the local folder, project, etc.
All memories remain with their respective projects over syncs, moves, devices, etc. The stub must state all this clearly, and nothing else.
This has worked very well.
If you give the model/memory a name, that name can be persistent and independent over "backend" model swaps.
Re: Claude Code Routines
#267Earlier quoted context omitted.
I'm the first to be tired of everyone, for every model, that says "uuuh became dumber" because I didn't believe them ... until this week! Opus is struggling worse than Sonnet those last two weeks.
My favourite was, Opus 4.6 last night (to be fair peak IST time, late afternoon my time), the first prompt with a small context: jams a copy-pasted function in between a bunch of import statements, doesn't even wire up it's own function and calls it done. Wild, I've not seen failure states like that since old Sonnet 4
Yesterday I had my biggest Opus WTF.
I asked Opus 4.6 to help me get GPU stats in btop on nixos. Opus's first approach was to use patchelf to monkey patch the btop binary. I had to redirect it to just look the nix wiki and add `nixpkgs.config.rocmSupport = true;`.
But the approach of modifying a compiled binary for a configuration issue is bizarre.
Re: Claude Code Routines
#268Earlier quoted context omitted.
> Not because I can't see a use-case for them, but because I have 0 trust in them > […] > Put another way, LLM companies are trying to climb the ladder to be a platform, I have zero interest in that, I was a "dumb pipe", I want a commodity, I want a provider, not a platform. That is my sentiment precisely, and a big reason why I’ve started moving away from Claude Code in the past few weeks when I realised how much of…
They can’t allow third party software because the third parties save the outputs of Claude responses and distill them into new models to compete with Claude.
Yeah who just goes and indiscriminately vacuums up data so they can train their products they’re going to sell with no intention of giving compensation to the very entities that made their products possible?
Re: Claude Code Routines
#269LLMs and LLM providers are massive black boxes. I get a lot of value from them and so I can put up with that to a certain extent, but these new "products"/features that Anthropic are shipping are very unappealing to me. Not because I can't see a use-case for them, but because I have 0 trust in them: - No trust that they won't nerf the tool/model behind the feature - No trust they won't sunset the feature (the graveya…
I'm glad I'm not the only one that feels this way. I've been creating a local first open source piece of software that lets me spin up different agent harnesses with different runtimes. I call it Major Tom because I wanted to be set free from the imprisonment of Claude Code after their DMCA aggression for their own leak and actions leading to lock down from open source adoption.
Don't put all your eggs in one basket has be true for me and my business for ages.
I could really use the open source community to help make this a reality so I'll release this soon hopefully to positive reception from others who want a similar path forward.
Re: Claude Code Routines
#270I am beginning to fear Claude is going to massively raise prices or at the very least severely restrict its $20/month plan. Hope it doesn’t happen but feels inevitable