Earlier quoted context omitted.
I'm in Claude Code 30+ hr/wk and always have a at least three tabs of CC agents open in my terminal. Agree with the other comments: pretty much running vanilla everything and only the Playwright MCP (IMO way better than the native chrome integration) and ccstatusline (for fun). Subagents can be as simple as saying "do X task(s) with subagent(s)". Skills are just self @-ing markdown files. Two of the most important th…
I also specifically instruct Claude how to use a globally git ignored scratch folder “tmp” in each repo. Curious what your approach is
Show HN: Stop Claude Code from forgetting everything
111–120 of 241 posts
Re: Show HN: Stop Claude Code from forgetting everything
#112Earlier quoted context omitted.
The funny part is, the vast majority of them are barely doing anything at all. All of these systems are for managing context. You can generally tell which ones are actually doing something if they are using skills, with programs in them. Because then, you're actually attaching some sort of feature to the system. Otherwise, you're just feeding in different prompts and steps, which can add some value, but okay, it does…
It sounds like you've used quite a few. What programs are you expecting? Assuming you're talking about doing some inference on the data? Or optimizing for some RAG or something?
another is one claude code ships with, using rip grep.
Those are actual features. It's adding deterministic programs that the llm calls when it needs something.
Re: Show HN: Stop Claude Code from forgetting everything
#113Quite a few of you have mentioned that you store a lot of your working context across sessions in some md file - what are you actually storing? What data do you actually go back to and refer to as you're building?
Re: Show HN: Stop Claude Code from forgetting everything
#114Earlier quoted context omitted.
Honestly, very reasonable ask, you're not the first person to ask for a self-hosted version. We have a privacy policy we've drafted that is up-to-date with the current version of the product https://www.ensue-network.ai/privacy-policy . The project is still in alpha, so you could shape what we build next - what do you need to see, or what gets you comfortable sending proprietary code to other external services?
> what do you need to see, or what gets you comfortable sending proprietary code to other external services? Honestly? It just has to be local. At work, we have contracts with OpenAI, Anthropic, and Google with isolated/private hosting requirements, coupled with internal, custom, private API endpoints that enforce our enterprise constraints. Those endpoints perform extensive logging of everything, and reject calls th…
Re: Show HN: Stop Claude Code from forgetting everything
#115Earlier quoted context omitted.
I just don't have much faith in "if you're doing it right the results will be magically better than what you get otherwise" anymore. Any single person saying "the problems you run into with using LLMs will be solved if you do it my way" has to really wow me if they want me to put in effort on their tips. I generally agree with your why of why you set up like that. I'm skeptical that it will get over the hump of where…
That's completely fair, I also don't have much faith in that anymore. Very often, the people who make those claims have the most basic implementation that barely is one. I'm not sure if the problems you run into with using LLMs will be solved if you do it my way. My problems are solved doing it my way. If I heard more about your problems, I would have a specific answer to them. These are the solutions to where I have…
In some sense, computers and digital things have now just become a part of reality, blending in by force.
Re: Show HN: Stop Claude Code from forgetting everything
#116Each time an LLM looks at my project, it's like a newcomer has arrived. If it keeps repeating mistakes, it's because my project sucks.
It's an unique opportunity. You can have lots of repeated feedback from "infinite newcomers" to a project, each of their failures an opportunity to make things clearer. Better docs (for humans, no machine-specific hacks), better conventions, better examples, more intuitive code.
That, in my opinion, is how markdown (for machines only and not humans) will fall. There will be a breed of projects that thrives with minimal machine-specific context.
For example, if my project uses MIDI, I'm much better doing some specialized tools and examples that introduce MIDI to newcomers (machines and humans alike) than writing extensive "skill documents" that explain what MIDI is and how it works.
Think like a human do. Do you prefer being introduced to a codebase by reading lots of verbose docs or having some ready-to-run examples that can get you going right away? We humans also forget, or ignore, or keep redundant context sources away (for a good reason).
Re: Show HN: Stop Claude Code from forgetting everything
#117Is anyone else just completely overwhelmed with the number of things you _need_ for claude code? Agents, sub agents, skills, claud.md, agents.md, rules, hooks, etc. We use Cursor where I work and I find it a good medium for still being in control and knowing what is happening with all of the changes being reviewed in an IDE. Claude feels more like a black box, and one with so many options that it's just overwhelming,…
All I use is curse words and it does a damn great job most of the time
Re: Show HN: Stop Claude Code from forgetting everything
#118Re: Show HN: Stop Claude Code from forgetting everything
#119Earlier quoted context omitted.
Have you tried using it? Not being flippant and annoying. Just curious if you tried it and what the results were
Who has time to try this when there's this huge backlog here: https://www.reddit.com/r/ClaudeAI/search/?q=memory
Re: Show HN: Stop Claude Code from forgetting everything
#120This is impressive. Though I have found repo level claude.md that is updated everytime claude makes a mistake plus using —restore to select a previous relevant session works well. There is no way for Anthropic to optimize Claude code or the underlying models for these custom setups. So it’s probably better to stick with the patterns Anthropic engineers use internally.
And also - I genuinely worry about vendor lock-in, do you?