systhema info

Show a doctor-style, sectioned diagnostic view of the CLI and current project. Useful for bug reports and quick health checks.

systhema info
systhema info --json   # machine-readable output

Each line is prefixed with a status glyph: ✔ (ok), ⚠ (warning), ✖ (error), ℹ (info).

SectionsLink to this section

• CLI — CLI version and how it was installed (global / local / npx); registry reachability and latency; an ℹ registry token not configured notice when no GitHub Packages auth token is found; a ⚠ update available <ver> — systhema self-update line when a newer stable release exists.
• Project (only when run inside a Systhema project) — project root; humanized type (Next.js or Payload + Next.js); version drift vs the running CLI (matches CLI, or → upgrade to <ver> (systhema upgrade)); the version the project's tokens were generated with (from manifest.json; shows tokens in legacy format when the manifest has no generator); and for Payload projects a connections summary (db <sqlite|postgres> · email <resend|sendgrid|smtp> · captcha <recaptcha|turnstile|both> · maps).
• Skills — how many bundled skills are installed and for which agents, or a hint to run systhema skills install.
• Health — the same fast (offline) checks as systhema doctor, summarised as an error/warning count with a prompt to run systhema doctor, or no issues when everything is clean.

Example output (inside a Payload project):

  CLI
  ✔ 1.6.0 · global install
  ✔ registry reachable (124ms)

  Project  ~/sites/acme
  ✔ Payload + Next.js
  ⚠ systhema 1.4.0 → upgrade to 1.6.0  (systhema upgrade)
  ✔ tokens generated with 1.0.0
  ✔ db postgres · email resend · captcha turnstile

  Skills
  ✔ 3 installed (claude, cursor)

  Health
  ⚠ 2 warnings — run systhema doctor

JSON outputLink to this section

The --json output includes the same data in a machine-readable object. In addition to the fields present before 1.6.0, the JSON is extended with: cli.installKind, project.tokens, project.connections, and a top-level health { errors, warnings }. Existing consumers are unaffected — the new fields are additive. No header is printed in --json mode.

OptionsLink to this section