I tried tools like Conductor, but I felt like I was still managing terminal sessions instead of managing work.. I wanted, - Project context written once, then refreshed as the codebase changes so I don't have to repeat myself - A kanban/task board with statuses where every task is its own agent - Multiple projects running from one place - A clear view of what each agent is doing and which tasks need me - One git worktree and branch per task - Sessions that keep running after I close the browser - Diff review and merge without hunting through terminals - Ability to host it remotely and access my orchestrator from any device anywhere My main idea was to operate one level above the IDE. Instead of remembering which terminal belongs to which task, I wanted to manage projects and tasks. Each task keeps its agent session, context, git state, and history together. It primarily supports Claude Code using subscription logins, with no API key or per-token billing. Codex is also (kinda) supported but I haven't texted it exhaustively yet so YMMV. Operator is open source and self-hostable! https://github.com/iishyfishyy/operator-oss I would be interested to hear how other people running several remote coding agents manage this today and if anyone has feedback :) |