Flowlight 0.9.6

What's new in 0.9.6

• Every domain an MCP server reaches. An MCP server touches the network four different ways, and Flowlight already learned each of them somewhere different: a URL in a config file, an endpoint the proxy watched this Mac speak JSON-RPC to, a connector declared to the model provider in the request body, and ordinary calls a local server process made itself. All four were being collected; none was offered as something you could act on. They are one list now, under MCP servers in an agent's detail, each domain labelled with which of the four it is known from — and a domain carrying several labels is a stronger fact than one carrying a single label, since configured and contacted says more than either alone.
• Two ways to refuse each one. For that agent and the tools it starts, or for every app on the Mac — different decisions, and the difference is invisible once a rule exists, so both are offered where the choice is made rather than one being discovered later in the rule editor. Both write ordinary rules, so the violations feed reports them and the simulation from 0.9.4 will say what one would have refused before it refuses anything.
• The extension stops asking you to wait for something that cannot happen. Reported three times as "the filter stops working after an update", and each time the version check was examined and found correct. It was. After several updates macOS holds the superseded copies until you restart — activated enabled for the build that matches the app, terminated waiting to uninstall on reboot for the rest — and because it runs one content filter at a time, the matching build is installed without being the one running. Nothing is stale, so nothing is repaired, and the app redialled an extension that could not answer until a restart, six times, then fell back to the sampler without naming the one thing that fixes it. It now recognises that state and says to restart.
• Except where a rule could not reach. A connector the provider reaches on its own never touches this Mac, so that row explains why instead of offering a refusal that would quietly do nothing. The moment the same host is also configured locally or contacted from this Mac, the buttons appear. A local server that only ever speaks over a pipe contributes no domain at all, for the same reason it appears nowhere else: that is not network traffic.

Install

Signed with Developer ID and notarized by Apple.

• brew install --cask xinbetween/tap/flowlight
• Flowlight.dmg — drag to Applications.
• Flowlight-0.9.6.pkg — installs to /Applications; offers to quit a running copy first.

macOS 15 or later, Apple silicon and Intel.

Full changelog: https://github.com/xinbetween/flowlight/releases

Checksums

46130d671f3a06b7203c633a0fb46cb79e0e1cfc840341a47f96983cedc3d412  Flowlight.dmg
9a471a9f31135e0ac273a1d25e581aa3726532e1b60b2e37331650b454fcaa5e  Flowlight-0.9.6.pkg