bodek.

The terminal for the odek agent.

bodek streams everything odek already speaks — reasoning, tokens, tool calls, approvals, sub-agents — into a fast Bubble Tea TUI over one WebSocket. The engine does the work; bodek renders it. New to odek? It's the agent — it plans, calls tools, and asks before acting.

bodek running in a terminal: a live odek session with the transcript — user prompt, reasoning, tool steps, and the agent's reply — and the composer at the bottom.
# once installed — chat. bodek spawns (or attaches to) odek serve $ bodek

Installation lives in one place: the odek Getting Started guide — engine, provider key, and this TUI, end to end. Prefer a binary? Grab one from Releases for Linux, macOS, or Windows.

Why bodek

  • One protocol, zero duplication. odek serve already speaks a public WebSocket protocol — bodek renders it. Tools, sandbox, approvals, skills, and memory keep running inside odek, untouched.
  • Full fidelity. Turns arrive exactly as the engine emits them: thinking, tool steps, and replies, in order — not a summary.
  • Upgrade odek, get it free. New engine behaviour appears in the TUI with no bodek update.

Highlights

  • Live turns — reasoning, tool calls, and replies interleave as they stream.
  • Sub-agents, readable — a chip per task; drill in for its steps and artifacts.
  • Approvals inline — allow or deny with one key, expiry countdown included.
  • Everything else in a drawer — skills, memory, tools, config, jobs.
  • EMBER themes — four looks via /theme, or --plain for pipes.
  • Resilient — spawns or attaches to odek serve, reconnects and resumes, wakes on background jobs.