Hey folks, I started working on Ouijit around the start of the new year, and its since become the daily driver for myself and a handful of other engineers (that I know of).
The initial reason I built it was over dissatisfaction with how most agent orchestrators abstract stuff behind chat UIs, require login, or only support their companies own model/harness. I didn’t want to keep cobbling together scripts for worktree isolation between tasks though, so the yak shaving began. A couple weeks in, I received a message from a friend sharing that they just finished an 8 hour session working in it and they really liked it, and that they’d even shared it with their coworkers unprompted. I’ve been a software engineer/designer for ~10 years and its hard to put into words how rewarding that felt.
Some things I think are unique about Ouijit:
-
Sandboxing is a first-class consideration, Ouijit supports running tasks in per-project Lima VMs. Right now I'm looking into making sandboxing pluggable so you can bring-your-own agent environment local or in the cloud, with a few baked in defaults.
-
Integrated agents are automatically aware of a session-scoped CLI that enables them to orchestrate and drive tasks from any Ouijit terminal, with no additional setup.
-
Tasks have lifecycle hooks that can trigger prompts, scripts, or both when tasks start, resume, move to review, or move to done.
-
You can organize child terminals, markdown, and url previews to terminals. It's a little like Claude artifacts in that way.
Supports macOS and linux; integrates with Claude Code, Codex, Pi, and OpenCode agent harnesses.
Free and open source, no login, no telemetry.
Website: [https://ouijit.com](https://ouijit.com)
Github : [https://github.com/ouijit/ouijit](https://github.com/ouijit/ouijit)
Comments URL: [https://news.ycombinator.com/item?id=48732590](https://news.ycombinator.com/item?id=48732590)
Points: 3