Hi HN. After exiting FusionAuth, I’ve been building a lot with coding agents, and the config sprawl got out of hand.
I’d fix something in one repo and forget the other ten. Or I’d start a new repo and have to copy everything over from whichever repo had the latest version.
I tried symlinks, submodules, subtrees, copy scripts, hooks, launchers, and a few other things. Nothing really worked.
The Agency lets you define config once and sync it to every repo that needs it. A small background daemon runs on every developer’s machine. It handles retrieving the latest config and distributing it to every repo that’s cloned on their machine. It removes drift issues entirely. Here’s a diagram that explains the flow:
voidmain42•2h ago
I’d fix something in one repo and forget the other ten. Or I’d start a new repo and have to copy everything over from whichever repo had the latest version.
I tried symlinks, submodules, subtrees, copy scripts, hooks, launchers, and a few other things. Nothing really worked.
The Agency lets you define config once and sync it to every repo that needs it. A small background daemon runs on every developer’s machine. It handles retrieving the latest config and distributing it to every repo that’s cloned on their machine. It removes drift issues entirely. Here’s a diagram that explains the flow:
https://theagencyhq.dev/how-it-works/
It’s day one, so it’s rough. It runs on Mac and Linux and Mac is the best-tested platform. I’d genuinely like to hear where it breaks for you.