HN Explorer

Show HN: Continuous Claude – run Claude Code in a loop (github.com)

170 points by anandchowdhary ↗ HN
Continuous Claude is a CLI wrapper I made that runs Claude Code in an iterative loop with persistent context, automatically driving a PR-based workflow. Each iteration creates a branch, applies a focused code change, generates a commit, opens a PR via GitHub's CLI, waits for required checks and reviews, merges if green, and records state into a shared notes file.

This avoids the typical stateless one-shot pattern of current coding agents and enables multi-step changes without losing intermediate reasoning, test failures, or partial progress.

The tool is useful for tasks that require many small, serial modifications: increasing test coverage, large refactors, dependency upgrades guided by release notes, or framework migrations.

Blog post about this: https://anandchowdhary.com/blog/2025/running-claude-code-in-...

18 comments

[ 2.5 ms ] story [ 42.0 ms ] thread
[deleted]
(comment deleted)
leobg
Missed opportunity to call it Claude Incontinent (CLI).
apapalns
> 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 and requires careful deliberate thought. Without deep understanding of business logic (which takes time and is often lost after the initial devs move on) you’re not gonna get great tests.

To be fair to AI, we hired a “consultant” that also got us this same level of testing so it’s not like there is a high bar out there. It’s just not the kind of problem you can solve in 2 weeks.

andai
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.

gloosx
Ah yes, classic "increase test coverage for the sake of increasing test coverage".

Aligns with vibe-coding values well: number go up – exec happy.

decide1000
How does it handle questions asked by Claude?
namanyayg
Exactly what I needed! I might use it for test coverage on an ancient project I need to improve...
cog-flex
Does this exist for Codex?
tinodb
You can do this with a single while loop in bash. No need for this project. Search for “ralph wiggum ai coding” and find a couple of guys that share plenty of examples and nerd out about it
kami23
I'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.
lizardking
It's oddly satisfying to watch your tooling improve itself.
jes5199
can it read code review comments? I've been finding that having claude write code but letting codex review PRs is a productive workflow, claude code is capable of reading the feedback left in comments and is pretty good at following the advice.
DeathArrow
>run Claude code in a loop

And watch your bank account go brrr!

i4k
I 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.