sandbox · example data only · not your workspace
← all scenarios

Desktop App Pairing Demo

Download desktop → pair workspace → analyze local repo.

End-to-end pairing flow + the first local capability surface.

Steps
5
Est. time
~6 min
Audience
public
Reviewed
2026-05-23
engineer · Engineer Workspace

read first

Desktop Install— macOS / Windows / Linux build + first pairing.
Permissions ModelScanning Model

data flow

scenario architecture


   web /admin/api-keys ──mint vxlk_live_*──▶  paste in desktop
                                                  │
                                          keyring (OS keychain)
                                                  │
                                          Authorization: Bearer
                                                  │
                                          v1 API surface
step 1/5·No approval needed

Download desktop app

macOS, Windows, Linux builds available.

Axiom Agent
⌘ 3 awaiting

approvals queue · live · polling every 5s

paired · ws_acme_prod · alice@acme.com
rundecide
ai_coding · ck98zxm9q…
✓ approve✗ reject
deploy_pipeline · ck98zw3py…
✓ approve✗ reject
infra_update · ck98ztr5h…
✓ approve✗ reject
Tray badge
3 awaiting
Notifications
enabled
Offline queue
0
Last vote
14s ago
nativeHide-to-tray on window close · OS notifications on new arrivals · quick-approve from the tray submenu · offline vote queue with 30s back-off retry · window state restored across launches.
Tauri 2 · React 19 · ~95kB gzippedmenubar · notifications · offline-vote queue · hide-to-tray

Desktop is just an API key

Pairing the desktop = pasting a vxlk_live_* key with the scopes you want it to have. The webview never sees plaintext credentials; the key lives in OS keychain via the keyring crate and is read on every Authorization header build.

expected result

Installer downloaded.

platform route

/download →

read more

Desktop Install

engineering principle

Pairing = pasting an API key. There's no separate auth flow, no special pairing protocol. The desktop is a thin Tauri shell around the same v1 surface you'd hit from a CI runner, with the OS keychain caching credentials.

Platform reference →Architecture overview →← Back to all scenariosSet up your real workspace →