bodek_

THE TERMINAL, WITH FOLLOW-THROUGH.

Stay in the terminal.
Stay in command.

Your agent is working. You’re in the loop. Follow the tools, inspect the changes, and make the call—with Odek’s power at your fingertips.

Get Bodek Take a closer look

Go + Bubble Tea / MIT licensed / Powered by Odek

01 / THE WORK, IN VIEW

A clear head.
A capable terminal.

Live steps. Readable results.
Details when you want them.

~/workspace/paymentsEmber Dark / 120 columns
Bodek in Ember Dark: a sample checkout review with plan progress, shell test output, an assistant reply, and the composer.
~/workspace/paymentsEmber Light / 120 columns
Bodek in Ember Light: a sample checkout review with plan progress, shell test output, an assistant reply, and the composer.
~/workspace/paymentsHigh Contrast / 120 columns
Bodek in High Contrast: a sample checkout review with plan progress, shell test output, an assistant reply, and the composer.
~/workspace/paymentsClassic / 120 columns
Bodek in Classic: a sample checkout review with plan progress, shell test output, an assistant reply, and the composer.

Actual Bodek renderer · Synthetic example session · Open a theme at full size.

/themeMake it feel like home.
Ctrl + E

Quiet on the surface.
Deep on demand.

Keep the transcript calm. Expand reasoning and tool output when you need the full picture.

Ctrl + K

Find your next move.
Keep your momentum.

Search commands, sessions, models, and drawer tabs from one keyboard-driven palette.

Alt + A / D

Read the action.
Make the call.

Review Odek’s approval requests in place. Approve or deny explicitly; friction prompts keep their extra confirmation.

02 / FIVE WHYS

Power is useful.
Clarity is essential.

Your terminal is already where the work happens. Bodek gives the agent a place in that workflow.

Explore every feature ↗
  1. 01

    WHY STAY IN THE TERMINAL?

    Keep your hands
    where the work happens.

    Navigate turns, switch models, queue prompts, and return to a session with the keyboard. Launch a local engine or attach to one you already run.

  2. 02

    WHY A CALM INTERFACE?

    Attention is part
    of the budget.

    Compact tool rows and turn receipts make progress easy to scan. Details expand on demand, and scrolling back to read doesn’t surrender your place to incoming output.

  3. 03

    WHY STRUCTURED RESULTS?

    Confidence
    needs receipts.

    Inspect diffs, test verdicts, and per-tool durations. Sub-agent chips show who is working and who failed. Missing success metadata stays neutral; prose alone never earns a green check.

  4. 04

    WHY A SEPARATE FRONT-END?

    A richer terminal.
    A focused engine.

    Bodek brings the Bubble Tea interface. Odek owns tools, memory, sandboxing, and execution policy. Presentation dependencies stay in the client; security decisions stay with the engine.

    See the integration contract ↗
  5. 05

    WHY OPEN SOURCE?

    Read both sides
    of the connection.

    Trace how Bodek presents an action and how Odek enforces its boundaries. Both projects are MIT licensed, with source you can inspect, modify, and build yourself.

    Inspect Bodek ↗ Inspect Odek ↗

ONE ENGINE. YOUR CHOICE OF INTERFACE.

Odek does the work.
Bodek keeps it in view.

Use your existing Odek provider configuration, sessions, and tools. The terminal connects to the same engine as the Web UI.

Meet the engine ↗
bodekterminal interface

↕ WebSocket · live events & decisions

odek servetools · memory · sandbox · policy

03 / MAKE YOUR NEXT MOVE

One command.
Back in your flow.

Install Odek and Bodek, configure your provider,
then choose how you want to work.

Installation guide ↗Download Bodek ↗Prebuilt Bodek binaries for macOS, Linux, and Windows.

Start here. Build from here.

Starts Odek’s server and opens a fresh session in the current directory.

bodek

Pick up the thread.

Continue this directory’s last session instead of starting fresh.

bodek --resume

Your engine is already running.

Replace the example URL with the full token URL printed by your Odek server.

bodek --url 'http://127.0.0.1:8080/?token=YOUR_TOKEN'

Bodek is the front-end and needs the Odek engine. Provider keys and agent configuration stay with Odek. Bodek settings ↗

bodek_

Keep the power.
Find your focus.

Your terminal is ready ↗