What's new?

October 2026

• Oct 28, 2026 HostedPro

  Your machine and stream names stay encrypted

  The names you give your machines and streams are now encrypted on your machine with your stream secret before they’re sent, the same way your events are. The hosted service stores only the encrypted form, and the dashboard opens it in your browser. The agent platform and project name in a connect request are encrypted too, and session IDs now stay inside the encrypted sync data.

  Machine IDs are now random rather than worked out from your hostname. A machine that synced before keeps its history: the first sync after upgrading moves it to the new ID.

  You’ll need omnodex 0.11.0 or later to sync to or connect the hosted dashboard. Older versions are refused. Run npm install -g omnodex@latest on each machine.

  Requires omnodex 0.11.0 or later Docs →
• Oct 23, 2026 CommunityHostedPro

  Agents can't quietly switch Omnodex off

  If an agent tries to turn off its own monitoring, Omnodex now tells you. That covers taking Omnodex out of an agent’s hook settings, switching hooks off altogether, disabling the plugin or MCP server through the agent’s CLI, and overwriting the hook file, in Claude Code, Codex and Antigravity. In Claude Code, Codex and Cowork you’ll see the attempt even when the agent’s own permission prompt stops it.

  Removing Omnodex is now a job for a person, too: omnodex uninstall needs an interactive terminal, so an agent’s shell can’t run it. Uninstalling from a script or a fleet tool? Add --unattended. The removal goes ahead, and it’s recorded with a finding so you can tell it apart from one an agent made.

  Requires omnodex 0.10.0 or later Docs → Uninstalling from a script →
• Oct 23, 2026 CommunityHostedPro

  Omnodex checks that it's still watching

  If something takes out or switches off Omnodex’s hooks, plugin or MCP entry without going through Omnodex, whether that’s an agent, a script or someone editing a settings file, you’ll now get a finding.

  Omnodex checks its own setup in the background while your agents run (at most every 15 minutes) and whenever you run omnodex status. omnodex status shows each agent as ok, or tells you what’s missing and the command to put it back.

  Requires omnodex 0.10.0 or later Docs → Monitoring tampering →
• Oct 23, 2026 CommunityHostedPro

  Notice when an MCP server changes

  You approve an MCP server once, but it keeps running whatever its publisher ships next, and your agent follows whatever its tool descriptions say. For servers routed through the Omnodex MCP proxy, you now get a finding when one has changed since your machine last saw it: a new version, an edited config entry, tools added or removed, or a tool description or schema that changed without a new version. That last one is rated higher.

  Open the finding in the local dashboard to see each tool’s old and new description and what changed in its schema. The hosted dashboard shows which tools changed; the descriptions themselves stay on your machine. This can’t see a change to a server’s code that leaves its tools and version alone.

  Requires omnodex 0.10.0 or later Docs → MCP proxy guide →
• Oct 23, 2026 CommunityHostedPro

  AI provider keys, and fewer false alarms when they're used

  Omnodex now recognizes API keys from Anthropic, OpenAI, OpenRouter, xAI, Groq, Perplexity, Hugging Face and Google, plus more kinds of GitHub token. Sending a key to its own service to log in, like a GitHub token going to the GitHub API, no longer counts as the key leaving your machine. And if an agent reads the saved logins of Codex, Claude Code or OpenCode, you’ll see it as sensitive file access.

  A secret in no format we recognize now gets its own low-severity finding, so you can check it or mute it on its own. Raw IP findings also catch IPv6 and addresses tucked inside another URL, and they tell you when an address is on a private network or is a cloud metadata service.

  Requires omnodex 0.10.0 or later Docs → Unrecognized secrets →
• Oct 23, 2026 CommunityHostedPro

  More reliable capture and tool startup

  Short Claude Code sessions no longer lose their last few events: capture now finishes in the background after the session ends. Omnodex’s self-checks also notice when an agent edits settings through an MCP filesystem tool, and you’ll see one warning instead of two when hooks are switched off.

  To pick this up, run omnodex update, then omnodex install claude-code again with the same scope you used before, and start a new session.

  MCP servers with no cached tool list now get up to 45 seconds to connect on a first run, and cached tools still show up right away. If a server is still connecting, omnodex_status tells you which one and when to restart. In Cowork, quit the app completely and reopen it once the server connects. Starting another task won’t refresh the tools.

  Requires omnodex 0.10.0 or later Docs → Missing tools in Cowork →
• Oct 19, 2026 CommunityHostedPro

  Shadow mode and guardrails

  Omnodex can now step in on tool calls, not just record them. Start with shadow mode: your agents run exactly as before, and every finding gets a note saying whether it would have been stopped. That way you can see what guardrails would catch before you trust them with anything. In the hosted dashboard, the Would have blocked filter pulls those findings together.

  When you’re ready, guardrails (on Pro) stop the calls you pick, or hold them until you say yes, and tell the agent why. Nothing is blocked until you decide it should be. Switch between modes with omnodex enforce.

  Requires omnodex 0.8.0 or later Docs → Guardrails →
• Oct 19, 2026 Pro

  Sensitive-data investigations

  Did that credential actually leave, or was it just used to log in? The advanced rules now follow credentials, database files, mail stores and source code from where they were read, through any zipping or encoding, to where they ended up. You get one investigation per chain, with the evidence for each step, instead of a pile of separate findings. The hosted dashboard lists them across all your sessions, and you can narrow them down by stream or machine.

  Requires omnodex 0.8.0 or later Docs → Investigations →
• Oct 15, 2026 CommunityHostedPro

  One command sets up each agent

  omnodex install now sets up each agent’s Omnodex plugin along with its hooks, for Claude Code, Codex and Antigravity, so there’s one command instead of several. Each release comes with the plugin versions it was tested with, and updating Omnodex brings your plugins along. You can also choose to record every project or just one, and leave out the ones you don’t want recorded.

  Requires omnodex 0.7.0 or later Docs →