Tails render logs in real time. Resolves any ${VAR} placeholders in backendUrl
(from outkit.json) against process.env and .env.local, so the same config works
locally and in deployed environments.
outkit logs list # newest firstoutkit logs tail # stream new logs (polls every 2s)outkit logs replay <logId> # replay a single log entryoutkit logs export --since 7d # bulk export to JSON or CSV
Each log row shows the input content, the components that were generated, the strategy
(single, single_hinted, two_step), token usage, and latency.
outkit doctor # quick auth + network checkoutkit doctor --full # also tests project mode, SDK packages, wire format, # and the design-token meta event end-to-endoutkit doctor --json # machine-readable for CIoutkit doctor --backend https://staging.api.example.com
doctor is the canonical “is anything broken” command. Run it any time setup looks off.
outkit status # local-only summary of what the CLI knowsoutkit whoami # round-trips the server to confirm your token worksoutkit config # view or edit outkit.json
outkit telemetry status # see whether anonymous analytics are onoutkit telemetry on # opt inoutkit telemetry off # opt outoutkit telemetry log # tail ~/.outkit/telemetry.log (NDJSON)
The local NDJSON log is written even when telemetry is off — it’s a glass-jar of every
event the CLI would send, so you can audit before flipping it on. Auto-truncates at 1 MB.
Anything that mutates your codebase or remote state is journaled. To reverse the most
recent command:
outkit undo
undo refuses to clobber files you have edited since the command ran. Dependencies are
not auto-removed — the CLI prints the uninstall command for you instead.
