ARMARA Course 01

Course 01 / Module 02

Running ArmaraOS as a Background Service

Prove that the service survives a closed terminal, learn its fast and full health checks, and practice the off switch.

Level
Beginner
Time
14 minutes
Commands
5 core
Finish
Healthy in a new window

Video / coming soon

The written proof is ready now.

Start from Module 1.1

  • Your named agent exists and has already replied.
  • ArmaraOS is currently healthy. This lesson will stop it once, then restore it detached.
Use PowerShell. When the lesson says close the terminal, close the whole PowerShell window, then open a new one.
01

Avoid the terminal wall

Plain foreground startup belongs to one terminal window. Detached startup belongs to the computer.

Running armaraos start without the flag occupies the terminal. Closing that window ends the foreground process. The --detach flag launches the daemon in the background, returns your prompt, and is documented to survive terminal close.

Do not demonstrate the trap.

You do not need to run foreground startup to learn this distinction. Use the reliable detached path throughout the course.

02

Prove detachment with a new window

Start detached, then remove the terminal that started it.

Run in your terminal
armaraos start --detach
Real ArmaraOS detached startup output reporting the daemon running at localhost
Fresh live capture / detached startup / 23 August 2026

In the new terminal, ask for the fast health check.

Run in your terminal
armaraos health
Real ArmaraOS health output reporting that the daemon is healthy
Fresh live capture / healthy response from a new terminal

The old window is gone and the service still answers. That is the complete proof of detachment.

03

Read the full status report

Status adds the provider, model, address, uptime, and agent roster.

Run in your terminal
armaraos status
Real ArmaraOS status output showing a running daemon, three agents, provider, model, localhost address, and data directory question mark
Fresh live capture / three restored agents / localhost only

Confirm Status: running. The Provider and Model lines should match what you selected in Module 1.1. The API address begins with 127.0.0.1, which means this computer.

Two calm output notes

Data dir: ? is a cosmetic display defect in 0.8.3, not a broken installation. The Dashboard line names a web surface this CLI course does not teach. It appears in genuine output, so we identify it and move on.

04

Choose the fast or full check

The two commands agree about health but answer at different depths.

CommandUse it whenWhat you get
armaraos healthYou need a quick yes or no.A short health result.
armaraos statusYou need to inspect the running setup.Service state, provider, model, address, uptime, and agents.

Both commands also support machine-readable output. Course 2 uses that capability for scripted checks, so there is no need to add those flags yet.

05

Practice the off switch, then restore service

Know how to stop a service before relying on it.

Run in your terminal
armaraos stop
Real terminal output confirming the ArmaraOS daemon stopped
Fresh live capture / deliberate stop

Run the fast check again while the daemon is down.

Run in your terminal
armaraos health
Real ArmaraOS health output reporting that the daemon is not running
Fresh live capture / honest failure state

Now restore the state needed for the rest of the course.

Restore service
armaraos start --detach

Wait for startup to finish. The module must end with ArmaraOS running detached.

06

Recognize the gateway alias

The gateway family controls the same daemon through a grouped command.

Run in your terminal
armaraos gateway status
Real gateway status output showing the same running ArmaraOS daemon fields
Fresh live capture / same daemon through the gateway family

This course uses the shorter top-level commands as the primary path. Live help confirms that gateway start has no --detach flag, while top-level detached startup does.

07

Keep live logs in a second window

Watching output should not take ownership of the service.

When you later need live logs, keep the daemon detached and open a second terminal for armaraos logs -f. Module 2.5 teaches that view. Your service remains independent and your working prompt remains available.

Check it / run this yourself

Close the window one more time.

Close the current terminal completely. Open a new one and run the fast check.

Run in the new window
armaraos health

A healthy response from the new window proves the daemon is detached. If it is down, run armaraos start --detach and repeat the physical check.

Safety note

The default daemon listens on localhost and has no daemon password. Another program already running on your computer can also reach localhost. Do not expose port 50051 beyond your machine. Course 7 returns to access control.

Troubleshooting for this sitting
What you seeLikely causeWhat to do
Health fails after the window closesThe daemon was started in the foreground or never started.Run armaraos start --detach, wait, and repeat the physical check.
Stop says no daemon is runningIt was already stopped.Nothing is damaged. Start it detached.
Status shows Data dir: ?Known cosmetic output defect in 0.8.3.Continue. Module 1.6 locates the real files.
The provider or model looks wrongThe Module 1.1 selection did not persist as expected.Run armaraos models set, then check status again.
Startup is still restoring agentsLocal startup has not finished.Wait, then run health before retrying anything.

Back to Module 1.1

Next / Module 1.3

Approving and Rejecting Agent Requests

Lesson ready