Live Workspace Activity

Observe CLI and Studio execution across terminals through one bounded activity graph without confusing telemetry with proof.

workspai live shows what Workspai commands are doing across terminals for the same project or workspace. It presents runs, stages, progress, warnings, failures, and published artifacts as one execution graph instead of an unbounded log stream.

Watch one workspace

# Terminal A
npx workspai live

# Terminal B
npx workspai workspace intelligence run --for-agent generic --strict --json

Closing Live does not cancel the command. A monitor, journal, or renderer failure cannot change the command result.

Use a bounded snapshot for automation and consumers:

npx workspai live --once --json --projection board

The Board projection is renderer-neutral. Terminal, IDE, browser, dashboard, and capture surfaces can consume the same bounded runs, nodes, edges, counters, selection, diagnostics, and evidence bindings without reconstructing execution from terminal text.

Local, fleet, and replay views

npx workspai live --global --max-scopes 20 --max-runs 20
npx workspai live --run <run-id>
npx workspai live --replay <run-id> --replay-speed 4

Global mode reads the bounded machine-local channel registry and deduplicates mirrored events. A project can remain visible in its own lane while also being correlated with its governing workspace. Replay reconstructs the selected run from durable event prefixes instead of inventing UI state.

workspace watch serves a different purpose: it observes workspace input changes so consumers know when bounded evidence may need refresh. live observes Workspai execution itself.

Accessible and deterministic output

npx workspai live --accessible
npx workspai live --ascii
npx workspai live --no-motion --no-color
npx workspai live --capture workspai-live.svg --capture-preset github --capture-theme obsidian

Accessible mode emits a stable linear projection without animation or terminal control sequences. SVG capture uses the same Activity Board model, writes atomically, and redacts local scope, project, run, and command-argument details by default.

Activity events may point to artifacts, projects, Graph entities, relations, or proofs. A Graph binding can include the exact source hash needed for a revision-safe overlay. Consumers must still resolve the referenced artifact and validate its contract, integrity, and freshness.

Live deliberately preserves these boundaries:

progress does not prove completion;
an exit code does not verify an engineering outcome;
a planned touch is not an observed effect;
an activity event is not authorization;
the activity journal is not the Evidence or Decisions ledger.

Model, Graph, Doctor, Security, Decisions, and verifiers remain authoritative for their own claims.

Privacy and retention

The activity plane is machine-local by default. It redacts sensitive options and metadata keys, avoids environment values, file contents, prompts, responses, and raw subprocess output, and applies bounded journal retention. External paths use portable locators rather than exposing a machine-specific absolute path.

Contract trail

See the generated live command reference for every current option and Observation, Feedback, and Evaluation for the separate measurement loop.