Choose a shell-native JSON reader
Use structured output to select a field, not merely to make the screen longer. The saved morning check stays human-readable.
(armaraos agent list --json | ConvertFrom-Json)[0].idarmaraos agent list --json | jq -r '.[0].id'If jq is not installed, copy the first id value manually. Do not add a dependency merely for this sitting.
Start with the smallest JSON document
armaraos health --json
JSON is useful when another command needs one exact field. Human output remains better for a quick visual scan.
Extract one UUID and nothing else
(armaraos agent list --json | ConvertFrom-Json)[0].idarmaraos agent list --json | jq -r '.[0].id'
The result is the identifier required by commands such as message. The full roster also contains prompts, paths, names, and model details, so do not share it casually.
Expect document sizes to differ
armaraos status --json
armaraos doctor --json
Status is a large runtime document. Doctor can report all_ok: true while optional checks still warn. Read the individual checks before deciding whether anything needs attention.
Read recurring flags correctly
| Flag | Contract |
|---|---|
--config <CONFIG> | Use another configuration file where live help offers the recurring option. |
--json | Request machine output only where that command's own help lists it. |
If JSON errors on another command, check its help before blaming your typing.
Save the thirty-second morning check
armaraos health
armaraos status
armaraos doctor
armaraos logs --lines 50armaraos health
armaraos status
armaraos doctor
armaraos logs --lines 50The check is deliberately readable. Run it each morning for a week and learn the normal shape of your own instance.
Keep audit text out of the routine
The next module adds a more sensitive record.
The security audit can contain prompt text. It stays out of a routine that might later be pasted into a support ticket without careful reading.
Check it / run the saved file
Read four results in sequence.
Run the morning check. Identify the daemon state, diagnostic summary, and whether the local TUI log contains lines.
Structured output can contain prompts, local paths, agent names, and provider details. Select and redact before sharing it.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
--json is rejected | That command does not offer the flag. | Read that command's own help. |
| PowerShell prints no UUID | The roster is empty or JSON did not parse. | Run the full JSON command and inspect it. |
jq is not found | It is not installed. | Copy the first id manually for this lesson. |
| Doctor warns while all_ok is true | An optional check is unavailable. | Read the named check and act only if you need it. |
| Logs prints nothing | The TUI log is empty on this build. | Record the observation and continue. |