alis doctor¶

Collect a diagnostics snapshot of the local Alis Build environment, and optionally upload it to a support conversation.

Synopsis¶

❯ alis doctor [flags]

Description¶

The snapshot holds live component probes (CLI, IDE extension, agent plugins) compared against the detection cache, setup-plan state, terminal and host shape, settings, and the recent log tail. Credentials and tokens are never included.

With --ticket, the snapshot is uploaded to that specialist conversation after a confirmation; a specialist may ask for this during a conversation.

Flags¶

Flag	Type	Default	Meaning
`--no-logs`	bool	false	Exclude the log tail from the snapshot.
`--ticket <id>`	string		Conversation to upload the snapshot to (`tickets/<id>` or bare id).
`--yes`	bool	false	Skip the upload confirmation prompt (same as `--approve`).

Plus the global flags.

Examples¶

Shell

alis doctor
alis doctor --json
alis doctor --no-logs
alis doctor --ticket tickets/<id>

Output¶

Human output:

alis diagnostics · <date> · cli <version>
Environment   darwin/arm64 · WezTerm … · zsh
Auth          authorized · account accounts/<id>
Components:
  cli                <version>    detected
  vscode extension   —            not installed
  claude plugin      <version>    detected
  …
Cached probe  <time> — matches live probe
Setup steps   9/9 installed
Settings      scanning=alisBuildOnly · safeMode off · notifications on
Log tail      …

--json returns an object with version, createdAt, cliVersion, os, arch, terminal, host, shell, path, auth, components, cachedProbe, claudePlugin, bins, setup, settings, logPath, logTail, cliLogPath and cliLogTail.

Notes¶

Uploading diagnostics is a destructive-class action under the automation tiers and asks for confirmation.
alis doctor --json also carries the command log a TIMEOUT envelope points at.