>run Claude code in a loop
And watch your bank account go brrr!
Show HN: Continuous Claude – run Claude Code in a loop
51–60 of 66 posts
Re: Show HN: Continuous Claude – run Claude Code in a loop
#52I was expecting to see links to a bunch of opensource successful examples, projects self-managed and continuously adding code and getting better.
99.9999% of AI software is vaporware.
Re: Show HN: Continuous Claude – run Claude Code in a loop
#53I've dubbed my loop of this as 'sicko mode' at work as I've become a bit obsessed with automating everything little thing in my flow, so I can focus on just features and bugs. It feels like a game to me and I enjoy it a lot.
It's oddly satisfying to watch your tooling improve itself.
Re: Show HN: Continuous Claude – run Claude Code in a loop
#54>run Claude code in a loop And watch your bank account go brrr!
If you have a max plan you just watch your usage get throttled
Re: Show HN: Continuous Claude – run Claude Code in a loop
#55Kudos on making Bash readable. ( https://github.com/AnandChowdhary/continuous-claude/blob/mai... )
im not saying OP did this, but I've actually had AI spit out some pretty stellar bash scripts, surprisingly
I don't think its that surprising. Bash is old as dirt and scripts by definition are meant to be simple. Where AI struggles is when you add complexity like object-oriented design. That's when the effect of it trying to solve every problem in a way unique to it just takes shit off the rails. LLMs known design patterns exist but they don't know how to use them because that's not how deep learning approaches problem solving.
Re: Show HN: Continuous Claude – run Claude Code in a loop
#56> codebase with hundreds of thousands of lines of code and go from 0% to 80%+ coverage in the next few weeks I had a coworker do this with windsurf + manual driving awhile back and it was an absolute mess. Awful tests that were unmaintainable and next to useless (too much mocking, testing that the code “works the way it was written”, etc.). Writing a useful test suite is one of the most important parts of a codebase…
I had a funny experience with Claude (Web) the other day.
Uploaded a Prolog interpreter in Python and asked for a JS version. It surprised my by not just giving me a code block, but actually running a bunch of commands in its little VM, setting up a npm project, it even wrote a test suite and ran it to make sure all the tests pass!
I was very impressed, then I opened the tests script and saw like 15 lines of code, which ran some random functions, did nothing to test their correctness, and just printed "Test passed!" regardless of the result.
Re: Show HN: Continuous Claude – run Claude Code in a loop
#57> codebase with hundreds of thousands of lines of code and go from 0% to 80%+ coverage in the next few weeks I had a coworker do this with windsurf + manual driving awhile back and it was an absolute mess. Awful tests that were unmaintainable and next to useless (too much mocking, testing that the code “works the way it was written”, etc.). Writing a useful test suite is one of the most important parts of a codebase…
I find coding agents can produce very high quality tests if and only if you give them detailed guidance and good starting examples. Ask a coding agent to build tests for a project that has none and you're likely to get all sorts of messy mocks and tests that exercise internals when really you want them to exercise the top level public API of the project. Give them just a few starting examples that demonstrate how to…
Does it depend on the model? I would have expected the bigger ones to be better with common sense and not fixating on irrelevant details. But I have only used them with quite small codebases so far. (Which have basically no internals to exercise!)
Re: Show HN: Continuous Claude – run Claude Code in a loop
#58Earlier quoted context omitted.
im not saying OP did this, but I've actually had AI spit out some pretty stellar bash scripts, surprisingly
The emojis give it away
Nah - as you'll see from my work from a pre-coding agents age, I like emoji :)
Here are receipts some from 2020: - https://github.com/AnandChowdhary/bsc-thesis - https://github.com/AnandChowdhary/slack-netlify-trigger - https://github.com/AnandChowdhary/analytics-icons
Re: Show HN: Continuous Claude – run Claude Code in a loop
#59> codebase with hundreds of thousands of lines of code and go from 0% to 80%+ coverage in the next few weeks I had a coworker do this with windsurf + manual driving awhile back and it was an absolute mess. Awful tests that were unmaintainable and next to useless (too much mocking, testing that the code “works the way it was written”, etc.). Writing a useful test suite is one of the most important parts of a codebase…
Ah yes, classic "increase test coverage for the sake of increasing test coverage".
Aligns with vibe-coding values well: number go up – exec happy.
Re: Show HN: Continuous Claude – run Claude Code in a loop
#60Earlier quoted context omitted.
FYI, you're missing two patterns that allow the `--key=value` admirers and the `-alltheshortopsinasinglestring` spacebar savers among us to be happy (for the otherwise excellent options parsing code). shopt -s extglob case "$1" # Flag support - allow -xyz z-takes-params -@(a|b|c)*) _flag=${1:1:1}; _rest=${1:2}; shift; set -- "-$_flag" "-$_rest" "$@";; # Param=Value support -?(-)*=*) _key=${1%%=*}; _value=${1#*=}; shi…
For letting me know! Would you like to create a PR? Otherwise I'll add you as a Co-Authored-By!
Co-authored is fine, thanks for asking!