PrismetSage Deutschle

Work / Developer Tools

PrismCode

The engineering workbench behind the unified Cicero app

Local workbench · evolving

Inside the work

Make agent work comparable.

Scripted demo

My contribution

Design and engineering of a desktop workbench for Claude Code, Codex and DeepSeek, with shared session and review surfaces.

Engineering decisions

  1. Normalize at the adapter boundary

    Agent-specific adapters emit one event contract for streamed text, tool activity, file changes and permission requests, keeping provider details out of the shared interface.

  2. Put review before adoption

    The comparison workflow presents proposed changes side by side with explicit choices to apply one result or keep both. A mock-agent loop supports interface development.

What you can inspect

The scripted demonstrations show the comparison and diff views from the engineering workbench. They illustrate that interface, rather than a benchmark or a fresh runtime test of the unified Cicero app.

Explore the project images ↑

PrismCode developed the engineering workspace for Claude Code, Codex and DeepSeek: agent panes, transcripts, approvals, terminals, files, Git, diffs, sessions and usage tracking. Its worktree comparison workflow puts proposed changes side by side before adoption.

That foundation is now part of the unified Cicero workbench, whose source also includes advisory Opinion, Legion and Senate dispatch, campaign tracking and a Historian. The older council prototype and installed phone companion belong to the same project lineage.

Highlights

  • Agent adapters normalize streamed activity into a shared interface
  • Separate Git worktrees support side-by-side comparison
  • A mock-agent development loop for interface work
  • Advisory and dispatch workflows brought together in the unified source

How the agents share one workspace

Claude CodeCodexDeepSeek One AgentEventstream One workspace PRISM A/Btwo worktrees, one prompt One adapter per agent

PRISM A/B: two git worktrees, one prompt Compare, apply the winner, or keep both

The PRISM A/B compare view for one prompt: Claude changed 2 files (+47) and Codex 1 file (+16), their diffs side by side, with Apply Claude, Apply Codex, Keep both and Discard buttons.
The PRISM A/B compare view for one prompt: Claude changed 2 files (+47) and Codex 1 file (+16), their diffs side by side, with Apply Claude, Apply Codex, Keep both and Discard buttons.

Project portfolio