Happier Docs
Features

Multi-server

Use multiple Happier servers from the same app and CLI.

Happier supports using multiple servers at once (for example Happier Cloud + personal self-host + company self-host).

Core model

  • A server profile is a saved API/webapp target.
  • Auth is scoped per server. Signing into server A does not sign you into server B.
  • Daemon/runtime state is also scoped per server, so one machine can run multiple daemon instances safely.

If you use the same identity provider (for example GitHub) on two servers, they are still separate server accounts.

App and web UI

Add and switch servers

  • Open Server settings to add, select, rename, or remove saved servers.
  • On web, server selection can be set per-tab or as a device default.
  • If a connect/notification link targets a different server, Happier switches to that server before continuing.

Installers and setup commands can print one-click links:

  • happier://server?url=<ENCODED_SERVER_URL>
  • <WEBAPP_URL>/?server=<ENCODED_SERVER_URL> (preferred)
  • <WEBAPP_URL>/server?url=<ENCODED_SERVER_URL>&auto=1 (legacy)

These prefill server settings so users do not have to paste URLs manually.

CLI server profiles

Persisted profiles

Use server profile commands:

happier server list
happier server current
happier server add --name company --server-url https://api.company.example --webapp-url https://app.company.example --use
happier server use company
happier server remove company
happier server test company

Per-command targeting (no default switch)

Target a server for one command only:

happier --server company auth login
happier --server personal daemon status

You can also pass explicit URLs for a single invocation:

happier --server-url https://api.company.example --webapp-url https://app.company.example auth login

Multiple daemons on one machine

Install/start one daemon service per server profile:

happier --server personal daemon service install
happier --server company daemon service install

Check status:

happier daemon status --all
happier --server personal daemon service status
happier --server company daemon service status
  1. Add/select the target server.
  2. Sign in on that server (app/web). If you already use Happier on another device, sign in with that same account.
  3. Connect terminal/daemon for that same server.

For end-to-end walkthroughs, see Onboarding and Proxmox deployment.

FAQ and gotchas

Happier stores the pending terminal-connect request, sends you through sign-in/create account, then returns you to terminal approval automatically.

I signed in with the same provider on two servers. Why do I see different data?

Accounts are server-scoped. The identity provider can be the same, but each server has independent account/session state.

I switched servers and my previous sessions are gone.

That is expected when the previous sessions belong to another server. Switch back to that server profile to see those sessions again.

Git & File Browser

Review repository changes in-session and use experimental Git write operations safely.

Friends

Add friends, share sessions with people you trust, and discover users by username.

On this page

Core modelApp and web UIAdd and switch serversConfigure-server linksCLI server profilesPersisted profilesPer-command targeting (no default switch)Multiple daemons on one machineRecommended flowFAQ and gotchasI opened a terminal-connect link while logged out. What should happen?I signed in with the same provider on two servers. Why do I see different data?I switched servers and my previous sessions are gone.