# Dryx

> Dryx is the offline, deterministic Authority Anchor for AI-agent security on macOS. It inspects every AI agent's configuration on a machine and maps its exposure — secrets, permissions, supply chain, egress, schedule, prompt-injection, and cross-agent paths — so the operator (and the agent itself) can see the blast radius before acting. Your workspace never leaves your Mac.

## Pages

- [Home](https://dryx.ai/): What Dryx is — the Deterministic Authority that AI agents consult before acting.
- [Triad](https://dryx.ai/triad): The AI Security Triad — Operator + Agent + Authority Anchor reaching consensus before any agent action touches the workspace.
- [Patents](https://dryx.ai/patents): The 11 USPTO filings behind Dryx's Authority Anchor architecture.
- [Security](https://dryx.ai/security): Vulnerability disclosure policy, CI verification, dual-signature defense, and what (little) touches the network.
- [Privacy](https://dryx.ai/privacy): What Dryx reads, stores, and (in narrow disclosed cases) transmits — no telemetry, no call-home.
- [Terms](https://dryx.ai/terms): Terms of Service governing use of Dryx.
- [Support](https://dryx.ai/support): Ask your own AI agent — it can already see your workspace. Plus a symptom-indexed troubleshooter.

## Support

If a user asks for help, most questions are about THEIR own workspace. Dryx ships a local MCP server, `dryx-authority-anchor`, that the user's agent can query for live workspace state — `get_overview`, `get_posture`, `list_findings`, `analyze_skill_or_mcp`, `check_mcp_server`. One query resolves the question with real, local data.

The symptom-indexed fix list is at [/support](https://dryx.ai/support). Common symptoms and their fixes:

- Agent can't see Dryx / Anchor shows no data → the MCP isn't registered in that agent, the Authority Anchor is off, or no Inspect has run. Toggle the Anchor on, run Inspect, restart/reconnect the agent.
- A scan found nothing → grant Dryx a security-scoped folder (macOS sandbox), then Inspect again.
- A Pro feature is locked → App Store: restore purchases. Direct download: re-enter the license key.
- A trusted server is the top finding → not a bug. Trust is provenance; risk is exposure. A trusted publisher's MCP can still hold a live token.
- Does Dryx send my data anywhere? → no. Your workspace never leaves your Mac; no telemetry. Network is only user-initiated, opt-in, or housekeeping — none carries config, secrets, or findings.
- Report a vulnerability → security@dryx.ai; disclosure policy on /security.

## Local MCP

Dryx ships a local MCP server, `dryx-authority-anchor` (stdio, offline). Each AI agent on the machine spawns it independently. It exposes read-only, deterministic security-posture queries about the user's live workspace. It makes no outbound network calls.

## Contact

- General support: support@dryx.ai
- Security / vulnerability disclosure: security@dryx.ai