Back up the exact printed path
Run armaraos config show, confirm its first-line path, then make and verify a separate copy before any edit.
Copy-Item "$env:USERPROFILE\.armaraos\config.toml" ".\config.toml.backup"cp "$HOME/.armaraos/config.toml" "./config.toml.backup"Read a key that exists
armaraos config get efficient_mode
Help examples demonstrate dotted syntax; they do not promise those keys exist. Choose a path you have seen in config show.
Keep the broken scalar setter off the live file
armaraos config set efficient_mode balanced --config <DISPOSABLE_COPY>
The 0.8.3 command rejected an existing scalar as a section. The copy stayed unchanged. Do not build a workflow around this setter or troubleshoot it against the only live file.
Respect the comment-loss warning
Even when a future build fixes the scalar error, both mutation commands document that they strip TOML comments. That is why the backup comes first.
Prefer a visible editor for real changes
armaraos config editA visible editor lets you review surrounding TOML and comments. It does not remove the need for a backup.
Keep the destructive inventory
| Command | What it can destroy | Taught |
|---|---|---|
config set / config unset | Config comments, once mutation succeeds | 2.10 |
agent kill | In-flight runtime work | 2.2 |
cron delete | A scheduled job | 3.1 |
webhooks delete | A webhook registration | 3.5 |
trigger delete | A trigger | 3.6 |
mission cancel | A mission, one-way | 4.4 |
workflow delete | A workflow definition | 4.8 |
memory delete | One stored key-value pair | 5.1 |
memory graph-forget | Stored agent knowledge | 5.3 |
trajectory prune | Trajectory detail rows | 5.6 |
skill remove | An installed skill | 6.1 |
vault remove / config delete-key | A stored credential | 2.4 / 1.5 |
devices remove | A device's access | 7.4 |
reset / uninstall | The installation | 7.6 / Appendix B |
Ending an agent is not the same as deleting its stored directory. Each row has its own recovery boundary.
Memorize the two rehearsals
armaraos trajectory prune --dry-runarmaraos migrate --dry-runThese are the two dry-run flags in the verified surface. Everywhere else, resolve the exact target and make a backup.
Check it / prove recovery first
Read the value and verify the copy.
armaraos config get efficient_modeConfirm the value, then confirm your separate backup exists. Do not run set or unset against the live file merely to finish the lesson.
Never experiment on the only live configuration. Resolve the exact path, make a separate backup, and verify the backup before mutation.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
| Key not found | A help example was mistaken for a real key. | Run config show and choose an existing path. |
| A scalar is called a section | Verified 0.8.3 setter defect. | Keep the live file unchanged and review a manual copy. |
| Comments disappear later | Documented mutation behavior. | Restore from the verified backup. |
| Editor does not open | No editor association is available. | Open the printed path in your normal editor. |