Frequently Asked Questions

Short answers to the most common questions about Friring. For depth, follow the links into the rest of the docs.

What is Friring?

Friring is a multi-session TUI orchestrator that runs any coding-agent CLI — Claude Code, Codex, Antigravity, opencode, aider, GitHub Copilot CLI, Vibe, pi, Oh My Pi, or any CLI you define — inside persistent tmux panes. Sessions, agents, and git worktrees are first-class citizens, and sessions survive crashes, restarts, and reboots because tmux keeps the processes alive.

Is Friring related to Thurbox?

Friring is a personal, opinionated fork of Thurbox by Thurbeen. It tracks upstream — improvements there get merged down, and the original commit history is kept intact — while landing features of its own. Thurbox's thur- reads as Thursday; Friring bumps it to Friday, and a ring is a boxing arena, so the name reads as an arena for agents. Friring cuts its own releases, so every install command here fetches a friring binary from its own repository.

How is Friring different from other parallel coding-agent tools?

Unlike tools such as Conductor, Claude Squad, or Cursor, Friring uses real tmux as its session backend rather than a re-implemented multiplexer, runs as a lightweight terminal UI rather than an Electron or native desktop app, and launches the unmodified vendor CLI rather than its own model. A single session can span multiple repositories, and it ships a native in-TUI code-review view. Agents are defined as data, so any CLI works with no recompile. See the comparison for the full breakdown.

Which coding agents does Friring support?

Friring is agent-neutral. It ships built-in definitions for Claude Code, Codex, Antigravity, opencode, aider, GitHub Copilot CLI, Vibe, pi, and Oh My Pi, and you can add any other CLI by editing agents.toml — no recompile required. Friring only knows how to launch each CLI with the right command and arguments; it never touches the agent's model, prompts, or permissions.

How do I install Friring?

On Linux or macOS, run curl -fsSL https://raw.githubusercontent.com/bvc3at/friring/main/scripts/install.sh | sh. It is also available via Homebrew (brew tap bvc3at/friring https://github.com/bvc3at/friring then brew install bvc3at/friring/friring), and on Windows via PowerShell (irm https://raw.githubusercontent.com/bvc3at/friring/main/scripts/install.ps1 | iex). On platforms with no prebuilt binary, install with cargo install --git https://github.com/bvc3at/friring --locked, or build from source with cargo build --release. See installation for details.

Which platforms does Friring run on? Does it support remote machines?

Friring runs on Linux, macOS, and Windows. It requires tmux 3.2+ on Linux/macOS and psmux on Windows. It can also run sessions on a remote host over SSH while the TUI runs locally — remote hosts are declared in hosts.toml.

Do my sessions survive a crash or restart?

Yes. Each session runs inside a persistent tmux session, so the agent processes keep running even if Friring crashes or you close and reopen it. Session state is stored in SQLite and re-adopted on restart.

Is Friring free and open source?

Yes. Friring is open source under the MIT license and free to use.

Can I use Friring without the TUI, headlessly?

Yes. A second binary, friring-cli, drives the same SQLite-backed, tmux-hosted sessions headlessly — create, list, send to, capture, restart, and delete sessions, plus automations and tasks — sharing the database with the TUI. This makes Friring scriptable for automation and CI.