Desktop app · Local-first

The sandbox runs on your machine

Use aibuddy where your work already lives. The Desktop App lets agents read files, run commands, and complete tasks inside a local sandbox, with conversations and run state stored on your device.

Download Setup guide

macOS Apple silicon + Intel Windows 10 and 11 Linux AppImage + deb

~/projects/acme-api On-device

acme-api local workspace

modified src/api/users.ts +12 −3

$ run_tests --watch 42 passed executed in local sandbox · 0 egress

SQLite · local keys sealed

Your machine, your boundary

Use Desktop when the task depends on local files, private context, or a machine you control. It keeps the same aibuddy workflow while moving execution and storage onto your device.

01
Work beside real files

Point aibuddy at a repo, folder, or local workspace instead of uploading work into a cloud runtime.
02
Keep control local

Runs, history, keys, and storage stay on the device unless you explicitly connect an external service.

Local sandbox

Tool calls run on your own machine — shell, filesystem, scripts. No round-trip to a cloud sandbox, no egress.
On-device storage

Conversations and agents live in a local SQLite database. Your work never leaves the machine unless you send it.
Encrypted keys

API keys are sealed with the OS keychain via Electron SafeStorage — encrypted at rest, decrypted only in-process.
Native filesystem

Point an agent at a real project directory. It reads, writes, and runs against your files directly.
Works offline

The app shell, history, and local tools work without a connection. Only the model call needs the network.
Same as web

One codebase, one UI. Only storage differs — SQLite on Desktop, Postgres in the cloud. Your data shape is identical.

Web or Desktop?

Same agent, different boundary

Web is the fastest place to start. Desktop is the better boundary when the work needs local files, local tools, or device-side data control.

	Web	Desktop
Sandbox	Managed cloud	Your machine
Storage	Postgres (cloud)	SQLite (on-device)
Setup	None — open a tab	One-time download
Filesystem access	Sandbox only	Native, your files
Works offline	No	Yes (except model call)
Best for	Teams, quick starts	Local repos, private data

The sandbox runs on your machine

Your machine, your boundary

Work beside real files

Keep control local

Local sandbox

On-device storage

Encrypted keys

Native filesystem

Works offline

Same as web

Same agent, different boundary

Give it one real task