Kryex is the agent. There's no other path in.
Kryex isn't a policy layer bolted onto whichever editor or agent a team already runs. It's self-hosted, and it is the coding agent — so there's nothing to configure, and no separate route to a model or a tool call that could bypass the gate.
The live trace
Every action a developer takes runs through the same two-step check, every time: Kryex's own Tool Proxy classifies the call, then the Policy Decision Point (PDP) resolves it against the developer's live grant before it executes.
Kryex CodeKryex is the agent
- For
- Teams adopting Kryex as their coding agent, not bolting it onto an existing one.
- Setup
- Nothing to configure — Kryex already is the client.
- Enforcement
- Structural. Every read, write, and execute passes through Kryex's own Tool Proxy → PDP before it runs.
Why this is structural, not agent-mediated
There's no separate client for a developer, or a model, to talk its way around — Kryex already is the client. A prompt never has anywhere else to go: it's classified and authorized by the same Tool Proxy → PDP path before it ever reaches a database, a command, or a connected tool. See How Kryex Works for the full brain-and-hands architecture behind this.
MCP servers are a connection type, not a deployment path. Kryex connects to and governs MCP servers the same way it governs a database or a browser — same grant model, same audit trail — covered in Tool Calling & Governed Actions. That's a separate concept from how you adopt Kryex itself, which this page covers.
Any model, still no lock-in
Being the agent doesn't mean picking a model for you. Kryex's own Model Gateway governs whichever provider you already pay for — see Bring Your Own Model for the exact mechanics.