Hi HN, I’m working on Ouijit.
It’s a project and task-based terminal session manager that provides a few basic but useful tools for agent workflows:
- Terminal sessions in Ouijit have access to the ouijit CLI, and supported agents (Claude, Codex, Pi) can work with it out of the box to manage tasks and customize a personal development workflow
- Tasks live on a kanban board that supports hooks for task lifecycle events (eg. ‘Run this script when a task moves to ‘in progress’)
I’ve found this simple combination to be very expressive and flexible for adapting to changing workflows.
I made the V1 a couple months ago for fun, and have kept at it since a friend shared they had logged an 8 hour work session in it. Along the way I’ve baked in lots of what I believe are table-stakes for this type of tool, like task isolation via Git worktrees, agent working/idle status with sound and notifications, diff/markdown plan/URL previews, and support for VM sandboxing using Lima.
It’s free and open source with no login or telemetry, so feedback is highly appreciated.
Github: https://github.com/ouijit/ouijit Website: https://ouijit.com
Nice job... the kanban + task hooks combine is a good one. Wonder how parallel activities function in practice though. How do you keep two or three agents running at the same time on distinct tasks from stomping on each other? Like, is each agent going to receive its own sandboxed terminal/session or is it going to rely on worktrees to keep things separated? Asking because I've wanted to run many instances of Claude side-by-side without one overwriting the other's edits.
Every task automatically gets git worktree isolation to support the parallel work. The VM sandboxing is project scoped and more about isolating agent workloads from user-space for those who want to --dangerously-skip-permissions for example.
[flagged]
[dead]