Hey r/ClaudeCode , I want to share a project that’s really two things at once. The product: GymCoach is an open-source, self-hosted hypertrophy training tracker with a built-in AI coach. Next.js 14 + TypeScript, Prisma/Postgres, Docker. The coach builds a compact, structured payload from your profile, recent sessions, active program and per-exercise progression - then suggests program changes that are Zod-validated before anything touches your data. Provider-agnostic LLM layer (Anthropic / OpenRouter / a keyless demo mode), so you can run it however you want. The actual experiment: this is a deliberate test of the limits — I’m letting the repo run itself and seeing how far an autonomous loop can take a real codebase before it breaks, stalls, or surprises me. There are autonomous Claude Code loops that:
- triage the codebase for real work (TODOs, coverage gaps, small bugs, roadmap items) and file scoped GitHub issues,
- implement an issue end-to-end on its own branch, following the repo’s conventions,
- pass a hard “green-gate” (lint + typecheck + unit + build, integration/E2E in CI) before anything merges,
- ship the PR — wait for CI, self-review the diff, auto-merge on green,
- then write up what shipped in the changelog and a public playbook. So the issue → PR → review → merge → document cycle closes without me in the middle. Every merged change has to earn its way past the same gate a human contributor would. The whole “how it maintains itself” démarche is documented in the repo so it’s reproducible, not just a demo. The open question: I genuinely don’t know where this goes
- that’s the point of pushing the limits. Does the loop grind toward becoming the most advanced open-source fitness-tracking repo out there? Or does it quietly pivot on its own into something I didn’t plan? We’ll see how far it can go. And I keep adding new loops to feed the self-improvement - like a deep-research loop that scouts new feature ideas, benchmarks against competing apps, and mines the public reviews of other fitness apps to turn real user pain points into issues the build loop can pick up. Follow along (issues, PRs, changelog all public): github.com/Julien-Au/gymcoach Happy to answer questions about the loop setup, the green-gate, or how the AI coach payload is built. submitted by /u/Newbie_investisseur
Originally posted by u/Newbie_investisseur on r/ClaudeCode