Inspect, do not activate
This lesson never runs --yolo on your working machine. It reads the binary's contract and confirms the ordinary detached state.
armaraos start --detach command.armaraos start --detach command.Read the flag contract from the binary
The word all is the safety lesson.
armaraos start --help
--yolo requests automatic approval for all tool calls with no confirmation prompts. It is not a shortcut for one harmless action.
Separate process lifetime from permission
--detach and --yolo solve different problems.
| Flag | What it changes | Normal course use |
|---|---|---|
--detach | Process lifetime. The daemon survives terminal close. | Yes, for normal background startup. |
--yolo | Permission behavior. Tool calls are automatically approved. | No, not on the working machine. |
State the CLI limitation once
The original before-and-after queue exercise does not reproduce reliably.
In Module 1.3, CLI-originated network and shell tool use left the approvals queue empty even without this flag. The course therefore does not stage a visible difference that the CLI cannot prove.
The binary documents the contract. The CLI path does not give us a reliable comparative approval prompt in version 0.8.3.
Keep experimentation disposable
A suitable test environment has nothing worth protecting.
- No provider or integration credentials.
- No personal or work files.
- No configured messaging channels.
- No network access beyond what the test explicitly needs.
- No consequence if the environment is destroyed.
This course does not ask you to reproduce the flag on your everyday computer.
Never pair blanket approval with a channel
A remote input path and automatic permission remove two separate brakes.
Do not combine --yolo with Telegram, Discord, Slack, email, or any other configured channel. Course 3 teaches the channel allow-list boundary before any remote work is opened.
Confirm the prepared state
armaraos status
Status confirms the running local service. It does not print the startup flag, so safe practice comes from the command you actually ran and your shell history.
Check it / run this yourself
Name the two contracts correctly.
armaraos statusConfirm the daemon is running. Then say: detach controls process lifetime; yolo requests automatic approval. Confirm that you did not run --yolo on this machine.
Do not run blanket auto-approval on a computer containing files, credentials, configured channels, or anything you are unwilling to lose.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
| You expected a queued comparison | The CLI path does not reproduce it in 0.8.3. | Use live help as the authoritative contract. |
| Status does not name a startup flag | Status does not expose it. | Use known startup history. Do not restart merely to demonstrate this module. |
| You want to experiment | The flag invites curiosity. | Use a disposable isolated environment later. |