The way orchestrating agents should feel.
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 to Claude subagents. Switch agents mid-session. Approve, steer, review and commit from wherever you are.
Open source · Self-hostable · End-to-end encrypted
Get started · Downloads · Docs · Self-host · Discord
Happier is free and open source.
Your agents keep using the subscriptions and API keys you already have:
Claude Pro/Max, ChatGPT/Codex, API keys, or local models.
The desktop app is the recommended way in: it sets up the CLI and the daemon for you.
Prefer the terminal? Install the CLI and daemon without the desktop app
macOS/Linux:
curl -fsSL https://happier.dev/install | bashWindows:
iwr https://happier.dev/install.ps1 -useb | iexIf you specifically want the npm package instead: npm install -g @happier-dev/cli (CLI docs).
You sign in from the app, or on first run.
|
|
Direct APK stable release |
 |
 |
 |
Sign in with the same account and your sessions, machines and settings are already there.
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 # OpenCodeEither 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.
Parallel sessions, on every machine you own. Start as many sessions as you like and pick the machine, folder, agent and model for each one. Give a session its own Git worktree so parallel agents never collide, and add a new machine over SSH from the app or the CLI. Starting a session · Machines and the daemon
Subagents across agents. Any session can launch review, plan or delegate runs on another agent and read the results: Claude handing work to Codex subagents, Codex to Claude, or any other pairing. Subagents
Switch agents mid-session. Change the engine and the same session keeps going. A returning agent resumes its own thread and receives only what it missed. Continue with another agent
Hand a session to another machine. Move a live Claude Code or OpenCode session to your desktop, a VPS or a dev box, and bring the working tree along if you want it. Session handoff
Queue it, steer it. Queue messages while the agent works, reorder or edit them before they run, and steer a running turn without interrupting it. Steering · Pending queue
Review diffs, line by line. Browse your agent's changes, mark the exact lines you want addressed, and send the notes straight back: same session, or a new one. Review comments
Git from any device. Stage, commit, push, branch and open pull requests without leaving the app. Git
Files, editor, terminal. Open any file in a real editor, and drop into a live terminal on the connected machine when you need a shell. Files and editor · Embedded terminal
An inbox for what needs you. Permission requests, agent questions and unread sessions gather in one attention center across all sessions and machines, and push notifications open the exact session that asked. Inbox and approvals
A colleague you can talk to. The voice assistant follows your running sessions, answers permission requests for you, and sends the messages you dictate. Bring your own ElevenLabs key or run a local voice pipeline. Voice
Share a session. Invite someone with view or edit access, or publish a read-only public link. Session sharing
MCP, in both directions. Define your MCP servers once and use them with every agent on every machine. Happier is also an MCP server itself, so an external MCP host can spawn and drive your sessions. MCP servers · Happier as an MCP server
Your accounts, with usage in view. Link provider subscriptions and API keys once, reuse them across your machines, and monitor usage and quota where the provider exposes them. Connected services
Self-host, same features. The self-hosted relay runs the same apps, the same encryption and the same features as the hosted one. Self-hosting
Any agent that speaks ACP (the Agent Client Protocol) can be added from the settings, next to the built-in ones. Capabilities differ per agent: see the feature matrix.
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.
Run your own relay with one command:
happier relay host install --mode systemThis 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.
- 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.
| Platform | Get it |
|---|---|
| iOS | App Store |
| Android | Google Play · APK |
| macOS · Windows · Linux (desktop app) | happier.dev/download · all desktop builds |
| Web | app.happier.dev |
| CLI (macOS, Linux) | curl -fsSL https://happier.dev/install | bash |
| CLI (Windows) | iwr https://happier.dev/install.ps1 -useb | iex |
Release notes live in the changelog.
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: what the hosted cloud (app.happier.dev) runs; new features land here first.
- dev: nightly builds of the latest changes. Can contain partial commits and can break at any moment.
Install preview or dev builds
Preview (macOS/Linux, then Windows):
curl -fsSL https://happier.dev/install-preview | bashiwr https://happier.dev/install-preview.ps1 -useb | iexDev:
curl -fsSL https://happier.dev/install-dev | bashiwr https://happier.dev/install-dev.ps1 -useb | iexThen 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 runs preview, so 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:
- iOS TestFlight
- Android dev APK
- Server images: Docker Hub
happierdev/relay-server:dev· GHCR - Dev box (CLI + daemon + agents preinstalled): Docker Hub
happierdev/dev-box:dev
How channels map to release tags and how each install method updates: docs.happier.dev/releases/updates.
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.
- Bugs, with repro steps: GitHub issues
- Ideas and design questions: GitHub discussions
- News, questions and quick feedback: Discord
- Code, docs and development setup: CONTRIBUTING.md
A clear issue is often worth more than a pull request: say what you did, what you expected, and what happened instead.
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.
Built in Switzerland. MIT licensed.
Not affiliated with or endorsed by Anthropic, OpenAI, or Google.