v0.9.26 · two clients · one daemon

Reach your alpi / from any device.

Once a daemon is running on your laptop, home server, or umbrel, the desktop and mobile apps connect to it as paired clients over Tailscale. Same profiles, same memory, same approvals — just the surface differs.

Desktop ↓ Mobile ↓
desktop · macOS · Linux · Windows

The window you keep open all day.

Native Tauri shell with one job: be the most pleasant way to talk to your alpi. Multi-daemon picker (local + every remote you've paired), per-profile chat, workgroup viewer, sessions sheet, native approval modal for caution commands, model override per turn.

  • Multi-daemon. Switch between local, home server, and any paired remote alpi with one click. Each connection holds its own profiles, workgroups, and session state.
  • Native approvals. When the agent wants to run something risky (`rm -rf`, `sudo`, force-push…) the modal pops with command preview, severity, and four choices: once / session / always / deny.
  • Workgroup-aware. Transcript, roster, briefing, tasks, post composer. Same surface ALP.3 workgroups have on every client.
  • Realistic loading. Skeletons match the row geometry so first paint doesn't ghost the layout.
  • Source available. desktop/, BSL-1.1.
Download for macOS →

v0.3.75 · macOS, Linux and Windows builds in desktop releases

mobile · iOS + android

Your alpi, in your pocket.

Pair your phone with a daemon by scanning the QR from desktop or terminal. Then chat, manage workgroups, inspect tasks, and approve caution commands — anywhere you have Tailscale.

  • QR pairing. No accounts, no cloud. The daemon generates a one-time pairing token; your phone scans it and stores it in the device secure store (iOS Keychain / Android Keystore via Expo SecureStore).
  • Inbox + workgroups. Pinned profiles, segmented filters, full workgroup transcript with task markers and post composer.
  • Approvals on the go. A caution-command prompt opens a native sheet — you can allow or deny from the bus stop.
  • Biometric unlock. Face ID / fingerprint gates the app; pairing tokens stay on the device.
  • No telemetry. The phone speaks only to the daemons you paired. Nothing else.
iOS · TestFlight internal Android · internal builds

Mobile builds are in internal testing. Follow releases for the public rollout.

how this fits

The daemon is the agent. The apps are just clients.

No matter which client you use — TUI, desktop, mobile — the agent never leaves the daemon. Memory, skills, model keys, and approvals all live on the machine you trust. The apps render and forward; they never carry an LLM of their own. Run one alpi, or a network of them, and the same memory follows you across surfaces.

Install the daemon → Read the architecture →

theme