Synthesis work, visible

Synthesis Console

A local interface for the files that carry your work forward.

Synthesis Console turns plain Markdown and YAML into a browsable workspace for projects, daily plans, decisions, commitments, lessons, and agent conformance. It reads your files in place. There is no account, cloud import, or database.

View the sourceRun the demo

The role

Your files remain the system of record

Synthesis work accumulates durable project state: an index of projects, a short working context for each one, stable reference notes, session history, lessons, and a daily plan. Those files are readable by people, scripts, and AI agents.

The Console gives that state an interface without taking ownership of it. Edit a file, refresh the page, and the interface changes. Remove the Console and the work is still there, readable by whatever comes next.

Synthesis Console demo project list, with project status totals, search, filters, and initiatives
Built-in demo data lets you inspect the product before connecting your own files.

What you can do

See the state. Act where judgment is needed.

01

Navigate projects

Browse initiatives and projects, filter by status or tag, and open working context, reference notes, and session history.

02

Work from the daily plan

Review priorities, make decisions, mark tasks complete, and handle prepared drafts next to the evidence behind them.

03

Track commitments

See who owes what, what you owe, meeting preparation, and the ledger of work that needs attention.

04

Inspect system health

Check repository sync, context integrity, and whether agent setups agree, with each layer shown as separate evidence.

Ragenie + Console

Two interfaces over the same work

Agent harness

Ragenie is becoming the runtime

Ragenie is being built to run procedures and coordinate agent work across the synthesis system.

Human interface

Synthesis Console makes state visible

The Console places projects, evidence, and decisions where a person can inspect and act on them directly.

They meet at the filesystem. Neither product becomes the landlord of the work.

Try it with sample data

See a working Console before configuring anything

The repository includes a complete demo workspace. Install Bun, then run:

git clone https://github.com/synthesisengineering/synthesis-console.git
cd synthesis-console
bun install
bun run demo

Open http://localhost:5555. When you are ready, point the Console at your own project directories through ~/.synthesis/console.yaml.

Further reading

Articles featuring Synthesis Console

  1. Synthesis Console: open-source tooling for synthesis engineering

    The product's origin, architecture, and three-dependency budget.

  2. Demo mode as a pattern for software

    Why representative sample data belongs in the product itself.

  3. Every bug report is now a patch-or-redesign decision

    A day of Console defects used to distinguish patch moments from redesign moments.

  4. Why my AI stack has three runtimes

    A practical model for conversation, repeatable procedures, and the visible state where people decide.

  5. AI tools should copy GitHub's identity model, not your employer's

    How one view can span contexts while each context keeps its own files.

Open source

Read the code and the operating documentation

The repository contains the source, setup instructions, data conventions, security notes, and design contracts for the Console's interactive surfaces.

Open Synthesis Console on GitHub