The multi-device control room to orchestrate teams of 100+ coding agents
From your phone, desktop and browser.
Claude Code, Codex, OpenCode, Pi and more, working together and in parallel on your own machines.
Sessions can spawn subagents across agents: e.g. Claude asking Codex for a review, or Codex delegating work to Claude subagents. Switch agents mid-session. Approve, steer, review and commit from wherever you are.
Open source · Self-hostable · End-to-end encrypted
Latest Happier project update
Get started
1. Install on your computer
The desktop app is the recommended way in: it sets up the CLI and the daemon for you.
macOS/Linux:
curl -fsSL https://happier.dev/install | bash
Windows:
iwr https://happier.dev/install.ps1 -useb | iex
If you specifically want the npm package instead: npm install -g @happier-dev/cli (CLI docs).
One command installs the CLI and the daemon on the remote host (release-signature verified) and registers it as one of your machines:
happier machine setup --ssh user@host
To sign the remote machine in without a browser on its side, run this from a machine where you are already signed in:
happier auth pair-remote --ssh user@host
Headless alternative on the remote host itself: happier auth login --no-open --method web prints an authorization URL you approve from any browser. Machines and the daemon
You sign in from the app, or on first run.
2. Add your phone
Sign in with the same account and your sessions, machines and settings are already there.
3. Start a session
In the app → Press New session, pick the machine, the folder and the agent. No terminal needed.
Or in the terminal, from any project folder:
happier # Claude Code
happier codex # Codex
happier opencode # OpenCode
Either way, the session shows up everywhere at once: keep typing in the terminal, follow along and approve from your phone, review in the browser. happier --help lists the other agents and commands.
What you can do
Also in the box
- Session handoff. Move a live Claude Code or OpenCode session to another machine and bring the working tree along if you want it. Session handoff
- Session sharing. Invite someone with view or edit access, or publish a read-only public link. Session sharing
- Happier as an MCP server.
happier mcp serve lets any MCP host create sessions, send messages and run session actions. Happier as an MCP server · CLI
- MCP servers, configured once. Use them with every agent on every machine. MCP servers
- Add a machine over SSH from the app or the CLI. Machines and the daemon
- Self-hosting. The self-hosted relay runs the same apps, encryption and features. Self-hosting
- End-to-end encryption. Content is encrypted on your devices by default. Security
Step-by-step guides live at guides.happier.dev.
How Happier works
Phone Desktop Browser
│ │ │
└────────────────┼────────────────┘
│
▼
Happier relay (hosted or yours)
syncs end-to-end encrypted sessions
between your devices and machines
│
▼
Your machines (laptop, desktop, VPS, dev box)
the Happier daemon starts and manages
agent processes where your code lives
│
▼
Claude Code · Codex · OpenCode · Pi · ...
each agent talks to its own model
provider directly
The relay stores and forwards content it cannot read: session content is encrypted on your devices before it reaches the server. The server only processes what routing needs, such as session ids, timestamps, turn status and usage metadata. Your agents keep talking to their model providers directly.
Self-hosting
Run your own relay with one command:
happier relay host install --mode system
This installs and updates a managed relay service on the current machine. For a remote host: happier relay host install --ssh user@host --mode system.
The self-hosting docs (also reachable at happier.dev/self-host) cover the details, with Docker and Proxmox as alternatives.
Security
- Content is end-to-end encrypted by default. Code, prompts, messages and transcripts are encrypted on your devices before they ever reach a server. Encryption
- The server processes routing metadata. Session ids, timestamps, turn status and usage metadata are visible to the relay so it can sync your devices.
- Self-host operators choose their storage policy. A self-hosted server can be configured with other storage policies for its deployment. Server encryption settings
- Model traffic stays with your agents. Each agent talks to its own model provider directly.
More in the security docs.
Downloads
Release notes live in the changelog.
Release channels and nightly builds
Everything above installs the stable channel. Two faster channels ship
ahead of it, and they install side by side (happier, hprev, hdev), so
trying one never breaks your stable setup:
- preview: new features land here first, ahead of stable.
- dev: nightly builds of the latest changes. Can contain partial commits
and can break at any moment.
Preview (macOS/Linux, then Windows):
curl -fsSL https://happier.dev/install-preview | bash
iwr https://happier.dev/install-preview.ps1 -useb | iex
Dev:
curl -fsSL https://happier.dev/install-dev | bash
iwr https://happier.dev/install-dev.ps1 -useb | iex
Then run hprev or hdev instead of happier. If you want happier
to map to your dev lane, add alias happier='hdev' to your .bashrc/.zshrc.
On dev you must run everything from the dev releases (CLI, app, daemon and
server): the hosted cloud (cloud.happier.dev) runs stable, so preview and dev features may not work
against it, and dev has no hosted web app (self-host the dev server to use
the dev web UI).
Mobile and server dev builds:
How channels map to release tags and how each install method updates:
docs.happier.dev/releases/updates.
Community and contributing
Happier is built in the open, and it grows through real feedback. If something feels broken, missing or awkward, we want to hear about it.
A clear issue is often worth more than a pull request: say what you did, what you expected, and what happened instead.
Why “Happier”?
We originally started as contributors to Happy, submitting fixes, improvements, and new features upstream.
We were using it daily for work and genuinely loved the concept.
Over time, we realized that our own needs required faster iteration that we could not comfortably explore within the main project.
So we started building them for ourselves.
After weeks of refining, fixing, and extending the foundation, we decided to share Happier so others could try it, use it, and help shape what comes next.
Happier is about exploring a faster-moving, more collaborative direction, while remaining deeply grateful for the foundation Happy provided. We loved and still love Happy. ❤️ Happier would not exist without it.
Not affiliated with or endorsed by Anthropic, OpenAI, or Google.
