Clients
Clients
How the app, CLI, daemon, and external MCP clients interact with Happier.
Happier has multiple client surfaces that can all interact with the same server and account.
Use this section to understand which surface does what:
- App (
@happier-dev/app): the desktop, web, and mobile UI for sessions, devices, approvals, and settings. - CLI (
@happier-dev/cli): the scripting and operator client for install/auth/server profiles plus session control. - Daemon: the background process that keeps remote session control available without an open terminal.
- Happier MCP: the external MCP server you run from the CLI so other MCP hosts can control Happier sessions and actions.
All of these clients reuse the same core control plane:
- the same authenticated account/server selection
- the same canonical action catalog
- the same per-surface action settings
- the same approval flow when an action is configured as approval-gated
That is why session control, action discovery, approvals, and execution runs can appear consistently across the app, CLI, session agents, voice, and external MCP hosts.
For the most common user-facing flows:
- CLI for install/auth/server selection
- CLI sessions for create/list/send/resume/attach/manage
- Happier MCP (external) for editor/agent automation
- MCP host setup for privileged host configuration
If you’re looking specifically for background operation and service installation, see Daemon.
For server selection, profile switching, and multi-server behavior, see Features → Multi-server.