Skip to main content

The Problem: Tab Explosion


The Solution: Extension-Based Grouping

Extension = Renderer = CodexMono Application: Files with the same extension use the same renderer. This makes tab reuse semantically correct, not just efficient.

How Smart Reuse Decides


Smart Reuse in Action

Scenario A: Same Extension

Scenario B: Different Extension, Tab Exists

Scenario C: No Matching Tab

Extension Grouping: Files are grouped by extension because the extension determines the renderer. This aligns with how developers mentally categorize files.

Tab History: Browser-Like Navigation

Git-Style Branching: Navigate back, open new file, forward history is discarded. This prevents confusing non-linear navigation.

Editor Protection

Editor Mode Preservation: If you’re editing a file, opening a new file always creates a new tab. This prevents accidental data loss.

Closing Tabs: Graceful Cleanup

Graceful Degradation: When the last tab closes, the system returns to initial state. Panel hides, V button disables, ready for next session.

Decision Matrix


Browser vs VariableMD


The Brick Guarantee

The Brick Guarantee: Whether a tab is reused or newly created, CodexMono (600-unit monospace font) ensures identical rendering. Extension-based grouping preserves this consistency.

Key Insights


  • CodexMono: The fundamental monospace font that enables consistent rendering
  • Monokinetics: Unified Human + AI visual experience
  • The Brick: CodexMono as the fundamental rendering unit
  • SMPC/OFAC: Simplicity principles guiding the design