Skip to content
Cratis Cratis Cratis

Cratis CLI

CLI

A terminal window into your event store

When something happens in a running Chronicle system — an event you need to see, an observer that’s stuck, a read model that looks wrong — you don’t want to write a query. You want to look. cratis is that look. Get started →

Terminal window
brew install cratis            # or: dotnet tool install -g Cratis.Cli
cratis get-started             # connects to your local Chronicle and shows you around

What you can do with it

Section titled “What you can do with it”
Inspect events

Browse event types, read the events on any stream, and follow appends as they happen.

 Watch the machinery

See projections, reducers, and reactors, check their state, and catch a stuck one.

 Browse read models

Look at projected state directly, without reaching for a database client.

 Diagnose failures

Find out why a partition paused — one command, not an investigation.

 Connect anywhere

Switch between local, staging, and production with named contexts.

 Set up AI tooling

cratis init teaches your AI assistant about your store with a command catalog.

Why a CLI?

Section titled “Why a CLI?”

You could open a database client, write ad-hoc queries, and reverse-engineer what your event store is doing. The CLI gives you a purpose-built, event-sourcing-aware view instead: it speaks events, streams, observers, and read models — so “why is this projection behind?” is one command, not an investigation.

It’s also AI-native. Run cratis init in your project and it teaches your AI tools (Claude Code, GitHub Copilot, Cursor, Windsurf) about your Chronicle store, so your assistant can help operate it too.