ARMARA Course 02

Course 02 / Module 03

Read the file ArmaraOS wrote about your agent

Locate a real manifest, compare its declarations with runtime evidence, and safely round-trip a copied agent.

Level
Beginner
Time
18 minutes
Commands
4 core
Finish
A verified manifest round trip

Video / coming soon

The written lesson is complete now.

Find before you open

Search the complete agents tree for agent.toml. Do not assume the folder named for your running agent contains one.

PowerShell
Get-ChildItem "$env:USERPROFILE\.armaraos\agents" -Filter agent.toml -Recurse
01

Locate a manifest that actually exists

Real filesystem result showing the one agent manifest currently found
Fresh live capture / one manifest found / 24 August 2026

Only the Email Drafter directory currently has agent.toml. Other running-agent directories contain runtime stores but no manifest. Open a file that exists, never an imagined path.

02

Read the declared capabilities twice

Real manifest excerpt with full profile and empty explicit capability arrays
Real manifest excerpt / declarations point in different directions

The file says profile = "full", then lists empty network, tools, and shell capabilities with agent spawn false. A field is a declaration, not proof of the runtime path.

Real workspace refusal from the live agent
Reused genuine runtime evidence / outside path refused

Runtime evidence is mixed: network and a harmless shell command completed, the outside-workspace read was refused, and the queue stayed empty. Use the observed result for the specific action.

03

Read the resource gate before delegation

Real manifest resources with zero subagent limits and zero cost values
Real manifest excerpt / delegation disabled by quota

max_subagents and max_spawn_depth are zero. The cost fields read 0.0 and do not provide proven enforcement. Course 4 changes delegation only after another backup.

04

Read the execution policy as text

Cropped real execution policy with safe binaries, limits, and enforced guards
Cropped real manifest excerpt / named binaries and guards

The policy names safe binaries, a timeout, an output limit, and enforced path and process guards. Do not translate mode = "full" into a promise that every path is reachable.

05

Prepare a copy with two unique fields

Copy the manifest outside the live agents directory before editing.

name = "manifest-roundtrip-test"
workspace = "<your ArmaraOS home>/workspaces/manifest-roundtrip-test"

Changing only the name would make two agents share one workspace. Change the name and workspace, then leave all capability and resource lines unchanged.

06

Spawn, confirm, and kill the copy

Run in your terminal
armaraos agent spawn <MANIFEST_COPY>
Real successful spawn of a disposable manifest copy
Fresh production capture / unique disposable name
Run in your terminal
armaraos agent list
Run in your terminal
armaraos agent kill <NEW_UUID>
Real kill confirmation followed by the intact original roster
Fresh production capture / original roster restored

Kill ends the running row but leaves its stored directory and workspace. This is a runtime round trip, not data deletion.

07

Name the missing command levers

The manifest copy is the CLI-side lever for declared capability changes.

There is no top-level tools command, no agent profile command, and live help documents only model for agent set.

Check it / complete the round trip

Confirm the copy, then end only the copy.

Run in your terminal
armaraos agent list

See the unique copied name, kill its new UUID, and confirm the original roster remains. Keep the edited manifest copy outside the live agents directory for Course 4.

Safety note

Never edit the only live manifest in place. Copy it, change both name and workspace, spawn the copy, verify its row, and remember that kill does not erase stored files.

Troubleshooting for this sitting
What you seeLikely causeWhat to do
The expected path is missingThat running agent has no manifest file.Search the full agents tree.
Spawn reports a name collisionThe copy kept the original name.Give it a unique name and workspace.
Two agents share one workspaceOnly the name changed.Kill the copy and prepare a corrected copy.
The queue stays empty during a probeThis matches verified CLI behavior.Use the direct response and refusal as evidence.

Back to Module 2.2

Next / Module 2.4

Put your secrets somewhere you can rotate them

Lesson ready