← All posts
  • #story
  • #claude-code
  • #development
  • #origin

Why I Built a Skinnable Terminal for Claude Code

· · 6 min read

I spend 8 hours a day staring at Claude Code. One day I decided it should look like something I actually want to look at.

I spend eight hours a day staring at a terminal. Claude Code, specifically — Anthropic's CLI that's basically become my second brain. And for the longest time, it looked like every other terminal on earth: monochrome text on a dark background, zero personality, zero joy.

I kept thinking about Winamp. Remember Winamp? The music player that let you skin it with literally anything — alien landscapes, anime characters, retrofuturist dashboards. The software itself was simple, but the community around skins was enormous. People shared them, rated them, competed to make the wildest ones. The skins turned a boring utility into a creative platform.

That's what I wanted for my AI terminal.

The Problem

Claude Code is incredible software. It reads your codebase, writes code, runs tests, commits changes. But visually? It's a rectangle of text. No panels, no widgets, no telemetry, no vibes. You can't even change the color scheme without editing your terminal emulator's config.

And it's not just Claude Code. Codex CLI, Gemini CLI, Aider — every AI terminal agent ships the same way. Plain text in a plain box. The tools are getting smarter every month, but the surfaces we use them through haven't changed since the 1980s.

I'm a hospitality revenue management professional by day. I'm not a frontend engineer. I'm not a designer. But I know what it feels like to stare at an ugly dashboard for 10 hours and I know what it feels like when someone finally makes it beautiful. The difference isn't cosmetic — it's motivational.

The First Prototype

MOLTamp started as a weekend experiment: wrap Claude Code's PTY in an Electron shell and inject custom CSS. That's it. A around a terminal with a stylesheet I could swap.

The first skin was terrible. I hardcoded hex colors, the panels didn't resize, the vibes banner was a static GIF that covered the actual terminal output. But when I loaded it up and saw Claude Code running inside something that looked like a Blade Runner dossier terminal, I felt something shift. I wasn't just using a tool anymore. I was in a cockpit.

What It Became

That weekend project is now MOLTamp — a skinnable cockpit for AI terminals that supports Claude Code, Codex CLI, Gemini CLI, Aider, Cursor, opencode, and Goose. It has:

  • A CSS variable contract that lets skin authors change every color, every border, every glow without touching JavaScript
  • Reactive data attributes that change based on what the AI is doing (thinking, streaming, using tools, asking for permission)
  • A widget system with clocks, weather, system monitors, music players, Live2D companions, visualizers
  • A community marketplace where people share skins, rate them, and download them
  • A skin validator that scans your CSS and tells you exactly what needs fixing — and generates an AI prompt you can paste into Claude or ChatGPT to get the fix

The whole thing is open source. The skins repo, the widget system, the visualizer engine — all of it.

Why It Matters

I don't think terminal aesthetics are vanity. I think they're a form of ownership. When you spend your entire working day inside a tool, that tool should feel like yours. Not like a generic rental. Not like everyone else's.

The AI coding revolution is making the terminal the most important window on your screen. More important than your browser, more important than your IDE. And right now, that window looks exactly the same for everyone.

MOLTamp is my answer to that. Pick a skin. Pick a layout. Make it yours.

If you're interested, join the beta. If you want to create a skin, check out the skinning guide. And if you just want to see what it looks like — scroll up. That preview on the home page isn't a mockup. It's real CSS running in your browser right now.