Local-First Desktop Agent Workspace Architecture
How openaiko 0.1.1 organizes local project indexes, the 15.38 MB native Rust daemon, WASM P3 plugins, and explicit BYOK data boundaries on disk.
When building an AI workspace for developers, how data and context are stored defines the trust boundary of the tool.
Why local-first matters
Most daily engineering work happens inside existing local workspaces. Forcing repositories and conversation logs into centralized cloud storage increases sync overhead and blurs the boundary between local files and outbound network calls.
openaiko keeps project indexes, Spaces, and session history on your local disk under ~/.openaiko/ (SQLite and local files):
- Native Rust daemon: A 15.38 MB Release arm64
openaikoddaemon runs locally to manage workspace indexing, multi-agent sessions, and the WASM P3 plugin runtime. - Non-destructive project mounting: Attach existing local directories as Spaces; removing a project from openaiko only detaches the workspace reference and never deletes source files on disk.
- Three-layer hot updates: The 5.40 MB L3
renderer.tar.gzbundle hot-reloads UI updates without restarting the app when the Electron base and main process hash match, automatically falling back to L2 Blockmap differential updates otherwise. - Explicit model boundaries: Local storage does not mean zero network traffic. openaiko uses bring-your-own-key (BYOK) direct calls to the model providers you configure, so you stay in control of what context leaves your machine.
Restraint and verifiable facts
In the 0.1.1 stable release for macOS (Apple Silicon), we focus on delivering a dependable local core first and documenting only capabilities verified in real builds.