Skip to content

Roadmap: 0.9 - #7

Merged
blessdyb merged 2 commits into
mainfrom
docs/roadmap-0.9
Sep 27, 2026
Merged

blessdyb merged 2 commits into
mainfrom
docs/roadmap-0.9

Conversation

@blessdyb

Copy link
Copy Markdown
Contributor

Adds the 0.9 line to the README roadmap and the website, from the 0.8.1 security review plus what fixing it exposed. No code, no version bump — documentation only, so it doesn't need a release.

  • 0.9.0 — Coverage, stated rather than assumed. Per app: watched by the extension, decrypted by the proxy, named only by DNS or SNI, or not covered at all — and why. Today you have to read several honest paragraphs elsewhere to know which of those applies to anything.
  • 0.9.1 — A threat model, written down. What it defends against and what it doesn't, with "monitoring, not prevention" said beside every mention of blocking. Plus a security contact for people who can't use GitHub's private reporting, and self-hosted fonts — a local-first tool shouldn't make a third-party request to render its own privacy page.
  • 0.9.2 — A budget for inspection. Recorded bodies are the most sensitive thing Flowlight holds, and the redaction protecting them is a guess at which headers carry credentials. Allowlist, own patterns, keep-no-headers, per-app ceilings, an expiring session.
  • 0.9.3 — Show me what this rule would have done. Replay the last day against a rule before it refuses anything.
  • 0.9.4 — What leaves the Mac, before it leaves. The export disclosing itself the way Flowlight makes everything else disclose.

🤖 Generated with Claude Code

blessdyb and others added 2 commits September 27, 2026 00:54
Five entries, and what they have in common is that each one turns a claim Flowlight makes into something it
can show. Coverage per app rather than "every connection". A threat model that says what it does not defend
against, and product language that says monitoring rather than prevention beside every mention of blocking.
Limits you set on the recorded bodies, which are the most sensitive thing it holds. A rule you can watch
before it refuses anything. And the export disclosing itself the way Flowlight makes everything else disclose.

Most of it comes from a security review of 0.8.1, the rest from what the 0.8.2 fixes exposed: the redaction
that protects recorded bodies is a guess at which headers carry credentials, and a guess is not a budget.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Flowlight can say an agent uploaded 40 MB somewhere unfamiliar. It cannot say it read ~/.ssh/id_rsa first, and
a file leaving is a read followed by a send — so today it watches half the event and names it in full.

Deliberately not a resource monitor. CPU, memory and energy per process are Activity Monitor's job, already on
every Mac and done well; adding tabs for them would make this a worse Activity Monitor with one good tab. The
one number of that shape worth having belongs beside the away-activity alert, not in a tab.

The two gates are in the entry rather than waiting to be discovered: EndpointSecurity needs an entitlement
Apple grants on review, and the data it yields is sensitive enough that 0.9.2's inspection budget becomes a
prerequisite rather than a nicety.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@blessdyb
blessdyb merged commit 858859d into main Sep 27, 2026
3 checks passed
@blessdyb
blessdyb deleted the docs/roadmap-0.9 branch September 27, 2026 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant