Pneuma is a workspace where coding agents edit files directly and humans watch the work happen. Files stay the canonical collaboration surface — not abstracted away. Viewers are live players for agent output (a deck, a board, a paper), so humans can intervene in the UI when it matters and stay out of the way the rest of the time.
Four pillars
The whole product surface composes from four orthogonal ideas.
- Visual environment — live players for agent output with optional human participation
- Skills — domain knowledge + seed templates + session persistence per mode
- Continuous learning — an evolution agent extracts preferences across sessions
- Distribution — marketplace, publishing, forking a mode like a fork of a repo
Product principles
Three non-obvious calls that shape every choice in the codebase.
- The agent edits files; the viewer renders them. No state hidden from the filesystem.
- Each mode declares its own viewer + skill. The runtime is a shell, not a monolith.
- Backends (Claude Code, Codex) plug in through a normalized protocol. Swap at startup, not mid-session.
What ships today11 built-in modes across three axes
- webcraft — web design with Impeccable.style intelligence
- kami — paper-canvas typesetting on locked A4/A5/Letter
- slide — HTML presentations on a 1280×720 canvas
- doc — live-preview markdown documents
- draw · diagram — Excalidraw + draw.io inside the viewer
- mode-maker · evolve — create new modes; learn from past sessions
"Files remain the canonical collaboration surface and are not abstracted away." — the line we keep coming back to when designing anything new. A mode earns its viewer by rendering what's on disk, not by adding a database.