Eight courses / one working system
Learn the
command line.
Run the work.
Start with one named assistant. Add safety before automation, and visibility before delegation. Every sitting ends with something you can check on your own computer.
Course 1 / 10 sittings
Getting to a Working Agent
A named assistant answers on your computer, with the first safety boundary close behind.
- 1.1 Installation and Your First Agent
- 1.2 Running ArmaraOS as a Background Service
- 1.3 Approving and Rejecting Agent Requests
- 1.4 Managing Agents and Reviewing Conversations
- 1.5 Providers, Models, and Free Tier Limits
- 1.6 Reading and Backing Up Your Configuration
- 1.7 Enabling Shell Tab Completion
- 1.8 Agent Names and Identifiers
- 1.9 Core Concepts and Reading Command Output
- 1.C Course Capstone
Course 2 / 11 sittings
The Safety Rails
Make the agent legible, stoppable, and less expensive before adding power.
- 2.1 See exactly what `--yolo` takes away
- 2.2 Manage a roster: change a brain, end an agent
- 2.3 Read the file ArmaraOS wrote about your agent
- 2.4 Put your secrets somewhere you can rotate them
- 2.5 The window you leave open
- 2.6 Read ArmaraOS output like a script, and save a 30-second morning check
- 2.7 The audit trail, and why it reports itself invalid
- 2.8 Cut the bill by picking a cheaper brain
- 2.9 Pay fewer tokens for the same answer
- 2.10 Change config without wrecking it, and meet the destructive inventory
- 2.C Course Capstone
Course 3 / 8 sittings
Work That Happens Without You
Start work on a schedule, hold it at a gate, and deliver the result.
- 3.1 Your first alarm clock
- 3.2 Find out what's already firing on your machine
- 3.3 Text your agent from your phone: setup, and reading what the wizard wrote
- 3.4 Test privately, then open the door
- 3.5 Register a callback URL
- 3.6 TRACK B: react instead of poll
- 3.7 Which one do I reach for?
- 3.8 CAPSTONE: the morning brief, end to end
Course 4 / 9 sittings
Multi-Agent Orchestration
Unlock delegation, run a mission, read its trace, cost it, and stop it.
- 4.1 Do it by hand once, so you feel what you are buying
- 4.2 Unlock delegation: the four lines that say no
- 4.3 Hand an agent a goal and walk away
- 4.4 Drive a running mission: pause before cancel
- 4.5 Read what happened: traces
- 4.6 See who delegated what to whom, and what it actually costs
- 4.7 Watch it live, and the budget field that reads 0.0
- 4.8 TRACK B: chain steps into a repeatable recipe
- 4.9 CAPSTONE: the containment drill, timed and rehearsed
Course 5 / 9 sittings
Memory, Trajectories, and MCP
Curate memory, inspect trajectories, and connect a real outside tool.
- 5.1 Tell it something it never forgets
- 5.2 Turn on the memory engine
- 5.3 Curate what your agent believes
- 5.4 Back up a brain before you risk it
- 5.5 Prove what your agent actually did
- 5.6 Dry-run, export, prune, in that order, always
- 5.7 Give your agent a real tool
- 5.8 Drive ArmaraOS from another tool
- 5.C Course Capstone
Course 6 / 6 sittings
Skills and Hands: Installing Things You Did Not Write
Install code you have read, observe it once, and remove it cleanly.
Course 7 / 7 sittings
Operating, Troubleshooting, and Backing Out
Diagnose, update, report honestly, and rehearse a safe exit.
Course 8 / 3 sittings
Your Runbook and the Reference Shelf
Write the operating page that another person can use without guessing.