Cratis CLI

CLI

Inspect and diagnose Chronicle from a terminal

The Cratis CLI provides terminal workflows for inspecting and diagnosing Chronicle. Use the exact CLI version and documented command scope for the environment you inspect.

Start here

Install the CLI

Choose a current distribution path for the machine running the terminal.

Connect and inspect

Create a context, select it, and run the bounded diagnostic summary.

Keep the limits visible

Separate inspection from mutation authority, support, and machine-contract claims.

Install

Homebrew

brew tap cratis/cratis
brew install cratis

.NET tool

dotnet tool install -g Cratis.Cli

The .NET tool requires the runtime declared by the current package. Native release assets and platform coverage vary by release; verify the exact artifact before installation.

Connect and inspect

1. Create a named Chronicle connection context.

   cratis context create dev --server chronicle://localhost:35000

2. Select that context.

   cratis context set dev

3. Run the documented diagnostic summary.

   cratis chronicle diagnose

The diagnostic command reports its documented connection, observer, failed-partition, and recommendation checks. Use command help and the exact CLI version to inspect the current command and output surface.

Product relationship

Chronicle Workbench provides a bundled local browser surface for authorized inspection of Chronicle runtime state and preview of supported projection behavior. The CLI provides the terminal inspection and diagnosis path around the same product family.

The CLI also contains separately documented command groups for other Cratis products. Their presence does not establish those products’ maturity, support, compatibility, or availability.

Current boundaries

Inspection is not authority

Inspection capability does not imply complete administration or production mutation authority. Confirm the event store, namespace, target, current state, and documented operational procedure before a mutation command.

• Ordinary output formats are not an unversioned stable machine contract.
• Command availability does not establish support, an SLA, reliability, security, compatibility, or production suitability.
• Connection strings and context files can contain credentials; keep them out of source, public issues, and shared logs.

Continue

CLI source, releases, and command guide

Repository README, current releases, operational cautions, and contribution paths.

CLI package

Published .NET tool metadata and versions.

Chronicle

The event-sourcing database and runtime the CLI inspects — kernel, protocol, and runtime documentation.

Chronicle Workbench

The bundled browser surface for authorized inspection of Chronicle runtime state.

Arc

The CQRS application framework whose running commands and queries the cratis arc group inspects.