DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to keep .env and key files out of ChatGPT reviews with Codex with ChatGPT

Use the default sensitive-file rules plus your own .c2cignore patterns to protect secrets.

Credentials. Your own .c2cignore patterns are only as complete as the ones you write, so review them before sharing any repo with ChatGPT.

Who it is forA developer working in a repo with .env files, keys, or credentials who wants ChatGPT reviews without exposing those files.

The problemReviews could expose secrets if the bridge can read them, and the default rules may not cover every file type your project uses.

The outcomeSensitive files stay out of ChatGPT's reach, and your own project-specific patterns are added to the rules.

What you need first

  • Node.js 20 or newer
  • git
  • cloudflared (the Codex Skill installs it for you)
  • A ChatGPT Plus or Pro subscription for the web app
  • Codex, with the ability to install a Codex Skill

Steps

  1. Confirm the default rules: .env*, keys, SSH, and credentials are denied, and .env.example is allowed.
  2. Add your own patterns for other sensitive files to .c2cignore in the workspace root.
  3. Run c2c status to confirm the bridge is running for this workspace.
  4. Run c2c doctor to check the setup. (inferred, check the README)
  5. Ask Codex to use Codex with ChatGPT to review a file, and confirm that no ignored file is read.

Prompt for your agent

In the workspace at <workspace path>, add the pattern <pattern> to .c2cignore, then run c2c status and c2c doctor and report their output. Confirm that the sensitive-file rules still deny .env files.

Caveat. The README lists the default denied file types but does not describe the exact .c2cignore syntax, so check the docs before you rely on a complex pattern.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page