This guide explains the core workflow:

1. Start a session from Happier on mobile (app or served web UI).
2. Let Happier run the session on your machine/server.
3. Continue that same session later from desktop or the CLI (attach for active sessions, resume for inactive ones).

Option A: use the served web UI (recommended for self-hosting)

If you’re self-hosting or using a custom Relay, make sure you have a reachable HTTPS URL for the UI (for example a *.ts.net URL via Tailscale Serve).

Why: browsers treat http://localhost as a secure context, but not a random LAN/Tailscale HTTP origin, and Happier relies on secure-context browser features.

Option B: use the native mobile app

If you’re using the mobile app, you’ll typically:

1. Select the correct Relay (Happier Cloud or your self-hosted Relay).
2. Sign in.
3. Ensure your machine/daemon is connected to the same Relay.

Start from mobile

From mobile (app or web UI):

1. Create a new session and choose the machine you want it to run on.
2. Send your task.
3. Leave it running while you’re away from your terminal.

Continue from the CLI on the owning machine

On the machine that owns the session:

If the session is still running

Use attach:

happier attach <session-id>

If the session is inactive

Use resume (only works when the session is vendor-resumable):

happier resume <session-id>

Troubleshooting

Mobile web UI loads but can’t connect or shows “wrong Relay”

Double-check:

• the UI is pointed at the same Relay as your daemon/machine
• you’re signed into the same account on that Relay
• if self-hosting, the URL you opened is HTTPS (not plain HTTP over LAN/Tailscale)