The console

The console is the whole product for anyone who does not use a terminal, and it is deliberately small. It answers the same four questions everything else here does: what can this agent do, what is it doing, why is that allowed, and what happens if we give it more. A console that needs a tour has stopped answering them.

One tree

There is one place to stand, so there is one tree. An organization holds a single workspace, made with it and named after it, so there is no level to go down into and no way back up to draw.

The order is the argument: what can act, what it may do, what it caught, what it reads, and the organization under all of it. What it reads is fourth and not first. A row near the top reads as step one, and connecting a system is not how an agent gets governed. What governs an agent is a runtime on the machine it runs on, which is why Fleet opens the tree.

The last group is named for the level it answers for rather than for the person signed in. Everything in it belongs to the organization: who is in it, what it pays, and how it is set up. The menu under the avatar is where what is only yours lives.

Routes stay flat. Which workspace a page answers for is the selection rather than a path segment, so nothing is opened on anybody's behalf.

The record

What happened is not a screen of its own. What was caught ends with every action each machine reported, newest first, with the rule that decided it and a trace of what led to it and what it set off. The sinks and webhooks the record is forwarded to are listed in Settings, under General, once one exists. The chain itself is sealed on the machine that wrote it, and an exported bundle carries the key that checks it (see Activity and audit).

A link that asks about one agent or one verdict opens that tab already narrowed: an agent's page links to every action it took, and the home page's denied count opens on what was denied.

What stayed a page

After setup Memnox runs itself, so the pages show only what needs a person right now and draw nothing where nothing is owed.

Waiting on you is one page with no tabs. It stacks a section for each kind of thing a person owes, and each section appears only while it has something in it: agents blocked on a question on a machine nobody is sitting at, approvals, rule changes waiting on a second administrator, decisions to confirm, facts to settle, an MCP server nobody approved, an exception waiting on a second admin, and any condition in force, with Lift to end it early. When every section is empty the page says Nothing needs you. Memnox is running. A condition is declared in chat with /memnox freeze, or through POST :ws/state; the console only lifts one.

Autonomy is one view: what proceeds on its own, what stops for a person, and what is refused, then What you could stop being asked about only while there is something to hand over. The rules, their history and need to know topics have no screen; they are read and written through the API.

Machines, Agents and What was caught are pages because each is a fleet wide list rather than one step of one action. An agent's own page is where it is given owners and frozen on the machine it runs on, while /memnox freeze-agent in chat freezes it on every machine (see Who acts here). What was caught opens with the incidents a detector opened, only while one is unresolved. An incident opens a drawer with its evidence, Acknowledge, Resolve, and Contain it: one press freezing the agent involved on every machine and one moving every machine to enforce. The MCP server inventory, exceptions and spend have no screen of their own, because they run by themselves (see MCP servers across the team and Writing policies).

Sources is a page and not a row for a different reason: it is step two of ingestion, and both it and Connectors carry the tab strip that links them, so a second row would have named one act twice. Connectors is the row because it is where somebody starts. Files is its own row rather than a panel at the foot of Sources, since uploading a handbook and naming a Slack channel are the same act to Memnox and not to the person doing them.

File locks and Usage are pages and not rows. A file lock only matters where two machines write one repository, and it is a Team feature, so on every other plan the row led to a page that was empty and gated at once, which is the worst pair a navigation item can be. It is linked from Machines. What a workspace has spent is a billing question and sits one click from the plan.