About

Hi, I’m Bilal.

I’ve been writing software for about two decades. In my off-hours I build free apps for nonprofits and my community, and the occasional tool I want for myself.

orchid is one of those tools. I was already paying for more than one coding agent, and each was good on its own. What I didn’t have was a way to let them work together without me sitting in the middle: one writes, another reviews, my tests decide, and I hear about it only when there is a real decision to make.

So orchid is deliberately small: a bash state machine, git for memory, and the CLIs I already had. I dogfood it on itself and on the apps I build, and I write down what breaks. The README says plainly what is enforced, what is policy and what hasn’t been proven yet.

It’s the third of shellbell, which brings a terminal to you when it needs attention, and sous, which keeps one list of what is waiting on you. I build and maintain all three on my own. The code is open so you can read it, run it, and write the engine adapter your work needs.

No API keys.
No server.
No dashboard.

orchid is free and MIT licensed. It runs on your machine, keeps its state in git on your repository’s integration branch, and calls only the agent CLIs you already use.

Read the code or contribute What orchid keeps, and where