Firetower icon

Firetower

Firetower is an open-source, self-hosted control plane for coding agents. Start from issues, monitor sessions, review changes, and open pull requests.

Firetower

Remote control for self-hosted coding agents

Firetower is an open-source, self-hosted control plane for running coding agents on machines you own. It connects to a server or worker over SSH, creates a branch and Git worktree, starts a tmux session, launches the agent, and provides a remote interface for following the work.

The workflow is designed for coding tasks that should continue after the initiating device disconnects. Users can start from tracked work such as GitHub Issues or Linear tickets, inspect and annotate changes, then commit the branch and open a pull request from a browser, desktop client, or mobile device. Firetower Cloud is planned but not currently available, so the documented deployment model is self-hosting.

Core features

Self-hosted control plane

Run the control plane on infrastructure you own and connect it to machines over SSH instead of relying on a hosted service.

Persistent remote agent sessions

Workers create a branch and worktree, start tmux, launch the coding agent, and keep the session running on the worker machine.

Multi-device access

Connect from a browser, macOS or Windows desktop, or iOS and Android mobile clients, then resume a session from another device.

Session monitoring and review

View the agent's progress, receive notice when it needs attention, and inspect or annotate the resulting changes before shipping them.

Issue-to-PR workflow

Start work from GitHub Issues, Linear tickets, or tickets surfaced in the interface, then commit changes and open a pull request.

Reconnect and failure recovery

The worker records events locally and the control plane replays missed events after reconnecting, while each worker keeps its own worktree and branch.

Practical use cases

  • Issue-driven feature work

    Start an issue or ticket from a browser, let the agent work in an isolated branch and worktree, and review the diff before committing and opening a pull request.

  • Coding while away from the desk

    Launch a task from a laptop, close it, and continue monitoring or responding from a phone or another supported client without moving the running agent.

  • Managing parallel remote sessions

    Keep several agent sessions running on separate worker machines or worktrees while using the control plane to identify sessions that have stopped or need attention.

  • Self-managed development infrastructure

    Run the app and workers on infrastructure under your control when keeping the agent runtime and repository work on self-managed machines is part of the operating model.

Pros and Cons

Pros

  • Runs coding agents on user-owned servers or other connected machines rather than on the client device.
  • Sessions survive closing the laptop because the agent runs remotely in tmux on a worker worktree.
  • Supports access from browser, macOS, Windows, iOS, and Android clients.
  • Includes an issue-to-branch-to-review workflow with diff review, annotation, commits, and pull requests.
  • Open-source and self-hosted, with no account required according to the product description.

Cons

  • Self-hosting requires users to install and operate the app and workers, with Docker, the Compose plugin, and Node 20 or newer required on installation machines.
  • The hosted Firetower Cloud option is planned and not available yet.
  • The supplied product material does not document the full list of supported coding agents, repository providers, or team and permission controls.

FAQ

How is Firetower installed?

Firetower is self-hosted today. Install the CLI, run the app once, and install a worker on each machine that should run agents. The documented requirements are Docker, the Compose plugin, and Node 20 or newer on each installation machine.

What is the difference between the app and a worker?

The app runs on a laptop or server and holds hosts, repositories, and credentials. Workers run on machines that contain git, tmux, and the coding agent. Firetower reaches those machines over SSH, while workers communicate through stdin and stdout.

Can a session continue when I close my laptop?

Yes. Agents run on the server or worker machine rather than on the device used to connect. You can close a laptop and resume from another supported device, including a browser, desktop app, or phone.

What workflow does Firetower support?

The documented workflow starts from GitHub Issues, Linear tickets, or tickets shown in the interface. Firetower creates a branch and worktree, starts tmux, launches the agent, and provides a workspace for reviewing changes, previewing and annotating, committing, and opening a pull request.

Is a hosted Firetower Cloud version available?

Firetower Cloud is planned but not available yet. The currently documented option is to host the app and workers yourself.

Quick Facts

Category
Developer Tool
Deployment
Self-hosted
Source model
Open source
Client access
Browser, macOS, Windows, iOS, and Android
Core workflow
Issue or ticket → agent worktree → review → commit and pull request
Current hosted option
Firetower Cloud is planned, not available yet