CLI output modes

Glade writes human output first. It names the result, the file or artifact that changed, and the next command to run.

Glade check

✓ No diagnostics found

Checked:
  Apex types   19
  Triggers     3
  Objects      8

Human output

Default command output is for a terminal. It uses short sections, project-relative paths, and Next: or Try: commands after non-trivial results.

Human output may change when it makes the command clearer. Do not parse it in CI.

Machine output

Use --json when a script needs stable fields.

glade doctor --project . --json
glade check --project . --json
glade test --project . --json --no-progress
glade exec --json "System.debug('local');"
glade debug profile --log apex.log --json

Completed result-producing JSON modes write JSON to stdout and progress to stderr. For glade doctor --json, recognized flags also keep missing-project and malformed-config setup failures in JSON. Flag syntax errors are CLI usage errors and remain human diagnostics on stderr. Watch modes emit NDJSON events. Wizard output and legacy paths such as glade test failed --json with no saved failures still print human text; do not parse those as a result envelope.

Progress

Use --no-progress for logs, CI, and copied examples.

glade check --project . --no-progress
glade test --project . --json --no-progress

--progress-json writes NDJSON progress events to stderr for tools that want a live feed.

Color

Glade disables color for non-TTY output, NO_COLOR, and TERM=dumb.

NO_COLOR=1 glade check --project .
TERM=dumb glade test --project .

The target contract reserves --color auto|always|never and --no-color. Until those flags are wired through every command, use the environment variables above.

Paths

Human output uses project-relative paths by default:

force-app/main/default/classes/RefinementService.cls:12:18

Verbose and debug output may show absolute paths.