Every agent, one timeline
Start Claude Code, Codex, OpenCode and friends side by side. Follow each turn live: messages, tool calls, file edits and command output.

Open source · Self-hosted · Apache-2.0
frogg runs Claude Code, Codex, OpenCode and more on a daemon you host. Watch them work, answer their questions and approve their commands from your desktop, phone, browser or terminal.
curl -fsSL https://frogg.app/install.sh | bashInstalls the daemon and frogg CLI on Linux or macOS. Other options
What it is
The frogg daemon lives on your laptop, a build box or a container. It launches the agent CLIs next to your code and keeps them going. The apps are windows onto it, so you can close the laptop, pick up your phone and carry on.
Start Claude Code, Codex, OpenCode and friends side by side. Follow each turn live: messages, tool calls, file edits and command output.
Give each task its own git worktree so parallel agents never trip over each other, then review the branch when they are done.
Permission prompts reach whichever device you have in hand. Allow, deny or answer a question without walking back to your desk.
Open shells on the host right next to the agent working there, without a separate SSH session.
Run agents on a schedule or keep a heartbeat going. The daemon carries on while every client is closed.
Script agents, workspaces and schedules with the frogg CLI.
Platforms
Put the daemon wherever your code lives, then open it from any client. Every app is a free download from GitHub Releases.
One command on Linux or macOS installs the daemon as a user service and adds the frogg CLI.
curl -fsSL https://frogg.app/install.sh | bashDesktop apps connect to daemons rather than bundling one. Builds and checksums live on GitHub Releases.
Companion · voice
Companion is a real-time voice conversation that sits above your projects. It answers straight away, hands real work to your coding agents, and tells you when they finish or get stuck.
Pair your phone
Run frogg daemon pair on the host and scan the code with the frogg app. From then on the phone sees the same agents, timelines and prompts as your desktop.
The pairing page never contacts your daemon: the code carries the whole offer, and nothing is stored.
Pairing guideMake it yours
Branding is data, not a patch series. Describe your product in one brand.jsonand the build carries your name, icon, colours, app IDs, installers and update feed, while you keep pulling upstream frogg.
frogg-app/frogg on GitHubbrands/your-app/brand.json
Install the daemon, connect a client, start an agent.