Choose a safe backup destination
- Use a folder outside the live
.armaraosdirectory. - Use a new filename so an older backup is not overwritten.
$env:USERPROFILE\.armaraos.$HOME/.armaraos.Read the configuration that exists
armaraos config show
Start with the path printed on the first line. This instance has a schema version, efficient_mode, and one MCP server named ainl. It has no model or channel section, and that is normal.
The transport uses stdio and points to a local executable. Course 5 returns to it. Course 2 returns to efficient mode.
Locate the home without trusting the status defect
Data dir: ? is cosmetic. The config path gives you the real location.
Your home may contain more files and directories. Look for config, agents, logs, workflows, and workspaces. Treat files named for secrets or environment variables as sensitive without opening them.
This prepared home contains secrets.env and no .env. Setup and environment choices can differ. Verify credentials with config test-key, not by opening secret files.
Make a backup outside the live home
Copy-Item "$env:USERPROFILE\.armaraos\config.toml" ".\config.toml.backup"cp "$HOME/.armaraos/config.toml" "./config.toml.backup"The destination is the current folder, outside the live ArmaraOS home. Prefer a dated name for future backups and never overwrite the only known-good copy.
Sort the four setup-looking commands
| Command | Verified role |
|---|---|
armaraos onboard | The guided first-run path from Module 1.1. |
armaraos init --quick | Writes config and .env without prompts for scripts or CI. |
armaraos setup --quick | Documented as the same quick initialization. |
armaraos configure | Interactive credentials-and-channels wizard. |
Do not run any of them now. Your working installation already exists. This table removes the mystery without rewriting state.
Verify before leaving
Compare the source path to the file you copied.
Run config show once more. Confirm that the backup exists at the destination and that its filename is not inside the live .armaraos directory.
Check it / run this yourself
Find the AINL block and your backup.
armaraos config showPoint to the [[mcp_servers]] block named ainl, then confirm the copied config.toml.backup exists outside the live home.
Treat the entire ArmaraOS home as sensitive. Do not open credential files for curiosity, and do not place the directory in source control or an uncontrolled sync folder.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
Status shows Data dir: ? | Known cosmetic defect. | Use the path printed by config show. |
| The config has different sections | Enabled features change the file. | Read what exists. Do not add sections merely because this lesson names them. |
.env is absent | Credentials may use another supported source. | Use config test-key instead of inventing a file. |
| The backup destination exists | The filename was reused. | Choose a new dated name rather than overwriting it. |