Codex Skin vs Terminal Theme: Inside the Bearded Family

--
title: "Codex Skin vs Terminal Theme: Inside the Bearded Family"
description: "A bearded codex theme starts its life somewhere else."
tags: ["codex", "skin", "terminal", "theme"]

canonical_url: https://awesomecodexskin.com/blog/bearded-family-codex-skin-vs-terminal-theme/

A bearded codex theme starts its life somewhere else. Bearded Theme Ports, the collection vufly maintains, carries 50+ variants of classic terminal palettes, and one of them landed in this index as Tokyo Night (CLI): the same #1A1B26 night blue you know from the emulator, shipped as a .tmTheme file and activated with /theme Tokyo Night.

What a terminal theme controls. Your emulator reads a palette file and colors 16 ANSI slots plus foreground, background, and cursor. That's the whole surface.

What changes after the port to Codex. A Codex skin isn't applied by your terminal. It's read by Codex itself, so it colors everything the tool renders: prompts, diffs, tool-call output, status lines, streaming text.

Four ports of one palette. The family neatly shows how theme family migration drifts. All four trace back to the same Tokyo Night design, and none of them are byte-identical:

• Tokyo Night (CLI) is the Bearded port: a .tmtheme file for Codex CLI, catalogued under dark-midnight.

Family ports or one-off skins. The bearded series codex approach buys you portability. Palettes like Tokyo Night, Monokai Stone, and Solarized have been ported to dozens of tools, so whatever editor or terminal you pick up next probably has an entry waiting.

The part worth keeping: Start with Tokyo Night (CLI) since it's the most faithful to the original, then compare it against the ychampion variant to feel how much a port can drift. Full write-up is on the source blog.