Allowlists check where. Nosi checks who.
Stolen tokens rarely go to evil.example. They go to a GitHub gist, a Slack webhook or webhook.site: hosts every firewall, and every developer, already trusts.
The giveaway is who's doing the calling. A node process, started by some package's install script, three steps down from the npm install you typed. Nosi follows the whole family tree, so it notices. The same goes for pip install.
For when your agent goes off-script.
An agent that reads the wrong README can be talked into sending your keys somewhere. It won't use a shady domain. It'll use GitHub, like it does all day.
A sandbox allowlist has to let github.com through, so it can't tell your push from that one. Nosi looks at the command and the repo. It recognises Claude Code and Codex by their code signatures and keeps a closer eye on what they start.
Stepped away? When your screen is locked, you've been idle a few minutes or the Nosi app is closed, unanswered questions from agent tools are denied. Your own apps and browser carry on as normal.
-R, a link or a re-pointed remote.Peek, ponder, pipe up.
Most connections never bother you. Nosi saves the questions for the ones that deserve them.
Every connection, traced home
Each outgoing connection is matched to the program that opened it, its code signature, its command line and every process that launched it.
Rules first, then a second opinion
Your choices and the built-in rules decide first, right on your Mac. If nothing matches, an AI model (Jev) gets a few narrow questions about a masked summary. Its answer is remembered, so the same connection isn't asked about twice.
Asks you, plainly
When a rule says “check with a human”, or Jev isn't sure, you get a prompt. It names the program, the host and what happens if you don't answer. Allow once, deny, or make it a rule.
No riddles when it matters.
Nosi is chatty when nothing's at stake. When you have to decide, it gets to the point.
node wants to connect to api.github.com
Started by an npm install script.
- Program
- /opt/homebrew/bin/node setup.js
- Package
- [email protected] (postinstall)
- Destination
- api.github.com:443
- Started by
- zsh → npm install → sh
A rule asks you to confirm this. Install scripts rarely talk to the GitHub API; stolen tokens often leave as new repos or gists. Jev thinks it looks unusual too.
Nosy by design.
Everything a busybody needs to keep the street safe, and nothing that reads your mail.
Family trees, not just names
Sees the parent, grandparent and great-grandparent of every connection, so a sneaky child process can't hide behind a famous name.
Install scripts on a short leash
Anything an npm postinstall or a pip install build spawns is tagged with its package and version. If nobody answers, its unexpected connections are denied.
Rules you can actually read
Policies are written in Cedar. Your clicks beat your rules, your rules beat the built-ins, and community packs come last.
Side-eye alerts
Ordinary traffic gets a quiet second look in the background. If it looks off, Nosi flags it without breaking anything.
Replay before you commit
Try new rules against your real history and see exactly which decisions would change before you turn them on.
Guardrails for coding agents
Claude Code and Codex are recognised by their code signatures. Pushes to unfamiliar repos, GitHub API writes and uploads to new hosts are checked with you first.
History you can search
Every decision, who made it and why: denied, allowed, asked, overridden. Filter, search and copy the details.
You get the last word
Disagree with a rule? Override it. Nosi warns you once, then does what you said.
Read the room at a glance.
Nosi lives in your menu bar. Its face tells you how things are going without opening anything.
Watching
Filter on, all quiet.
Asking
A question is waiting for you.
Side-eye
Allowed, but something looked off.
Asleep
Filter off. Nosi's napping.
Nosy, not leaky.
A firewall that spills your secrets would be a funny kind of neighbour.
- No snooping inside your trafficNosi never decrypts TLS. It looks at who connects and where, not what's inside.
- The AI second opinion sees a summary, never your dataJev gets the program, what started it, the destination and the command line, with token-shaped values masked before anything leaves your Mac. It never sees connection contents.
- Your key, your choiceJev uses your own key. Skip it and nothing is sent anywhere: the rules still run, and Nosi asks you instead. You can also switch off the background second looks.
- History stays homeYour connection history and rules live on your Mac, nowhere else.
- Easy to switch offTurn the filter off any time in System Settings → Network Extensions.
Questions over the fence.
What's Jev, and do I need it?
Jev is a hosted AI model from TypeSafe that answers narrow questions such as “is this program likely to be uploading local data?”. Nosi only asks it about connections its rules haven't already decided, and only with a masked summary. You add your own Jev key during setup. Without one, the built-in rules still protect install scripts and coding agents, and Nosi asks you about the rest instead of guessing.
How is this different from other Mac firewalls?
Most firewalls decide by program and destination: “allow node to talk to GitHub”. Nosi also looks at who launched the program, which package it came from and what command it's running, because that's where supply-chain attacks and misled agents give themselves away.
My agent already has a sandbox. Do I need this?
They work well together. An agent sandbox limits which domains its commands can reach, which is a good fence. Nosi watches everything on your Mac, including install scripts you run yourself, and it can tell a push to your repo from a push to a stranger's on the same domain.
What if I'm not around when it asks?
After 60 seconds Nosi applies the default. With the standard “Balanced” setting, install scripts and anything a rule flagged are denied, and so are agent tools while you're away. Ordinary traffic is let through and still gets a quiet second look. Prefer fewer denials? The “Relaxed” setting only denies install scripts.
Will it slow my Mac down?
Rules run locally and fast. Jev is only consulted for connections nothing else has decided. Its answers take a fraction of a second and are remembered, so the same connection isn't judged twice.
What doesn't it catch?
Nosi sees connections, not their contents, so a few things are out of its reach: data hidden in DNS lookups, data tucked into the address of a site you already use, and anything inside a container or on CI. A script quietly posting to a new website while you're at your desk is left to Jev and to you. We'd rather you knew.
What do I need to run it?
A Mac with Apple silicon on macOS 13 Ventura or later. On first launch, approve Nosi's network extension in System Settings → Privacy & Security. The welcome checklist walks you through it.
Does quitting Nosi turn it off?
No. Quitting closes the window and menu bar icon; the filter keeps watching. To stop it, turn Nosi off in System Settings → General → Login Items & Extensions → Network Extensions.