KodaCode
Coming soon
Redaction

Agents read everything. Your secrets stay out of it.

Most leaked keys don't start with a hacker. They start with someone trying to get a build working.

An agent opens your .env to work out why a test fails. It prints the environment to see what's set. It hardcodes a token because that made the error go away. Nobody meant any harm, and your production key has now left the building.

Out of the model's sight.

Turn on Mask secrets and keys, tokens and passwords are taken out of every request before it leaves your machine. The agent can still use a key you give it, without ever seeing it.

Out of your commits.

When the agent finishes changing files, a secret scanner checks them and tells you the file and line, while it's still easy to fix.

Give the agent the work. Keep the keys.

The model seesA placeholder, or a mask
Your commands getThe real value, on your machine
StoredEncrypted, with the key in your keychain
Changed filesScanned when the agent finishes
01Why it matters

One key is rarely just one key.

A cloud key can reach your customer data. A CI token can put code in front of every customer you have. A database password can sit in the same file as five others. Whoever holds one of these looks like a legitimate employee in your logs, which is why these breaches go unnoticed for so long. Then comes the part nobody budgets for: rotating everything that key touched, working out what was accessed, telling customers, and answering your auditor when they ask who has had access to that credential.

02How agents leak them
Sent to the modelWhatever the agent reads goes into the request. Your key is now on someone else's servers, under their retention policy, outside anything your security team controls
Committed to gitDeleting it in the next commit doesn't help. Git keeps the history, and so does every clone, fork and CI cache that already has a copy
Pushed to a private repoPrivate isn't safe. GitGuardian found hardcoded secrets in 32% of internal repositories, against 5.6% of public ones, and everyone with repo access can read them
Written faster29 million new secrets reached public GitHub in 2025, up 34% in a year. Commits made with one popular coding agent leaked at about twice the usual rate, 3.2% against 1.5%
Left working64% of the secrets GitGuardian found leaked in 2022 still worked in January 2026. A leak stays dangerous until someone rotates the key · the report
03Mask secrets

Strip them out before anything is sent.

Your messages, file contents and command output all pass through masking on your machine, right before each request goes to the provider. It's one switch in Settings, off until you turn it on. If masking can't finish, the text is replaced with a marker or the request isn't sent at all. It never falls back to sending the original.

04What gets masked
Known key formatsDozens of them, including OpenAI, GitHub, GitLab, AWS, Google, Slack, Stripe, npm and PyPI
Credentials in contextAuthorization headers, private keys, JWTs, and passwords inside database URLs
Files made for secretsWhen the agent reads .env files or shell profiles, or dumps the environment, any value under a name like KEY, TOKEN or PASSWORD is masked, whatever its format
Keys you've already given itOnce KodaCode holds a value, it's hidden wherever it turns up again, including in command output
What it can't catchMasking works by recognising secrets. A password in ordinary source code, with no known format, can get through. Keep those out of the code, and let the scanner and /review catch the rest
05Using a key safely

The agent can use a key it has never seen.

Click the shield and paste, and your message holds [secret 1] instead of the value. The model gets a placeholder like «secret:1» and writes that into its command. KodaCode swaps the real value back in on your machine just before the command runs. The value itself is stored encrypted, and the key that opens it stays in your system's keychain. A key you type straight into a message is picked up the same way, if KodaCode recognises it.

06Before it reaches your history
After every changeWhen a turn changes files, the secret scanner checks them and shows what it found, with the file and line · see it catch one
Branches and commitsRun /review on a branch or a commit and the scanner goes through those commits too
You decideThe scanner warns you and doesn't block anything. Move the value out, and rotate the key if it has already been pushed
The scan stays localThe report leaves the value out, and a key it finds is never sent to its provider to check whether it works
Masked values stay maskedIf the model tries to write a masked value into a file, the write is refused, so you don't end up with a broken key in your config

Let it read the repo. Not the keys.

macOSDesktop appComing soon
WindowsDesktop appComing soon
LinuxDesktop appComing soon