If you spend your day in a terminal, NAOMS now has a home there. It is called the TUI, short for terminal user interface: a full-screen app drawn with text and driven entirely by the keyboard.

It is the surface the maintainers use for their own work every day.

One daemon, two windows

The TUI does not hold your data. It connects to the same local NAOMS daemon your browser talks to. The daemon is the background program that keeps your identity, your hives and your relationships.

So nothing is split in two. Set something up in the browser and it shows up in the terminal. Approve something in the terminal and the browser sees it.

A morning with it

Maya checks that her daemon is up, builds the app once, and launches it. The app finds the daemon on its own.

1. It opens in chat. She presses F2 to pick a model and a device.
2. She presses Ctrl+K and lands in the cockpit.
3. The cockpit has four panes, reached with the number keys: what needs a human, what is running now, what is queued, and what is scheduled.
4. A row in the attention queue asks for approval. She focuses it and presses a.
5. Not sure of a key? She presses ?. The help overlay lists every binding, generated from the same code that handles the keys, so it always matches her build.

From any pane, function keys open bigger screens: questions waiting on a person, the board of every work item, fleet operations. / filters rows, and Esc steps back out.

Drive it from a script

Builders get a second feature. The tui-control package adds a naoms tui command family that starts a cockpit and presses keys for you. It can type, capture the screen, wait until the screen matches a pattern, and report state as JSON.

That makes terminal end-to-end tests ordinary shell scripts: start, send keys, wait, check. Distinct exit codes let scripts branch on what happened.

Control goes through the same authentication as a real keyboard. Commands that could reveal secrets on screen need explicit opt-in flags, and the opt-in is logged.

The shell-control package is marked experimental.

Who it is for

• People who prefer a keyboard cockpit to a browser tab.
• People who reach NAOMS over SSH.
• Builders who want to script or test a real interface.

Why it matters

A good tool meets you where you already work. The terminal is where many of us live, and now NAOMS lives there too, with the same identity and the same state as everywhere else.

What's next

• Coming next: onboarding in the terminal. Creating your identity and writing down your recovery phrase still happens in the browser, and the TUI expects an identity to exist already.
• Coming next: easier install. Today you build the binary yourself.
• Coming next: a cockpit view shaped for everyday users. Much of it is aimed at running NAOMS's own development for now.

Written by AI agents from real project logs; owned and edited by Mujo.