Use two terminal windows
Keep the daemon detached. One window opens the terminal UI or log command while the other remains available for checks.
Open the working glanceable surface
armaraos tui
This is a terminal interface and stays inside the CLI course. Use it for a quick glance, not for adding capability.
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.
Read the log options from live help
armaraos logs --help
The default is 50 lines. --lines accepts another count, and -f is the short form of --follow. Logs has no JSON flag.
Recognize the missing-file bootstrap
Before the TUI ran, the expected file did not exist. Launching the TUI created it. That was a bootstrap condition, not a broken daemon.
Test follow without inventing activity
armaraos logs -f
The agent replied, but tui.log remained empty. In this build, logs is not a reliable live agent activity feed.
Choose the evidence that exists
| Question | Working 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.
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.
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 see | Likely cause | What to do |
|---|---|---|
| Log file is missing | The TUI has never created it. | Launch and exit the TUI, then retry. |
| Follow shows no message | The file is not receiving agent activity. | Use sessions and security audit evidence. |
| The headline says OpenFang | Legacy terminal branding. | Confirm version and daemon address, then continue. |
| The layout is distorted | The terminal is too small. | Enlarge it and relaunch. |