Your coding agent can read your .env. Here’s what we did about it

Описание и применение

Пенв защищает секреты от утечки при работе AI‑агентов, разделяя схему переменных от их значений, валидируя окружение, маскируя вывод и генерируя правила защиты для конкретных harness‑ов.

Задача

Coding agents run in the same user context as developers, so they can read .env files and leak secrets through logs, transcripts, or stack traces.

Результат

penv protects secrets from being read or leaked by coding agents by separating the schema from the values, validating before execution, masking output, and generating harness‑specific guard rules.

Рабочий процесс

• Run penv init to read the existing .env, generate .env.schema, and gitignore .env.
• Use penv run -- <command> to validate the environment, inject values, and mask any sensitive output when an agent session is detected.
• Generate typed accessors with penv gen ts or penv gen py to replace direct process.env usage.
• If using a team, run penv login and penv push to store secrets in penv.cloud and delete local .env.
• Use penv reveal KEY under an agent session to request a secret with human approval.

Доказательства

penv init # reads .env, writes .env.schema, gitignores .env

Источник

penv run -- pnpm dev # validates, injects, masks

Источник

penv guard writes what each harness actually enforces

Источник

penv keeps secrets out of the files, the repo, the shell history and the captured output an agent reads.

Источник