Firekeeper

Start here

Quick start

Install once. Launch your agents normally. Run firekeeper in another terminal.

Before you start: have at least one supported agent installed and signed in on this machine: Claude Code, Codex, GitHub Copilot CLI, Kimi Code, OpenCode, Gemini CLI, or Cursor CLI. Firekeeper monitors agents; it does not install or launch them.

1. Install Firekeeper

Choose one installation method. These install a prebuilt binary; you do not need Go.

macOS with Homebrew

brew install DanBradbury/tap/firekeeper

Requires Homebrew. If you do not use Homebrew, choose the script below instead.

macOS or Linux with the install script

curl -fsSL https://raw.githubusercontent.com/DanBradbury/firekeeper/main/install.sh | sh

The script installs to ~/.local/bin without sudo. Follow its PATH hint if your shell cannot find firekeeper, or see command not found.

Windows with PowerShell

irm https://raw.githubusercontent.com/DanBradbury/firekeeper/main/install.ps1 | iex

The script installs to %LOCALAPPDATA%\Programs\firekeeper and adds it to your user PATH. Administrator rights are not required.

These one-liners execute a downloaded script. Prefer to inspect it or install a release manually? See installation, checksum verification, version pinning, and uninstall instructions.

macOS is the main target. Linux is best effort. Windows 10 1809+ and Windows 11 are supported on amd64 and arm64, with platform-specific limitations.

2. Find your first session

Open your project and start a supported agent using your normal command, for example claude or codex. If one is already running on this machine, leave it running. Use the same operating-system user for Firekeeper and the agent.

In a second terminal window, tab, or pane, run:

firekeeper

Firekeeper opens on Processes. Within a couple of seconds, you should see the agent's runtime, project, and the session details it can read. Firekeeper can run from any directory; it does not have to be inside the agent's project.

No setup service required. You do not need login, serve, or daemon install for this workflow. Your agent keeps its normal launch command and sign-in.

An empty list does not mean installation failed: Processes shows running agents, not all saved conversations. If your running agent is missing, follow the missing-session checklist. For agents inside WSL, install and run the Linux build of Firekeeper inside WSL too.

3. Try the everyday controls

  1. Use Up / Down to select a runtime and inspect its details.
  2. Press c to read its conversation. Press Esc to return.
  3. Press s to switch to its terminal on a supported platform. Terminal support and limitations explain where this works.
  4. Press Tab to visit Overview and Usage.
  5. Press ? for help. Close help, then press q to quit the dashboard.

Quitting Firekeeper does not stop your agents. Reopen it whenever you want another look.