Support that proves itself

Ask your agent. It can already see your Dryx.

Dryx installed a local source of truth your AI agent can query. Most support questions are about YOUR workspace — so ask the thing that's already in it. The answer comes from your machine, offline.

Ask your agent

Paste one of these into Claude Code, Cursor, or any agent where Dryx is registered. Each one resolves against your live workspace through Dryx's local Authority Anchor.

Copy a prompt. The capability tag shows which Dryx tool answers it.

Why does my Authority Anchor show no scan data?
get_overview An empty result is itself the diagnostic: no scan yet, no folder access, or Dryx isn't registered in that agent.
What does my top finding actually mean for me?
list_findings Dryx answers for YOUR workspace, not generic categories.
Is this MCP or skill safe to install in my workspace?
analyze_skill_or_mcp check_mcp_server The pre-install verdict, before anything touches your machine.
What's my posture score, and why isn't it 100?
get_posture list_findings The score, plus the findings holding it down.
No agent handy? See the troubleshooter below.
Agent-readable docs dryx.ai/llms.txt
Found a security bug? [email protected]

Common things you'll see

Indexed by the exact thing on your screen — not a generic FAQ. Each one: what it means, the one fix, and the agent prompt that resolves it live.

My agent can't see Dryx / the Anchor shows no data

What it means The MCP isn't registered in THAT agent, or the Authority Anchor is toggled off, or no Inspect/scan has run yet.

The fix Open Dryx, toggle the Authority Anchor on, run Inspect, then restart or reconnect the agent so it re-spawns the MCP.

Ask your agent: "What does Dryx's get_overview return?" — an empty result confirms one of the above.
A scan found nothing / I didn't grant folder access

What it means Dryx needs a security-scoped folder grant (macOS sandbox). Without it the scan completes but sees nothing.

The fix In Dryx, grant access when prompted (or Settings → re-grant), then Inspect again.

A Pro feature is locked / my license won't activate

What it means App Store builds use StoreKit; direct-download builds use a license key.

The fix App Store → restore purchases. Direct download → re-enter the license key.

A trusted server is my top finding — is that a bug?

What it means No. Trust is provenance — who published it. Risk is exposure — what it can reach. A trusted publisher's MCP can still hold a live token and be your top finding.

The fix Nothing to fix in Dryx — that's the design working. Act on the exposure the finding describes.

Does Dryx send my data anywhere?

What it means No — your workspace never leaves your Mac. Dryx makes no telemetry or call-home. The only network is user-initiated (fetching a remote skill/MCP you asked it to analyze), opt-in (the Ecosystem Contribution, off unless you turn it on), or housekeeping (update and license checks) — none of it carries your config, secrets, or findings.

The fix Nothing to fix. The full breakdown is on the Privacy page.

How do I report a vulnerability?

What it means Dryx runs a coordinated-disclosure process for good-faith reports.

The fix Email [email protected]; see the disclosure policy on the Security page.

Still stuck?

Questions →