franco pfp
franco
@francos.eth
I love leaving my little codex agents working over night. Currently running 5 on different parts of the codebase. I still have to figure out how to add dependencies so they don't create a ton of conflicts: * Agent A: Phases 1 → 2 * Agent B: Phase 3 (after 2) * Agent C: Phase 5 → 6 (after 3) * Agent D: Phase 4 (after 3) * Phases 7 – 9 follow once earlier work merges.
5 replies
0 recast
10 reactions

agusti pfp
agusti
@bleu.eth
you cold have a meta-orchestrator agent who can coordinate the sub-agents and spawn them sequentially/on parallel or when dependencies finish.
1 reply
0 recast
4 reactions

Marissa pfp
Marissa
@marissaposner
Also I would love to see your workflow for this in a video!
1 reply
0 recast
1 reaction

Marissa pfp
Marissa
@marissaposner
how are you splitting up the phases?
1 reply
0 recast
1 reaction

HH pfp
HH
@hamud
they go round in circles for me and the code then becomes waffle
0 reply
0 recast
1 reaction

s5eeo pfp
s5eeo
@s5eeo
What’s the rate of success with that in your experience so far? Does it ever result in a mess rather than improvements?  Also curious about how detailed your instructions are before you let the agents run.  In my experience, it often takes a detailed implementation plan to ensure they don’t make a mess. But it’s a lot of work to create it for all the tasks.
0 reply
0 recast
0 reaction