Codex terminal: hands-on mission control.

A tiny ops-style shell wired into my site content. Explore work, read, and reach out from the same green glow I use for real tooling.

Runs fully in your browser. Type `help` to start.

Why a terminal?

I'd rather show you how I think than hide behind marketing copy. The terminal behaves like a small ops console: list posts, open retros, follow prompts. It mirrors how I design real tools—opinionated commands, readable output, guardrails that keep you oriented.

Guided contact

The `contact` flow asks goals, constraints, priorities upfront—so my first reply includes options, not more forms.

Content drill-down

Point at `blog`, `projects`, or `community` to pull up posts and retros. Everything stays in one viewport.

Command-grade UX

History, autocomplete, and CRT theming keep it fun—but the layout and prompts are designed like real tooling.

Quick start

  • Type `help` to see commands. Use `codex` to enter content mode.
  • Navigate `blog`, `projects`, or `community`. Use `ls` to list, `cat [number]` to open.
  • `contact` launches a guided brief. `back` climbs up a level.

Commands

codex Enter codex mode for content navigation.

blog | projects | community Browse content. Use `ls` to list, `cat [number]` to open.

contact Guided intake for potential work.

back / cd .. Climb up a level.

help Command reference.