decli documentation

Mac-first developer desk backup and restore — then the ecosystem that rides on it.

The wedge

Great Mac backup and restore is how decli earns trust. Pack this machine; recover on a new MacBook; doctor is green; you code the same day. Integrations, AI, Google Workspace, and platform APIs expand that foundation — they do not replace it.

decli is an AI-native command interface for Apple Silicon Macs: plain English → real commands, desk state (Caddy, Postgres, iTerm, ~/dev), and a web console on *.lvh.me / *.decli.dev.

Golden path

# On the source Mac — encrypted desk pack
decli desk pack --to icloud
# or: decli desk pack --to aws | gcs | gdrive | s3:NAME

# On a new MacBook Pro
curl -fsSL https://decli.dev/install | sh
# then:
decli desk recover --from-archive ~/path/to/desk-….desk.enc --execute --restart-iterm
decli desk doctor

What we backup (desk only)

Not Time Machine. Not Arq for Photos. The developer desk: global Caddy, Homebrew PostgreSQL, iTerm, SSH, tooling inventory, soft Docker notes, playbook + repo list. Consumer Mac state stays with Apple iCloud / Migration Assistant.

Guides

Mac desk backup & restore — the product core
Destinations — iCloud, AWS, GCS, Drive, S3-compatible
Install · CLI · iTerm → Blink
Session environment — device fleet + air quality metadata
Google platform — Workspace auth + GCP APIs that run the platform
Architecture — how decli is built, managed, and improved recursively
CLI bridge & auth

Settings vs integrations

Settings	Integrations
How decli behaves (AI active provider, NL, session env)	What it connects to (GitHub, Google, destinations, Slack)
Account prefs after Workspace login	OAuth apps, API keys, buckets you own

Developer resources

Local docs: https://docs.decli.dev · Production: https://docs.decli.dev