CLI reference

One binary is the primary developer interface for Tarski. Every command ships complete --help; this page maps the families so you know where to look.

Author and iterate

Command	What it does
tarski scaffold	Create a text-file app; patterns: default, minimal, sensor, decision, chat, end-user-auth
tarski dev	The dev loop: watch, hot reload, and (cloud-first) source-bundle sync to a dev environment
tarski serve	Local inspection API and ingress; hosts Studio locally, query doors, and subscriptions
tarski templates	Materialize installable app templates at the workspace root
tarski examples	list / resolve / install / sync the example catalog
tarski entity expand	Refresh and report materialized entity expansions

Observe and replay

Command	What it does
tarski observe	Append observations to a lineage
tarski replay	Replay observation timelines (--isolated for a scratch lineage)
tarski run	Offline execution paths, including schedule catch-up, with stable zero-effect reasons
tarski activation	show / promote the effect-authoritative activation

Prove

Command	What it does
tarski verify	The proof gate: fixture replay, golden outputs, invariants, provenance, determinism, redaction, composition. --cross-engines requires bit-identical dual-engine output
tarski test	The deterministic test loop; --bless writes expected outputs from verified replays (refuses untrustworthy output; --all for suite rewrites; --refresh-recorded-digests for relay fixtures)
tarski fixture	Fixture authoring, including template query-relay <query>
tarski composition	Composition analysis; architecture writes the advisory module-split report

Query and inspect

Command	What it does
tarski query	Execute a declared query by name (--bindings, --explain, --head, --lineage, --json) or a scope-gated --adhoc-file — an audited spectator read
tarski mcp	Read-only worldview-query MCP server over stdio for coding agents; requires --actor-id and --projection
tarski studio	Launch Studio or produce snapshot data
tarski audit	facts / intents / attempts — semantic and runtime inspection
tarski agent	Agent inspection, including trace
tarski projection	inspect projections
tarski workview	list / inspect declared Workviews
tarski work-queue	list / inspect queues and issue durable queue controls
tarski contradiction	Contradiction evidence and resolution paths
tarski lineage	Inspect and manage observation histories
tarski stats	Storage usage, quotas, egress, index coverage, composition agreement, archive cost lines

Operate and maintain

Command	What it does
tarski reconcile	inspect and resolve ambiguous effect attempts
tarski schedule	list / show / create / update / pause / resume / remove / trigger / preview / fires / simulate
tarski index	create <relation> --position <n> / drop / rebuild / list [--json] — semantics-neutral fact-plane indexes
tarski gc	Store maintenance; --blobs [--dry-run] collects unreferenced blobs
tarski storage	migrate --to <backend> with digest verification
tarski blob	hash / put / get / inspect

Package and extend

Command	What it does
tarski plugin	new / verify / try / add / list / show / remove (JSON output includes digests and baseline status)
tarski package	pack / publish / plan / update / rollback / audit / show, plus source list/add/disable/remove/show/mirror
tarski export	Evaluation packages, observations, facts, projections, verification bundles, graph bundles

Cloud

Command	What it does
tarski cloud login	Code-only email login (--code, --code-command for agents)
tarski cloud whoami	Show the authenticated identity
tarski cloud select	Select org/project/workspace scope — fail-closed: a denial exits nonzero and keeps your previous scope
tarski cloud deploy	Deploy the app; identity configuration lands on the runtime before activation promotes
tarski cloud promote / pause / rollback / archive	Activation lifecycle with receipts
tarski cloud status / readiness	Deployment and runtime state, including selected-lineage health
tarski cloud observe	Append an observation to the hosted lineage
tarski cloud query	Hosted query execution with digest parity; typed unavailable states, never a silent local fallback
tarski cloud replay-export	Export hosted evidence for local replay verification
tarski cloud token issue	Issue runtime tokens
tarski runtime version	Runtime identity
tarski login / tarski self-update	Session login; update the CLI through release channels

The exit-code contract

Cloud commands separate operation success from lineage health:

Exit	Operation	Lineage health	What to do
0	succeeded	healthy	Continue
1	failed	unknown or unchanged	Fix the operation; no success receipt exists
2	succeeded	pending or trapped	Do not repeat a non-idempotent append; keep the receipt, inspect the diagnostic, repair and replay

Treating a health failure as an operation failure would teach retry loops to duplicate observations; treating it as success would hide a broken model. Exit 2 says exactly what happened.