DASHBOARDS

Two dashboards, one record

Every plan gets a local dashboard that reads the event log on your machine. The hosted dashboard shows the same record from anywhere, decrypted in your browser, with more ways to filter and manage it.

Where it runs

Local: On your machine, for a browser on the same machine

Hosted: In your browser from anywhere, decrypted on your device

Plan

Local: Every plan, no account needed

Hosted: Hosted and above

Live updates

Local: Yes, as events are recorded

Hosted: Yes, end-to-end encrypted live streaming

More than one source

Local: Several Omnodex homes on one machine

Hosted: Several machines and streams in one account

Findings and their detail

Local: Community findings, and a count of advanced ones

Hosted: Community findings, and advanced findings on Pro

Shadow-mode filter

Local: No

Hosted: Yes

Investigations

Local: No

Hosted: Pro

Session and stream management

Local: No

Hosted: Archive sessions; rename, pause, rotate or revoke streams

Local and hosted

Overview

The same session totals and risk summary at the top of both. The hosted dashboard adds a time range, and its filters reach across every machine in the account.

Local dashboard
The local dashboard overview with session filters, totals and the connection graph.
Hosted dashboard
The hosted dashboard overview with its sidebar, machine filter, time range, totals across two machines and the connection graph.
Local and hosted

Connection graph

Both show which tools and MCP servers each agent reached, with call counts, and group servers that were configured but never called. The hosted graph starts from each stream and the surfaces in it, and can be panned, zoomed and fitted.

Local dashboard
The local connection graph: Cowork via the MCP proxy, Antigravity and Codex, each linked to the servers and tools they called.
Hosted dashboard
The hosted connection graph for one session: the Demo Stream, its Cowork via MCP proxy surface, and two MCP servers with the tools called and their counts.
Local and hosted

Risk events

Findings with their severity, rule and time.

Local dashboard
The local risk events list with low, medium and high findings.
Hosted dashboard
The hosted risk events list with critical and high findings, each with its rule and category.
Local and hosted

Credential ledger

Credentials seen in tool calls, always masked, with how often they were used. The hosted ledger adds filters by type and server, a search, and first and last seen times.

Local dashboard
The local credential ledger listing two masked credentials with uses and last seen time.
Hosted dashboard
The hosted credential ledger with type and server filters, a search box and a masked API key.
Local and hosted

The call behind every finding

Select a finding, a tool call or a prompt for its full context: severity, rule, description, the related tool call with its parameters, and a link to the Risk Library entry that explains the rule. The detail is the same in both dashboards; the hosted one also shows the rule's plan and the call's status and duration.

Hosted dashboard

Event detail for a critical finding: severity, category, rule, plan, time, a Risk Library link, and the related Bash tool call with its status, duration and command.
Hosted

Streams

Each connected machine is a stream. See when it was last active and how much it has synced, and rename, pause receiving, rotate its token or revoke it.

The Connected Streams section: one active demo stream from two machines, with its last activity, sync size per machine, owner, masked connection token and stream actions.
Hosted

Sessions

Find sessions by time, surface or MCP server, and archive the ones you do not want on the dashboard. Archiving only hides them; collection and sync carry on.

The Sessions list with time, surface and MCP server filters, and sessions from Claude Code, Codex, Antigravity and Cowork with open and archive actions.

Investigations Pro

How the hosted dashboard follows sensitive data across a chain of calls.

Shadow mode and guardrails

What Omnodex would stop, and how it stops the calls you choose.

Screenshots show generated demo data, not activity from a real user.