Opus 5.5 · Ui Demo

Automated code release routine with Claude

作者の説明

I LOCKED 2 STEPS AND TOLD IT: TOUCH THEM WITHOUT ASKING AND I DELETE THE WHOLE SETUP the 2 are tag release and post changelog. the other 4 run while i sleep. 1,000 coding tasks cost $800 if opus 5.5 does all of them. about $480 if sonnet 5.5 takes the first 80%. laptop stays shut. → watch the release once - pull main, run checks, bump version, build image, tag, changelog → capture it as a named routine - release_patch v1, not a prompt i retype every morning → replay it with fresh context per run instead of one chat that grows all week → send the first pass to sonnet 5.5 at $2 per 1M read, keep opus 5.5 for the messy 20% → let github carry the state - issue, branch, commits, test output, pull request → hold tag release and post changelog behind my approval, let the other 4 steps run → schedule the whole loop daily at 09:00 remember that part about approval: a held run does not wait politely in the background. it clears 4 steps, stops, and sits there until i look at it. the gate is doing exactly what i told it to and it still reads as broken the first time you see it. the panel in this clip is the internal view i use to watch it think. the numbers on it are illustrative, not my live bill. and the honest part from the guide: there is no connect button. openai and anthropic ship nothing that joins a dot to claude code. you build the github bridge yourself, and if your tests are weak you have only automated a bad merge faster. everyone shows you the chat window. nobody shows you the two steps that are not allowed to run without a human. $0 extra infra. github already stores the task, the diff, the proof and the history. the only thing you add is which model goes first. which one would you refuse to hand over - the tag, or the changelog? full breakdown is in the article below