I'm a developer, and lately I've been vibe-coding 4–5 projects at the same time with coding agents.

The hardest part wasn't running the agents. It was keeping track of everything myself — what had been decided, what's blocked, what should happen next, and re-explaining that context whenever I opened a new session.

I'm currently using Orca as my ADE/orchestrator, and managing several projects at once made me want a more structured coordination and orchestration setup.

So I built this:

[https://github.com/Pixel-Tao/public-flux-conductor](https://github.com/Pixel-Tao/public-flux-conductor)

There's no app, bot, GitHub Actions, or separate service behind it.

It's basically a set of instructions that makes **GitHub Issues + one GitHub Project the persistent state of the work**.

* Execution plans are Issues
* Approval is a comment
* Nothing gets dispatched before approval
* An agent completion report only finishes that dispatch — it doesn't automatically mark the task Done
* Merging a PR doesn't automatically mean Done either

There's also a small environment config that maps the generic roles to whatever tools you actually use. The orchestrator and recommended skill baselines are optional, so it can also run with a single agent working through dependencies.

I've only been using this version on real projects for a short time, but so far having agents record decisions, progress, and state directly in GitHub has worked better than I expected. New sessions can usually look at the board and figure out where to continue without me reconstructing the whole project history.

The current instructions are mainly written around **Codex and Claude**, but if people find the approach useful, I'd like to keep expanding support for other agents and workflows.

It's still early and the instruction set is probably larger than it needs to be, so I'm sharing it partly to get feedback.

If you've been running multiple repos or agents at the same time, I'd especially like to know where you think this approach will break down.

Issues, criticism, and forks are welcome.

I got tired of keeping the state of 4–5 AI coding projects in my head, so I moved it into GitHub