devpit

devpit is a native desktop application for controlling your coding agents from a single window. It brings together a terminal per project, a board for the work, the cost of every call and an orchestrator that spans projects. It is built for developers who run coding agents such as Claude Code and want their sessions, tasks and spend in one place rather than spread across tabs and applications. devpit runs on Linux, macOS and Windows, is free and open source under Apache 2.0, and runs locally on your own machine using the Claude Code plan you already have. Most agent work happens in fragments. A terminal lives in one window, the task list lives somewhere else, and the cost of the calls is invisible until later. devpit's answer is one window with everything the work needs inside it, with panes side by side rather than tabs split across six applications. Its stated goal is that several agents can run at once and none of them get lost: sessions stay visible, the ones waiting on you surface first, and nothing advances without your knowledge. Because the app is local-first and writes nothing into your repository, it can be adopted without changing how a team works. The centerpiece is an orchestrator that works across projects. It is a chat that reads every board you link, so you can hand it a card and it starts a session, then reports back to you. A Sessions panel keeps track of every session of your account and puts the ones waiting on you first, letting you answer them in place, as yourself. Above your windows sits a capsule called the island, which shows what each agent is doing and lets you allow or deny from there. The island distinguishes states such as thinking (started, before its first step), working, asking, waiting, done, failed and sleeping. There are also reminders that only remind: you can ask devpit to remind you at three to review the PR, and it will tell you then without starting anything. Everything the work needs lives in panes side by side. The Chat pane shows a turn at a time, along with what each one cost. The Terminal pane is a real pty behind tmux, so it can be split, the window can be closed, and the process is still found running when you return. The Board pane shows your columns in your order, and moving a card starts the work. Capabilities are optional extras per project, Notes and Excalidraw today, opened as panes. There is also a view for files, diffs and a browser, so you can review what an agent changed and the page it serves without leaving the app. devpit drives the agent you already use: Claude Code today, with more behind the same interface, and your own agents are defined as markdown files. Each project gets its own workspace. The board, the panes, the terminal and the costs live in ~/.devpit, so nothing lands in your repository. There is nothing to gitignore and nothing appears in the diff, and a teammate can work with you without ever hearing about devpit. Every project has one target terminal; switching between lines of work switches what is attached, while the previous session keeps running. Sessions outlive the window: you can close devpit, reopen it, and what was running still is, because tmux holds the processes. A worktree is created per line of work when a step needs a checkout, and it is never removed while it holds uncommitted work. A spending cap sits on every call: the column sets the ceiling and the card gets the real cost. The board is deliberately conservative. Nothing advances on its own. A step writes down its output, its exit code and its real cost, then stops; moving on is your call, unless you have set a lane to move, which the board shows. The orchestrator has clear limits: it never moves a card into a lane that runs a step, never acts on a timer, and never approves anything in another session. Replies it drafts go out only when you send them. Under the interface, devpit is Rust and Tauri rather than an Electron app, and each terminal is a real pty behind tmux, or psmux on Windows. Agent status is reported through a devpit-agent hook for other agents, while Gemini CLI reports status with nothing to set up, and Claude Code works through the claude CLI you already have. The outcome for users is visibility and control. Sessions that would otherwise be forgotten stay listed, with the ones waiting on you at the top. Cost is attached to individual calls rather than discovered later. Work survives closing the window, so an agent can be left running and picked up again. Worktrees mean parallel lines of work do not collide, and they are protected while they hold uncommitted changes. Because everything is local-first and nothing is written into the repository, you can start using devpit without asking a team to change its process. And because it uses your existing Claude Code plan, there are no new API keys to manage. Typical workflows include running several projects at once and switching between them without losing the thread, since each project keeps its own board, panes, terminal and costs. A developer might hand a card to the orchestrator, let it start a session, and wait for it to report back. When an agent asks a question, it appears in the Sessions panel under waiting on you, and it can be answered in place. Someone working on a flaky test can watch the session in the island and allow or deny actions from there. A user can review an agent's diff and the page it serves inside devpit rather than switching tools. And a reminder such as reminding you at three to review the PR is used when the user wants a nudge and no agent activity at all. devpit is aimed at developers who already run coding agents, particularly Claude Code users who want one place to watch and steer them. It integrates with Claude Code through the claude CLI, supports status reporting from other agents through the devpit-agent hook, and works with Gemini CLI with nothing to set up; Codex, Cursor and opencode support is stated as coming. The stack is Rust and Tauri, with a real pty per terminal behind tmux (psmux on Windows). Installation is a shell command on Linux and macOS and a per-user installer on Windows, and the Linux build also runs in WSL 2. It is free and open source under Apache 2.0 and needs no account; an account today only signs you in. Access from a phone is possible over Tailscale by pairing a device with a one-time code and choosing what it may do. In short, devpit is a local-first, open-source control room where multiple coding agents run side by side, every session stays visible, every call carries its real cost, and nothing advances without your say-so.