About GUI
Tuoni's interface is developed alongside the server, so every feature the C2 and the agents gain is available in the GUI as soon as it ships. Everything it does is also available over the REST API, and the API is the contract - if you would rather drive Tuoni from a script, or build your own interface, nothing here is in the way. See the API Reference and the Tuoni Library.
The design comes from more than a decade of red teaming and cyber exercises. It is built for long sessions and large operations: a thousand agents, several operators on the same server, and a console that has to stay usable while all of that is happening.
This section
Roughly in the order a new operator meets them:
| Page | What it covers |
|---|---|
| Login | Connecting the client to a server, and to more than one |
| Menu | The navigation rail and the connection list |
| Agents | The agent table, multi-select and the row actions |
| Topology | The same agents as a graph, and who pivots through whom |
| Terminal | Sending commands and reading what came back |
| Terminal Shortcuts | Everything the keyboard does |
| File Browser | Browsing a host's filesystem |
| Side Panel | Working in two sections at once |
| Settings | Settings, the command palette, the shortcut sheet |
| Listeners | What agents call home to |
| Payloads | Building the artefacts that become agents |
| Files | Stored files, and hosting them over HTTP |
| Discovery | Hosts, services and credentials |
| Commands & Aliases | The command catalogue and your shorthands |
| Plugins | What this server has loaded |
| Users | Accounts and permissions |
| Scripts | The server-side script execution monitor |
Themes
The client ships several themes, including light and high-contrast variants and one for deuteranopia. The screenshots throughout this section are taken in the default dark theme.
Themes are switched from Settings or straight from the command palette, and the choice is remembered per browser.