Control Claude Code Without Losing the Thread

See It

Real screenshots, generated from the app with invented data. The repository has the full set, dark and light.

All screenshots on GitHub →

The Problem

You run Claude Code. You get 400 lines scrolling at machine speed. 90% is noise. The 10% that matters — a file touched out of scope, a missing translation, an unexpected behavior — disappears in the scroll.

Pragma fixes this.

How It Works

1. 1

   You write a prompt.

   Pragma injects the Pragma Protocol into Claude Code via --append-system-prompt. The session starts.

2. 2

   Claude works.

   Pragma reads the structured NDJSON stream line by line and atomizes every event: file touches, diffs, tool calls, errors, notes.

3. 3

   You navigate, not scroll.

   Atoms appear in a live feed — typed, color-coded, collapsible. The center panel tracks the current phase. You approve, confirm, or stop.

Pragma uses --output-format stream-json --verbose. Nothing is intercepted at the shell level — it’s Rust parsing a structured protocol.

Atom Types

Everything Claude does maps to one of these atom types. Each renders differently in the stream.

File type colors

FILE_TOUCH and DIFF use the file type color, not the atom type color.

Session Phases

Pragma doesn’t just stream atoms. It tracks where Claude is in the task and surfaces the right UI for each phase.

1. Idle Configure prompt, working directory, model, attachments.
2. Analyzing Claude processes the task. Analysis text builds in real time.
3. Awaiting Answers optional Claude has blocking questions. You answer or skip.
4. Awaiting Approval The plan (numbered steps) appears. Approve, modify, or switch to a stronger model — past five steps, Pragma proposes Opus and Fable.
5. Running Steps execute. Step progress visible. Stop anytime.
6. Awaiting Confirmation After each step: review, continue, or finalize early.
7. Complete Report + test checklist + closing. Export as JSON or Markdown.

Tests and Review

A session that says it is done is not done. When the work is finished, Pragma checks it.

• VERIFY — your test command really runs. Only failures that are new compared to the project’s baseline block the session; tests that were already failing do not.
• REVIEW — a separate Claude session, with no memory of the work, reads exactly what changed, with your project’s rules in hand and a security pass on sensitive paths. You choose Fix or Accept. It runs after every finished session in a git repository and costs one review each time; one switch turns it off.
• Projects, to-dos, scheduled sessions — sessions are grouped by project, each with its own test command, rules and checklist, and a session can be held until a chosen time.

Pragma does not save tokens: in a small three-round comparison against Claude Code alone, quality was the same (19/19 hidden tests every time) and cost was within noise. Method and numbers.

What Else

• Model choice — Sonnet, Opus, or Fable, chosen per session. The models key in ~/.pragma/settings.json maps each name in the interface to the id passed to Claude Code, so a newly released model can be adopted without waiting for a new build.
• Multi-profile CLI — Manage multiple Claude Code installations. Each profile has its own binary, config dir, and optional language override.
• Session history — Full-text search (SQLite FTS5) over past sessions, scoped to the project you are in.
• Attachments — Files copied to pragmadocs/ in the working dir. Claude sees them via --add-dir.
• Auto-confirm — Optional: step confirmations bypass automatically after 1.5s if no anomaly.
• Scroll lock — Stream auto-scrolls. Scroll up → lock activates → badge shows new atom count.
• Export — JSON or Markdown. From UI or CLI (pragma export <session-id>).
• Local-first — No telemetry. Sessions live in ~/.pragma/pragma.db. The only thing that ever leaves your machine is what you choose to share on the web, through a relay; the privacy policy says exactly what.
• Web sharing — Optional. Follow a session from a browser or a phone through a temporary link, and, if you allow it and set a PIN, approve or answer from there. It needs a personal access key, available on request.
• Dark / Light theme — Persisted. Focus mode available.

Built On

Rust (Tauri v2) backend · Vue 3 + Pinia frontend · SQLite (WAL + FTS5) · NDJSON parser written in Rust.

Open Source

Pragma Symphony is released under the MIT licence: read it, change it, fork it. It is not affiliated with Anthropic or with any other project called Symphony. It drives the Claude Code you already have installed.