Module tui 

Full-screen ratatui dashboard — the default interactive UI.

Management on the left: every server and client as a card with its buttons and sections, always visible. On the right, one stream of what is happening and of the conversation, with the input box at the bottom. See src/tui/AGENTS.md for the design.

Modules

actions

Every instance action, executed in one place.

activity

The activity feed: what the machine is doing, as it happens.

app

Dashboard application state: where the cursor is, what the last poll saw, and which modals are open.

cards

The instance canvas: every server and client, always visible, each as a card with its buttons and its sub-sections.

chat

In-memory chat/log history for the dashboard.

command_exec

Sink-based execution of the remaining UserCommand variants.

commands

Chat submit path: history, UserCommand parsing, LLM dispatch.

driver

Who answers an instance’s events, in one word.

event_loop

Terminal lifecycle and the main select loop.

hit

Mouse hit-testing.

keymap

Keyboard and mouse handling for the panes.

llm_activity

Shared activity labels and animation for the cards, chat and footer.

metrics

Per-instance throughput: one sample a second, a rate, a sparkline.

modal

Overlay modals: the dashboard’s drill-in and editing surfaces.

modal_keys

Input handling for every modal.

projection

Poll-based projection of AppState into owned display data for the rail.

rail

The one-line instance summary: status glyph, id, protocol, address, live peers, sparkline, driver badge. A card’s header row is one of these.

render

Frame composition.

theme

Adapter from the shared crossterm ColorPalette (with termbg auto-detection) to ratatui Styles. ratatui 0.29 converts crossterm::style::Color losslessly via From.

uimsg

Results of work that must not run on the event loop.

wireshark

[ view in wireshark ] — a paste-ready capture command for one instance.

Functions

run_dashboard

Entry point: the interactive UI.

run_dashboard_on

The dashboard on a caller-supplied terminal and input stream: the browser build’s entry point (crates/netget-web), where the terminal is xterm.js and the events come from the DOM. Same construction as run_dashboard; on_ready receives the status and UI channels once the loop is about to start.

Type Aliases

DashboardReady

Channels a hosted page uses to report status and request dashboard forms.