Module 02 | Manage a roster: change a brain, end an agent

Create a disposable agent first

Never practice agent kill on an agent you depend on. Use a clearly named disposable assistant and write its UUID beside its name.

Use PowerShell. The interactive creation screen must be captured live.

Create something safe to end

Run in your terminal

armaraos agent new assistant

Production used a manifest copy to create the same controlled state. The learner path reuses the assistant template already introduced in Course 1.

Get the disposable UUID

Run in your terminal

armaraos agent list --json

Find course-2-model-test and copy its id. Both set and kill require that UUID. Match it to the name again before each command.

Change only that agent's model

Run in your terminal

armaraos agent set <UUID> model openrouter/minimax/minimax-m2.5:free

Real output confirming a per-agent model change using a full OpenRouter model ID — Fresh live capture / disposable UUID only / 24 August 2026

Real four-agent roster showing only the disposable agent on the MiniMax free model — Fresh live capture / original three rows unchanged

Use the full catalog ID.

A shorter value beginning minimax/ was parsed as provider MiniMax and left authentication missing. Prefix the value with the configured provider exactly as the live catalog prints it.

Live help documents model as the only supported field. This course does not invent other field names.

End the disposable running agent

Run in your terminal

armaraos agent kill <UUID>

Real kill confirmation followed by the restored original three-agent roster — Fresh live capture / disposable row gone / originals restored

Kill loses in-flight work and has no undo for that work. Confirm the UUID immediately before running it.

State what kill does not erase

Kill is an execution stop, not data deletion.

The live disposable agent directory and workspace remained after the row left the roster. Production moved those exact directories into a recoverable course archive. Do not improvise manual filesystem deletion on your own agent.

Compare the two model scopes

Run in your terminal

armaraos status

Run in your terminal

armaraos agent list --json

Status names the daemon-wide default. Agent JSON names each per-agent model. The local override never changed the daemon default or the original agents.

Check it / run this yourself

Prove the original roster is intact.

Run in your terminal

armaraos agent list --json

The disposable UUID is absent. Your original agents remain with their previous model values. Confirm the daemon default separately with armaraos status.

Safety note

agent kill loses in-flight work without undo. Use a disposable agent, match UUID to name before the command, and never assume kill deletes stored files or memory.

Troubleshooting for this sitting

What you see	Likely cause	What to do
Authentication becomes missing	The model value was parsed as another provider.	Use the full provider-prefixed catalog ID.
Set rejects the agent	A name was used instead of UUID.	Copy `id` from the JSON roster.
Files remain after kill	Kill is not stored-data deletion.	This is verified behavior. Do not improvise filesystem deletion.

Back to Module 2.1

Next / Module 2.3

Read the file ArmaraOS wrote about your agent

Lesson ready

Manage a roster: change a brain, end an agent

The written lesson is complete now.

Create a disposable agent first

Create something safe to end

Get the disposable UUID

Change only that agent's model

End the disposable running agent

State what kill does not erase

Compare the two model scopes

Prove the original roster is intact.

Read the file ArmaraOS wrote about your agent