Most active commenters
  • anandchowdhary(4)

←back to thread

Show HN: Continuous Claude – run Claude Code in a loop

(github.com)
170 points anandchowdhary | 12 comments | 15 Nov 25 16:27 UTC | HN request time: 0.195s | source | bottom

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

1. janaagaard ◴[17 Nov 25 20:08 UTC] No.45957680[source]▶
Kudos on making Bash readable.

(https://github.com/AnandChowdhary/continuous-claude/blob/mai...)

replies(1): >>45958379 #
2. jdc0589 ◴[17 Nov 25 21:14 UTC] No.45958379[source]▶
im not saying OP did this, but I've actually had AI spit out some pretty stellar bash scripts, surprisingly
replies(3): >>45958439 #>>45961287 #>>45967647 #
3. anandchowdhary ◴[17 Nov 25 21:18 UTC] No.45958439[source]▶
No, you're right. It was a pretty collaborative effort with me and Claude!
replies(1): >>45958550 #
4. svieira ◴[17 Nov 25 21:29 UTC] No.45958550{3}[source]▶
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#*=}; shift; set -- "${_key}" "$_value" "$@";;
   esac
replies(2): >>45958853 #>>45961848 #
5. anandchowdhary ◴[17 Nov 25 22:00 UTC] No.45958853{4}[source]▶
For letting me know! Would you like to create a PR? Otherwise I'll add you as a Co-Authored-By!
replies(1): >>45970962 #
6. cortesoft ◴[18 Nov 25 04:09 UTC] No.45961287[source]▶
The emojis give it away
replies(2): >>45968248 #>>45994040 #
7. insin ◴[18 Nov 25 05:59 UTC] No.45961848{4}[source]▶
Gesundheit
8. rkozik1989 ◴[18 Nov 25 15:37 UTC] No.45967647[source]▶
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.
9. anandchowdhary ◴[18 Nov 25 16:19 UTC] No.45968248{3}[source]▶
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

replies(1): >>46002911 #
10. svieira ◴[18 Nov 25 19:37 UTC] No.45970962{5}[source]▶
Co-authored is fine, thanks for asking!
11. jdc0589 ◴[20 Nov 25 16:01 UTC] No.45994040{3}[source]▶
I got a couple bug reports years ago on https://github.com/jdavisclark/jsformat for not dealing unicode emojis correctly when used in variable names in javascript. people are weird.
12. johntash ◴[21 Nov 25 09:47 UTC] No.46002911{4}[source]▶
LLMs had to learn where to use emoji from somewhere, now we know who to blame ;)