Install

A frogg has two parts:

• The daemon runs on the machine with your code and your agent CLIs (Claude Code, Codex, OpenCode…). It owns agents, workspaces and history. Agents keep running when every client disconnects.
• Clients connect to one or more daemons: the desktop app, the web app served by the daemon, the Android app and the frogg CLI.

The desktop app does not include a daemon. Install the daemon first, even if it is on the same computer.

1. Install the daemon

Linux / macOS

curl -fsSL https://frogg.app/install.sh | bash

The script:

• downloads the self-contained daemon bundle (Node runtime, daemon, CLI, web app) for your platform from GitHub releases and verifies its SHA-256,
• installs it to ~/.local/share/frogg/versions/<version> and links frogg into ~/.local/bin,
• registers a systemd user service frogg-daemon (Linux) or launchd agent app.frogg.frogg-daemon (macOS) listening on 0.0.0.0:9999 with the web app enabled,
• waits until the new daemon reports healthy.

Re-running it upgrades in place. On Linux, keep the daemon running after you log out:

sudo loginctl enable-linger "$USER"

The service inherits the PATH of the shell that ran the installer. Install your agent CLIs first so the daemon can find them.

Windows

There is no Windows install script. Download frogg-<version>-win-x64-daemon.zip (or win-arm64) from the latest release, unpack it, and run:

.\bin\frogg.cmd start
.\bin\frogg.cmd install-service   # start at login (scheduled task)

Windows daemon installs have not had the same validation as Linux and macOS.

Docker

curl -fsSL https://frogg.app/install-docker.sh | bash

This runs container frogg-daemon on port 9999 with state in ~/.frogg.

Published images are out of date

At the time of writing, froggapp/frogg on Docker Hub only has 0.1.x tags, and latest points to 0.1.14. Current clients require daemon 0.6.0 or later. Build the image from source until a 0.6 image is published. See Docker.

Nix

The flake lives in deploy/nix:

{
  inputs.frogg.url = "github:frogg-app/frogg?dir=deploy/nix";
  outputs = { nixpkgs, frogg, ... }: {
    nixosConfigurations.box = nixpkgs.lib.nixosSystem {
      system = "x86_64-linux";
      modules = [
        frogg.nixosModules.default
        { services.frogg = { enable = true; openFirewall = true; }; }
      ];
    };
  };
}

See Nix for every option.

Check it:

frogg status

KEY               VALUE
Local Daemon      running
frogg Home          /home/you/.frogg
Listen            0.0.0.0:9999
Daemon Version    0.6.19
LAN Trusted       true

Providers
  Claude          available (daemon)
  Codex           available (daemon)
  OpenCode        not found (daemon)

If a provider shows not found, install its CLI where the daemon can see it, then frogg restart. See providers.

2. Install a client

Client	Get it
Desktop (Windows, macOS, Linux)	GitHub releases: frogg-<version>-win-x64.exe, frogg-<version>-mac-arm64.dmg / mac-x64.dmg, frogg-<version>-linux-x86_64.AppImage / linux-amd64.deb
Web	Already there: open http://<daemon-host>:9999/
Android	frogg-<version>-android-arm64-v8a-unsigned.apk from releases. See mobile
CLI	Installed with the daemon. See the CLI reference

Release coverage

Not every release carries every platform. Development releases can include only Windows, the Linux daemon and Android. If an asset is missing, use the most recent release that has it; the release notes say what was built.

macOS builds are not notarized. On first launch, open the app from Finder with Control-click → Open, or allow it in System Settings → Privacy & Security. Windows builds may be unsigned; SmartScreen then asks you to confirm.

3. Connect

Continue with connect and pair.

Uninstall

curl -fsSL https://frogg.app/uninstall.sh | bash            # keeps ~/.frogg
FROGG_PURGE=1 bash <(curl -fsSL https://frogg.app/uninstall.sh)  # also deletes ~/.frogg

For Docker, run uninstall-docker.sh from the release assets.