AI agents
Set http://127.0.0.1:8765/v1 and a non-empty placeholder API key.
BetaEndpoint channel / Windows-first beta
Endpoint Connector links desktop AI agents, IDE clients and the managed browser extension to the central Gateway. Provider keys are never sent to the device.
Connector listens only on loopback. It attributes the device and sends the request for central inspection.
The extension never sees the device token. Connector stores it under %ProgramData% with administrator/SYSTEM ACLs.
OpenAI-compatible and MCP-capable clients use different loopback URLs on one managed Connector. The browser channel uses separate DOM adapters.
Set http://127.0.0.1:8765/v1 and a non-empty placeholder API key.
BetaAn OpenAI-compatible client uses /v1, while an MCP-capable IDE uses http://127.0.0.1:8765/mcp/<slug>. Tool policy is configured centrally.
BetaThe extension checks supported text forms through Connector before submission.
BetaPreventing bypass requires more than an agent: firewall, DNS and MDM/GPO must block direct LLM egress.
| Capability | Status | Boundary |
|---|---|---|
| Windows service + tray | Beta | CI-built ZIP, PowerShell installer and status tray; not yet a signed MSI. |
| Browser prompts | Beta | A DOM adapter for supported sites. It is not a transparent TLS proxy. |
| File upload | Beta | TXT, CSV, MD, JSON, PDF, DOCX and XLSX are inspected in memory; encrypted, embedded and unsupported formats are blocked. |
| macOS/Linux endpoint | Planned | The central server stack runs on Linux; the desktop package is currently Windows-first. |
| Direct egress prevention | Customer control | Enforced by the customer firewall, DNS and MDM, not by Connector alone. |
For an endpoint pilot, we agree the Windows build, MDM/GPO, supported clients and fail-open/fail-closed mode.
Request an endpoint pilot →