Why we forked OmniRoute — and how to avoid it
OmniRoute is one of the most active AI routing projects on GitHub. I shipped 101 merged PRs to it as an external contributor before we forked it. So why fork at all?
WRITING
Notes on the work — systems, OSS contributions, fork discipline, and the long arc of building infra that has to keep running.
OmniRoute is one of the most active AI routing projects on GitHub. I shipped 101 merged PRs to it as an external contributor before we forked it. So why fork at all?
I ran a mechanical keyboard group buy: ~4,900 line items across 10 regions in 30 days. Its operational lessons carry straight into software systems.
Where process management, provider routing, and runtime constraints shape what software can actually do — and why I choose to work there.
BytePort models deployment as intent, not commands. The insight is simple: what you want to deploy is a different question from how it gets deployed.
ShareCLI observes and coordinates hundreds of concurrent AI coding agents. The engineering is about visibility, not control.