Security at Codo

Your code is the most valuable thing you share. Here is how Codo protects it, on your computer, on our servers and in between.

On your computer

Codo runs next to your AI coding tool and follows strict rules on your machine.

Only your prompts run

Codo runs prompts you send yourself from the app and asks first by default. Never prompts from other people.

Your logins stay yours

Codo does not read your ~/.ssh folder and does not send the logins of your AI coding tools.

Secrets stay masked

Passwords, keys and tokens are masked before anything is shared. Secret values from your .env files are recognised on your computer and masked too.

Checked before it runs

The installer verifies a signed manifest and a checksum for every file, and updates carry an Ed25519 signature. If one check fails, nothing is installed.

On the way

Every hop between your computer and Codo is protected.

Encrypted in transit

TLS from your computer to Cloudflare, then a Cloudflare Tunnel to our server. Offsite backups are encrypted before they leave the server.

Signed commands

Every command Codo sends to your computer is signed, expires and works only once. Critical commands also need your own signature.

HSTS on every domain

Browsers only ever reach Codo over HTTPS, on every Codo domain.

Strict browser rules

A strict Content Security Policy blocks scripts and styles from other sites.

On our servers

We keep as little as possible, and protect what we keep.

No copy of your repository

Codo stores prompts, agent replies and changed lines with secrets masked, and you can lower this per repository. A full file loads only when someone opens it and stays in memory, never on disk.

Stored secrets encrypted

Tokens and sign-in codes are kept only as hashes. Two-factor secrets, repository tokens and uploads are encrypted with AES-256-GCM.

Roles on every request

Every project has roles, and the server checks them on every request.

No prompts or code in analytics

Product analytics never include prompts, code or names. In the app they run only after you agree.

Your account

Sign-in that is quick for you and hard for anyone else.

Passkeys and two-factor sign-in

Sign in with a passkey or an email code and add a second factor.

Confirm sensitive actions

Sensitive actions ask you to confirm it is you again.

Safe sessions

Session cookies are HttpOnly, Secure and SameSite.

Limits against abuse

Sign-in attempts and email codes are rate limited.

In development

End-to-end, quantum-ready encryption

Locked on your device. Opened on your team’s. In between, the server holds ciphertext.

Two locks, one key

Curve25519 meets ML-KEM-768, the lattice standard NIST finalized as FIPS 203. X-Wing welds them into one key exchange.

X25519ML-KEM-768FIPS 203

Every change signed twice

Ed25519 plus ML-DSA-65 (FIPS 204). Both stamps must verify or the change is dropped.

Ed25519ML-DSA-65FIPS 204

Record now, read never

Tape today’s traffic and wait for a quantum computer? That is the harvest-now-decrypt-later play. Hybrid post-quantum keys are built to blunt it.

60 digits, one glance

Compare a new device’s safety number once. A match means nobody sits in the middle.

Out means out

Remove someone and the project keys roll over. They can’t read what comes next.

One envelope per event

AES-256-GCM, bound to project, epoch and event ID, with per-sender subkeys from HKDF-SHA-256. Copy one elsewhere and it won’t open.

AES-256-GCMHKDF-SHA-256

A signed membership chain

Fork it or roll it back and Codo notices.

Replays bounce

Your connector remembers every prompt ID it ran. Send one twice and it says no.

15 words, new laptop

A 15-word recovery code brings your keys along.

Pings with no payload

Notifications say that something happened, never what.

End-to-end encryption is in development and not released yet. An independent review and audit come before release. Until then, Codo protects your data as described above.

Report a vulnerability

Found a security issue? Email [email protected] privately, not as a public issue. We get back to you as soon as we can.

Machine-readable: security.txt (RFC 9116)

The future of building is multiplayer

Your AI, their AI, one shared workspace