Firetower

Firetower is an open-source, self-hosted control plane for coding agents. Give it a machine you can SSH into and a repository, and it picks a host, cuts a branch, makes a worktree, starts tmux, launches the agent and keeps it running. Then it does the part that actually costs you time: it tells you the moment the agent stops being useful without you. It is built for developers and engineering teams who want to run agents such as Claude Code and Codex on infrastructure they control, and it is described as self-hosted with no account. Firetower installs in about five minutes with a single curl command and offers clients for macOS, Windows, iOS and Android, so the same work can be attached to from a browser or a phone. The problem Firetower targets is where the agent runs. In a typical setup the agent lives in a terminal on the laptop you started it from, so closing the lid, crashing the app or losing a connection either kills the run or leaves it orphaned with no clear picture of what changed. Firetower argues that the agent should not run on the device you happen to be holding. Because the agent runs on your own server rather than on the device that started it, every device can pick up exactly where another left off. The work survives the failure of any single part, and the repository, the diffs and the agent sessions stay on infrastructure you control rather than inside a vendor's cloud. Firetower folds the entire workflow into one place: you start from your issues and Linear tickets, the agent runs your worktrees, you preview and annotate, then you commit and open a PR. Firetower reads from your trackers as you look, and starting a ticket opens a workspace. The ticket list shows an ID, a title, the project, the assignee, how long ago it was updated and a status column that can already show that an agent is starting — for example adding a dark mode toggle, fixing an invite link on mobile, or rate-limiting a webhook receiver. Workspaces are scoped per repository and per user, a command palette (⌘K) sits over the interface, and the product offers twelve ticket sources to pick from. Firetower runs remotely and keeps going when you close your laptop, and a pause control is available. The site walks through three failure cases. If your laptop closes or the app crashes, nothing happens to the agent, because it never ran on the laptop — open Firetower on any other device and the conversation is exactly where you left it. If the Firetower server goes down, the workers keep running: each agent is on its own machine in its own worktree, and when the server comes back it catches up on everything that happened while it was away. If a worker dies, the worktree is still there, your branch and every file the agent changed are on that machine, and Firetower still knows about them — restart the worker and carry on. How it fits together: Firetower reaches each machine over SSH and starts a worker there. The agents run on that machine — in tmux, on their own worktree — which is why closing your laptop costs nothing and why the app itself never has to be the thing that is busy. The apps (desktop on macOS and Windows, mobile on iOS and Android) talk to a Firetower control plane over HTTPS. The control plane is one compose file on a server you already own, and it dials out to workers over SSH. Workers are authoritative: they write what happened to their own log before reporting it, and when the control plane comes back it asks for everything since the last thing it saw, so a reconnect is a replay rather than a guess. The worker never opens a port — it reads frames from stdin and writes them to stdout — so who dials is a transport detail: a child process, a container exec, or SSH. Firetower is written in Rust and presented as small by design: a small core, no accumulating terminal daemons, and workspace memory ceilings where the host supports them, built for work that keeps running. The site compares its resource profile against an alternative. On desktop it reports roughly 50 MB for the Firetower app, against a reported ~1.5 GB idle for the Orca app plus daemon, which it describes as 30× more efficient. For an agent worker it reports 5 MB with the agent CLI separate, against a reported ~500 MB per agent, described as 100× more efficient. For the server it reports a 200 MB control plane, against a reported ~1 GB after restart, described as 5× more efficient. The benefit is straightforward: agent work continues whether or not you are watching, and your attention is requested only when an agent has stopped and needs you. Because each agent runs in its own worktree on its own machine, one broken run does not take the rest with it, and a dead worker does not lose the branch or the files it changed. Because sessions live on the server, you can start something at a desk and check on it later from a phone without losing state. And because the control plane self-hosts from a single compose file with no account, teams can keep the code, the credentials and the diffs on servers they already own, behind whatever firewall rules they already have. Concrete workflows follow directly from the way Firetower is described. You can open your GitHub issues or Linear tickets in Firetower, start a ticket and have a workspace open with an agent already running against the right repository. You can start a long agent run on a Mac Studio or a Hetzner VM and close your laptop, checking the diff later from an iPhone or Android device. You can run several agents at once across different machines and repositories — for example Claude Code on one repository and Codex on another — and watch the inbox for the sessions that are waiting on you. You can annotate an agent's output, then commit and open a pull request. And if a server restarts or a worker dies, you can restart the worker on its existing worktree and carry on rather than starting over. Firetower is aimed at developers, engineering teams and anyone already running coding agents who wants them off their laptop. The integrations named in the content are GitHub and Linear for tickets; the trackers are read as you look, and the product is listed under Product Hunt topics including Open Source, Software Engineering, Developer Tools and GitHub. Clients are available for macOS, Windows, iOS and Android, and the site also describes attaching from a browser or a phone. The stack described on the site includes Rust, SSH, tmux, git worktrees and a compose file, in a self-hosted deployment with no account and an install command of curl -fsSL https://usefiretower.com/install.sh | sh. The takeaway: Firetower turns scattered, laptop-bound agent sessions into something that behaves like infrastructure. Give it a server you can SSH into and a repository, and it handles the branch, the worktree, the tmux session and the launch — then stays quiet until an agent actually needs you, across every device you use.