Your agents. Your machine.
From anywhere.
Run autonomous AI agents on your machine. Monitor them from any device through P2P encrypted connections the server can never read.
Built different
Not another cloud platform. Botster runs on your machine. The server only exists to negotiate encrypted handshakes between your devices.
Zero-Knowledge Architecture
Keys exchanged offline via QR code. The server relays encrypted blobs it can never read. Not "we don't look" — we can't.
Multi-Agent Management
Run 20+ agents simultaneously, each in isolated git worktrees. Manage from the TUI or your browser.
Plugin System
Extensible architecture. GitHub is a first-party plugin — @botster triggers agents automatically.
Local-First Execution
Agents run on your hardware. Keys live in your OS keychain. No cloud execution, no vendor lock-in.
Agent Accessories
Configure accessory processes per agent with port forwarding. Preview a web app your agent is building — tunneled over the same E2E encrypted WebRTC connection, so only you can access it.
Direct Push Notifications
Push notifications are sent directly from your machine to your browser. Our server is never in the path — the CLI sends encrypted Web Push messages straight to the push service, bypassing Botster entirely.
Privacy model
The server sees nothing
Offline key exchange
Encryption keys are shared via QR code using URL hash parameters. They never touch the server — not in transit, not in logs, nowhere.
Encrypted signaling
The server's only job is negotiating handshakes — and even those are encrypted blobs it relays without any ability to read.
P2P data channel
After the handshake, connections are direct P2P. Data is encrypted with vodozemac — the Matrix Foundation's independently audited Rust implementation of Olm — on top of WebRTC encryption, so even TURN relay servers see nothing.
No trust required
The server cannot decrypt your data, even if compromised. Privacy by architecture, not policy.
Device-direct push
Push notifications go straight from your CLI to the browser push service. Botster's server never sees when, what, or who you notify.
How it works
Install the CLI
Download the binary and pair your device in seconds. Keys are stored in your OS keychain automatically.
Assign work
Create agents from any browser, the TUI, or via @botster on GitHub.
Monitor from anywhere
Watch agents work in real-time through your browser or phone. E2E encrypted, always.
Agents (3) * 10s V:-
> fix-auth-flow >:8080
update-api-docs
refactor-payments >:3000
fix-auth-flow [Ctrl+P | Ctrl+J/K | Shift+PgUp scroll]
bash-5.2$ claude --prompt "$BOTSTER_PROMPT"
✓ Read app/controllers/sessions_controller.rb
✓ Read app/models/user.rb
Fixing token refresh logic in sessions#create...
Writing to app/controllers/sessions_controller.rb
TUI with real-time agent output · Ctrl+J/K to navigate agents
Ready to run agents locally?
No cloud execution. No data collection. Just your machine, your agents, your control.