I built `oly` because I was tired of babysitting long-running CLI tools

I kept running into the same problem with AI coding agents and other interactive CLI tools: They do real work for a while, and then they get stuck on something small. A y/n prompt. A permission check. A confirmation step. A password prompt. Something that takes two seconds to answer, but somehow forces you to keep a terminal open and stay mentally tethered to it the whole time. That friction annoyed me enough that I built oly . The idea is simple: Run any CLI like a managed service. oly turns long-running, interactive CLI processes into persistent supervised sessions. You can start something, detach, close your terminal, come back later, inspect logs, reattach, or send input without fully jumping back into the session. What I wanted was not another terminal multiplexer. tmux and screen are great, but my problem was a little different. I did not just want persistence. I wanted something built around supervising agent-like CLI workloads: keep the process alive even if my terminal closes