Flowstate Agent

The Flowstate Agent is a single binary running on each developer machine. It captures AI traffic, forwards it to the cloud proxy at ai.flowstate.inc, and from there into your Flowstate tenant for attribution, spend reconciliation, and (optionally) policy enforcement.

The agent is the ground-truth source for everything in AI Governance — Insights. One agent, one ledger.

How the agent ships

A single Go binary (flowstate) plus a per-platform daemon supervisor:

• macOS — launchd runs the daemon; flowstate install writes the plist, generates the per-machine root CA, and configures PAC routing. When FlowstateAgent.app lands (gated on Apple notarisation), the same install command auto-promotes to Network Extension mode for kernel-level capture. PAC mode covers every customer-facing AI tool we know about today.
• Windows — A Windows service called FlowstateAgent, installed under C:\Program Files\Flowstate\. Capture uses WinDivert for kernel-level diversion of outbound TCP/443.
• Linux — A systemd unit, PAC mode only.

Roll it out via your MDM. We've validated end-to-end Kandji recipes and ship general guidance for Jamf, Mosyle, Intune for Mac, Workspace ONE, JumpCloud (macOS), Intune + Group Policy (Windows), and Ansible + Puppet (Linux).

Install

Pick your operating system:

• Install on macOS — PAC mode today (v1), Network Extension mode coming (v2). Same install command for both.
• Install on Windows — WinDivert + Windows service.
• Install on Linux — systemd + PAC.

Every platform has the same one-shot install UX:

sudo flowstate install --key="<org-key>" --user="<user-email>"

— and the same one-shot uninstall:

sudo flowstate uninstall

Provision the org-scope key once at https://app.flowstate.inc/settings/ai/cloud-proxy and embed it in your MDM payload. See telemetry keys for the key model and rotation flow.

Two pathways

The agent supports two operating postures, chosen per organisation in Settings → AI → Agent Policy:

• Telemetry — usage metadata only. No prompt capture. Works whether your engineers are on consumer or enterprise AI plans.
• Enterprise — full capture, prompt-quality scoring, policy enforcement, and authoritative usage reconciliation. The one you want if you're on Claude for Enterprise, ChatGPT for Enterprise, or anything else with a real admin contract.

Compare the two pathways →

Configure + operate

After install, work through the configure + operate sections in order:

1. Telemetry keys — issue the org-scope composite key used by every device in the fleet (plus how legacy per-user keys map onto the new model).
2. Agent policy — capture mode, enforcement, per-platform overrides.
3. Corporate proxies — co-existence with Zscaler, Netskope, Forcepoint, Palo Alto, Cisco Umbrella, Cloudflare Zero Trust. Includes the SWG hostname allow-list.
4. Auto-updates — manual today (flowstate install is idempotent), Sparkle on macOS once notarisation lands.
5. Enforcement — turn the agent from observer to gate.

Reference material: environment variables and troubleshooting.