🐛 Loop Intermediario: GitHub Issue Bot

O GitHub Issue Bot usa uma sessao principal de Claude Code como orchestrator que despacha 4 workflows paralelos. Cada workflow e uma sessao independente que recebe uma issue, implementa o fix, roda testes e cria o PR.

"We can use Archon to send off workflows to run in parallel, handling multiple GitHub issues at the exact same time. And this is very much like loop engineering because we have our primary cloud code here as our orchestrator."

You are the orchestrator for a GitHub issue fixing system.

1. Read the list of open issues from the GitHub API
2. For each issue, dispatch a worker workflow in a separate worktree
3. Each worker will: extract context, classify (bug/feature), implement, validate, create PR
4. Monitor all workers. When all PRs are ready, dispatch review workflows
5. Report final status with PR links

Issues to handle: #42, #45, #51, #58

Quando multiplos workers editam codigo em paralelo, eles precisam de isolamento total. Git worktrees resolvem isso: cada worker opera em seu proprio checkout do repositorio, com sua branch separada.

"Work trees are also a really important part of loop engineering. Boris talks about this as well. If we're having many different agents handling tasks in a loop, we need to make sure they're running in isolation so they're not stepping on each other's toes."

# Criar worktree para cada issue
git worktree add ../worktree-42 -b fix/issue-42
git worktree add ../worktree-45 -b fix/issue-45
git worktree add ../worktree-51 -b fix/issue-51
git worktree add ../worktree-58 -b fix/issue-58

# Cada worker roda em seu diretorio
cd ../worktree-42 && claude --prompt "Fix issue #42..."

# Limpar apos merge
git worktree remove ../worktree-42

Isolamento de codigo (worktrees) resolve metade do problema. A outra metade e isolamento de dados. Neon permite criar branches do banco Postgres para cada worker, evitando que migracoes e dados de teste conflitem.

"One thing that you have to do a lot is branches in your database. If each coding agent is working on something in parallel, you don't want them to be stepping on each other's toes, not just with code changes, but also database changes. So work trees and Neon is a super powerful thing."

# Criar branch de banco para cada worker (via Neon CLI)
neonctl branches create --name worker-42 --parent main
neonctl branches create --name worker-45 --parent main

# Cada worker recebe sua DATABASE_URL isolada
export DATABASE_URL=$(neonctl connection-string --branch worker-42)

# Apos merge do PR, deletar branch
neonctl branches delete worker-42

Cada worker segue um pipeline deterministico de 7 steps. O processo e fixo (o humano define os steps), mas cada step usa um LLM para executar. Isso combina o melhor de loops e workflows deterministicos.

"Another really important thing with Archon is that we're not having the agent drive the entire thing. It's more deterministic because we set up the process in this workflow file."

Uma das maiores vantagens de workflows deterministicos sobre loops puros e a capacidade de usar modelos diferentes em cada step. Isso reduz custo drasticamente sem sacrificar qualidade onde ela importa.

"One of the other big issues I see with using slash goal or routines or loops in cloud code is you're just using one model for pretty much everything. That's part of the problem of why it's so expensive."

O issue bot e poderoso, mas nao e magico. Questoes reais que surgem na pratica.