What is Pentect? — Pentect

Skip to content

Appearance

Get started

MenuReturn to top

Pentect runs locally between an AI coding tool and its model provider. It replaces secrets and sensitive data with handles before a request leaves your computer. A handle is a safe reference such as >.<br>Use Pentect when an agent needs a credential or sensitive file. The agent can use the handle without receiving the real value.<br>Why normal masking is not enough ​<br>Normal masking hides both the value and its name:<br>dotenvDATABASE_URL=[REDACTED]<br>The model cannot use this value in a command. Pentect keeps a named reference:<br>dotenvDATABASE_URL=><br>The model can copy this handle into a tool call. Pentect restores the real value just before the local tool runs. The model provider does not need to see it.<br>Scope ​<br>Pentect protects supported AI requests. It is not a password manager or secret vault. Keep using normal permissions, sandboxes, and access controls.<br>Pentect does not give an agent new access. It only changes what the model provider can see. Local tools still use the permissions of the current user.<br>One request, end to end ​<br>StepWhat Pentect doesLocal inputFinds supported sensitive values and creates handlesRequest to the providerSends handles instead of known real valuesModel responseKeeps handles in text and tool argumentsBefore a local tool runsRestores handles that the current session knowsTool resultChecks and masks output before the next requestThe client UI stays the same. Pentect starts the client with a local gateway for that process only.<br>Supported surfaces ​<br>Pentect supports Codex CLI, Claude Code, Codex App, and selected Claude Desktop features. It also offers local masking commands, custom gateways, and safe plugins.<br>See Compatibility for the release-tested matrix.