ARMARA Course 02

Course 02 / Module 05

The window you leave open

Use the terminal UI for a working system glance and evaluate the 0.8.3 log surface without pretending it records activity it does not show.

Level
Beginner
Time
10 minutes
Commands
3
Finish
An honest live observation

Video / coming soon

The written lesson is complete now.

Use two terminal windows

Keep the daemon detached. One window opens the terminal UI or log command while the other remains available for checks.

Use PowerShell and enlarge the window before launching the TUI.
01

Open the working glanceable surface

Run in your terminal
armaraos tui

This is a terminal interface and stays inside the CLI course. Use it for a quick glance, not for adding capability.

Legacy headline

The version 0.8.3 terminal screen currently carries an OpenFang headline. Confirm the ArmaraOS daemon address and version, then treat the headline as cosmetic.

02

Read the log options from live help

Run in your terminal
armaraos logs --help
Real log help showing default 50 lines and the follow flag
Fresh live help / exact defaults / 24 August 2026

The default is 50 lines. --lines accepts another count, and -f is the short form of --follow. Logs has no JSON flag.

03

Recognize the missing-file bootstrap

Real logs error showing the expected tui.log file did not exist
Fresh live output / before the terminal UI created the file

Before the TUI ran, the expected file did not exist. Launching the TUI created it. That was a bootstrap condition, not a broken daemon.

04

Test follow without inventing activity

Run in your terminal
armaraos logs -f
Real follow banner attached to the ArmaraOS tui.log file
Fresh live output / follow attached successfully

The agent replied, but tui.log remained empty. In this build, logs is not a reliable live agent activity feed.

05

Choose the evidence that exists

QuestionWorking evidence
Is the local daemon visible?The terminal UI and health.
Was a conversation recorded?sessions metadata.
What events were recorded?The security audit in Module 2.7.
Did this build write TUI log lines?logs --lines 50, which may be empty.

Check it / run this yourself

Use the glance, then report the file honestly.

Run in your terminal
armaraos tui

Identify the daemon, agent count, and provider, then exit with q. Run armaraos logs --lines 50 and report whether your own file contains lines.

Safety note

Logs can contain prompts and tool output on builds where they are populated. Read them before sharing, even though the verified file for this instance is empty.

Troubleshooting for this sitting
What you seeLikely causeWhat to do
Log file is missingThe TUI has never created it.Launch and exit the TUI, then retry.
Follow shows no messageThe file is not receiving agent activity.Use sessions and security audit evidence.
The headline says OpenFangLegacy terminal branding.Confirm version and daemon address, then continue.
The layout is distortedThe terminal is too small.Enlarge it and relaunch.

Back to Module 2.4

Next / Module 2.6

Read ArmaraOS output like a script, and save a 30-second morning check

Planned