← All work

OkenOS.
Local-first AI operator cockpit.

A calm operator cockpit for running a portfolio of businesses with AI agents, built from scratch, owned outright, and engineered around flat-rate subscriptions.

Role
Creator system architect · engineer
Delivery
Localhost 127.0.0.1:4400
Velocity
3 days to a functional v1
Scale
13,500 lines · 47 API routes
The Personas screen in OkenOS, showing the agent roster and which model does which job

Personas · the agent roster and its routingFig. 01

Overview01

OkenOS is a personal control center built to manage multi-brand workflows, agent fleets, and execution logs from a single dashboard.

Instead of relying on fragmented web GUIs or expensive metered API usage, OkenOS routes tasks locally through flat-rate AI subscriptions, serving as the command bridge for autonomous development and operations.

Key architectural decisions02
01

Subscription-first cost engineering

Built specifically to run on flat-rate plans (Claude Code on Max, ChatGPT Pro via Codex CLI) rather than metered API keys. Ideation and speccing are handled by lightweight models, reserving premium model compute exclusively for execution.

02

Deterministic intelligence (the code counts, the model explains)

Features automated systems like Dream Review that analyze weekly logs and error repetition. Deterministic evidence packs are generated directly in code so models interpret verified metrics without hallucinating data.

03

Local-first and zero-database storage

Reads directly off disk using plain JSON (oken-data/*.json) and connects straight to your Obsidian markdown vault ([[wikilinks]]) with 3D graph visualization. Zero external telemetry or third-party database dependencies.

04

Multi-agent orchestration

Houses specialized operational views, including an agent-driven Kanban board, structured goal decomposition, and multi-model roundtables (Claude, GPT, Kimi) working off shared workspace context.

On a phone03

One dashboard, whichever screen is nearest.

The cockpit runs at 127.0.0.1:4400 and the layout follows the viewport, so the same roster, board and logs are legible on a phone on the same network as they are on the desk.

The Personas roster in OkenOS on a phone

Personas on a phoneFig. 02

Built with04

Framework & UI

Next.js 15
React 19 · TypeScript 5.7
Tailwind CSS

Server architecture

Custom node server.mjs
Dual WebSockets
/api/pty & /api/agent

Embedded shell

node-pty
@xterm/xterm
Integrated terminal

Agent runtimes

@anthropic-ai/claude-agent-sdk
Codex CLI
OpenRouter

Data engine

Local JSON
Markdown filesystem
No database