I am excited to see another project that works as a stand-alone tool without any kind of server and without being an IDE plugin. I am highly curious about how you actually approach making modifications, so I am mostly interested in the transcript you posted. https://pastebin.com/FcGKdPbU
1. I notice that it seems to look at all files in examples, then opts to scan examples/react/start-basic-auth/src/main.tsx, then says "I apologize for the confusion" and seems to move on to something else (lines 13-22). What happened here? This happens again on line 77.
2. It looks (lines 25 to 37) like it has difficulty actually working with source files, due to file size. This seems to happen several more times in the h3 section (line 85). It might be worth building something like Aider's repomap to handle larger files.
It does seem to get to a useful conclusion without a lot of looping around, so overall it looks promising!
> I notice that it seems to look at all files in examples, then opts to scan examples/react/start-basic-auth/src/main.tsx, then says "I apologize for the confusion" and seems to move on to something else (lines 13-22). What happened here? This happens again on line 77.
You mean this response? "Looking at "examples/react/start-basic-auth/src/main.tsx", Checking main file for useSession usage"
I think there was a miscommunication between the agent and the sub-agent, the proper path should have had "app" not "src". I am working on better sub-agent prompting as there is some information loss sometimes, and then wrong assumptions made.
On line 77 it made the same wrong assumption about "src" instead of "app."
> It looks (lines 25 to 37) like it has difficulty actually working with source files, due to file size. This seems to happen several more times in the h3 section (line 85).
I did add a 10K limit to the characters of a file that will be read at a time, and I tried to tell it was only a partial read. The issue is that a single file can be huge sometimes and I didn't want to blow the context window.
While I appreciate the emergence of new AI coding tools, I've observed that many of them fail to offer significant improvements over Aider's existing capabilities (but I want to be proven wrong).
except that the future of LLM assisted programming means I can also make my own implementation of aider pretty easily. So theres going to be an explosion of software that does basically the same thing but it's private or just not widely shared. not because I don't want to share but because starting and supporting an open source project is a pita and I just want to build this one little cool thing and be done with it.
When I use it heavily for a work day it costs around $25 a day.
It will write whole features and debug things and write tests and docs. It is that valuable.
I’ve started to run two sessions at once to be more productive. I will be moving it to the cloud soon so I can run dozens of sessions at the same time.
Tech like this replaces human developers for the most part so yes it is worth it. $25/day is cheaper than hiring another dev or two.
I spent about five hours using Claude Code heavily yesterday to upgrade and enhance a four year old React web app. This app is widely used to reference anatomical nomenclature.
I was able to internationalize it for 45 major languages across the world (still subject to human testing). That allows it to be accessible for 85-90% of the world's population.
It cost me about $50. It saved me months of work on a "labor of love" project and allowed me to add lots of quality of life features in a single day that I just never would have gotten to otherwise.
https://github.com/xemantic/claudine/
reply