@dev_b5ee97
25 days ago
ran into this same problem and ended up rolling my own markdown-based memory files instead of claude-mem. works for my setup but the 46k stars are telling - most people want zero config.

Anthropic's terminal-native coding agent that reads and edits code, runs tests, and commits to GitHub; launched as a research preview with Claude 3.7 Sonnet.
@dev_b5ee97
25 days ago
ran into this same problem and ended up rolling my own markdown-based memory files instead of claude-mem. works for my setup but the 46k stars are telling - most people want zero config.
@hn_9e6193
26 days ago
I agree that AI powered programming can give you a boost, and the points made in the post I would agree with if they were not made about Claude Code or other "agentic" coding tools. The human-LLM boosting interaction exists particularly when you use the LLM in its chat form, where you inspect and reshape with both editing the code and explaining with words what the LLM produced, and where (this is my golden rule) you can only move code from the LLM environment to your environment after inspecting and manually cut & pasting stuff. Claude Code and other similar systems have a different goal: to allow somebody to create a project without much coding at all, and the direction is to mostly observe more the result itself of the code, that how it is written and the design decisions. This is fine with me, I don't tell people what to do, and many people can't code, and with systems like that they can build a certain degree of systems. But: I believe that tody, 21 April 2025 (tomorrow it may change) the human+LLM strict collaboration on the code, where the LLM is mostly a tool, is what produces the best results possible, assuming the human is a good coder. So I would say there are three categories of programmers: 1. Programmers that just want to prompt, using AI agents to write the code. 2. Programmers, like me, that use LLM as tools, writing code by hand, letting the LLM write some code too, inspecting it, incorporating what makes sense, using the LLM to explore the frontier of programming and math topics that are relevant to the task at hand, to write better code. 3. Programmers that refuse to use AI. I believe that today category "2" is what has a real advantage over the other two. If you are interested in this perspective, a longer form of this comment is contained in this video in my YouTube channel. Enable the English subtitles if you can't understand Italian. https://www.youtube.com/watch?v=N5pX2T72-hM
@hn_d843cc
26 days ago
> When your workflow consists of asking questions and getting answers immediately, you don't get to see what's nearby. Very much aligns with my experience. For me this is the most unsatisfying thing about AI-based workflows in general, they miss stuff humans would never miss. All the time I wonder what am I missing that's right nearby? It's remarkable how many times I have to ask Claude code to fully ingest something before it actually puts it into context. It always tries to laser through to target it's looking for, which is often not what you want it to look for, at least not all you want it to look for. Getting these models to open up their field of vision is tough.
@rd_16e6d0
26 days ago
this is clearly an agent instruction issue, I have the same with sonnet within cc. It *has* the Read tool but it has the stupid habit to use sed instead. I wrote it to claude md - "Always prefer the Read tool over sed for reading files."
@hn_a37270
26 days ago
Claude code runs in the terminal, not Chromium. It's hardly an "electron app" at all. It's a nodejs app, and there is no reason to have a problem with that. Nodejs can wait for inference as fast as any native app can.