Self-host personal gateway
Start from the desktop app, or run okbot serve headless. Assistants, sessions, and memory live under ~/.okbot on the gateway host.
At a glance
Client, personal gateway, runtime computers.
One client can save and switch among many personal gateways (one active at a time); one gateway can register many runtime computers. Keep the gateway running for continuous service; send work to those registered machines.
Many runtime computers
Local is always available; register remote sandbox-agent hosts under Settings → Computers and route tools to one of them.
Members collaborate
In 1:1 chats, assistants can ask roster peers for help (Mesh). For multi-role parallel work, form a Squad with captain orchestration.
Cross-session memory and upkeep
Important facts are stored in memory across chats; after a turn, “Wrapping up” updates persona (SOUL.md), skills, and memory for the next prompt.
BYO models · security · observability
Bring your own model providers; path/command soft guards (not an OS sandbox) plus optional human approval (most tools auto-allow out of the box; MCP always asks); light usage analytics and message tracing.
Marketplace and packs
Install assistants and connectors from the in-app Marketplace; export and import persona and skills with .okbot packs.
Capabilities
Models, Marketplace, and assistant packs.
Bring your own model providers; install assistants and connectors from Marketplace; export and import persona and skills with .okbot packs.
01
Personal gateway
okbot serve as a headless host; optional LAN Web UI.
02
Many computers
Local tools by default; register remote sandbox-agent hosts under Settings → Computers.
03
Export / Import assistant
.okbot packs include persona and skills (name, avatar, SOUL.md, skills).
Named assistants
Name, avatar, persona (SOUL.md), private skills and memory; steer mid-turn, continue after Stop; @ mentions.
Skills & upkeep
Hot-reload skills; post-chat “Wrapping up” silent upkeep — next turn picks it up.
Marketplace & MCP
In-app Marketplace for assistants and connectors; MCP master switch on by default (every call still needs approval; Marketplace connector presets still need enabling individually).
Gateway host
Data lives on the gateway host.
Assistants, sessions, and memory live under ~/.okbot on the active gateway host. Model APIs are ones you configure.
Data dirGateway host ~/.okbot
DesktopmacOS / Windows / Linux
Gatewayokbot serve · self-host
ModelsBYO providers
Personal Agent
Desktop client connects to a personal gateway, one runtime.
Security protection
Path and dangerous-command soft guards (not an OS sandbox); optional human approval and auto-approval rules.
Light observability
Usage analytics and message traces for debugging.
Marketplace
Assistants / connectors; share .okbot packs via export/import.
macOSWindowsLinuxGet builds from GitHub Releases; early builds may be unsigned.
Get started
Add a provider, create an assistant, start chatting.
Download the desktop app, or read the install guide first. Add a model provider, then start chatting.
Bring your own models. Start chatting.