Local usage and release notes

See local usage: `/usage`

In an active session:

/usage

Aliases: /cost. /usage show is the same as bare /usage.

In fullscreen, Matcha CLI opens a usage panel. The **session** block is the useful part: tokens and estimated cost for the current conversation. Account-allowance / credit rows stay empty or say there is no billing data — that is expected. There is no MatchaCode account to query.

In **minimal** mode (--minimal / /minimal) the same session summary is printed into scrollback instead of a modal. If the session has not started yet, you see **Session usage is unavailable until the session starts.**

/usage with no active assistant does nothing.

`/usage manage` is not offered

/usage manage

prints **Account billing is unavailable in this Matcha build (Mode A).**

This is not a broken install. Billing and subscription are turned off. Your Provider (xAI, OpenAI, Anthropic, and so on) may still bill you on their side; Matcha CLI does not show or manage that invoice.

If a Provider returns a usage-limit error, Matcha CLI can say the Provider limit was reached and repeat that account billing is unavailable here.

On some installs /usage is hidden entirely (external auth provider). Typed /usage then says **/usage is not available.**

What changed in this build: `/release-notes`

/release-notes

Alias: /changelog.

Remote release notes are **not published** for this Matcha CLI. The command fails closed and tells you to use /docs for the local How-to Guides. It does not fetch a CDN, and it does not name a product host.

To see **which binary** you are running:

matcha --version

matcha version is the same idea; add --json for scripts.

To read task help inside the TUI: /docs. The in-app first hour is /tutorial (aliases /tour, /onboarding).

Local logs and crash files

Write a file log when you need a trail Doctor cannot show:

MATCHA_LOG_FILE=/tmp/matcha.log RUST_LOG=debug matcha

MATCHA_LOG_FILE is used as a literal path. A relative value such as 1 creates a file named 1 in the current directory. Do not put API keys in a path you will share.

If MATCHA_LOG_FILE is unset, a registered GROK_LOG_FILE is still read.

Crash dumps stay on disk. They are not uploaded. matcha doctor can **identify** leftover Grok crash directories under ~/.grok without opening or deleting them. Uninstalling Matcha CLI never removes ~/.grok.

/privacy opens the local coding-data settings row (value **Local**). It does not open a remote policy page. Extra arguments such as opt-in are ignored.

Surfaces that look related and are not

These names exist in the binary. They are **not** user procedures in this Matcha CLI:

Setting MATCHA_TELEMETRY_*, MATCHA_EXTERNAL_OTEL, or [telemetry] otel_* does not send metrics or events to MatchaCode, xAI, or a third-party collector.