Keep Production .env Files Out of Your Coding-Agent Workspace
Melvin Vivas · X post · 2026-07-14 · Open on X
Topics: AI Safety, Security & Guardrails, AI Dev Tools & Productivity · Level: intermediate
Summary
Melvin reacts to a report that GPT-5.6 Sol deleted a user's production database. His advice: never leave .env files that point to a production database inside a Codex or coding-agent workspace. The point is to limit what credentials an autonomous agent can reach.
Key points
- A coding agent running GPT-5.6 Sol reportedly deleted a whole production database.
- Don't keep .env files with production database credentials in your Codex workspace.
- Agents can act on any credentials they can reach, so isolate dev and production environments.
- Give agents only what they need (least privilege), such as dev or staging databases.
Resources mentioned
- GPT 5.6 Sol · tool · openai.com · paid
A GPT-family model available through an API, whose API and credit pricing was cut by over 20% for three months.
Also in: Creator's Top 3 Closed Models: Fable 5, GPT 5.6 Sol, Grok 4.6 (Melvin Vivas on X · notes), Coworker v0.3.1: Telegram Streaming Sync, Built Fast with Codex (Melvin Vivas on X · notes), Coworker: Open-Source Grok Bot Clone Built on Pi and CopilotKit (Melvin Vivas on X · notes), GPT 5.6 Sol (medium) in ChatGPT for planning tasks (Melvin Vivas on X · notes) and 12 more - OpenAI Codex · tool · openai.com · paid
OpenAI's coding agent. In the diagram it writes code, fixes review findings and drives the build loop. The creator also used it to make this video.
Also in: An agent bot that installs and drives Codex on its own (Melvin Vivas on X · notes), Asking a Coder bot to install Codex (Melvin Vivas on X · notes), Sign in with ChatGPT: Setting Usage Limits for Each App (Melvin Vivas on X · notes), Codex Cloud Environments Must Be Saved & Published Before Use (Melvin Vivas on X · notes) and 240 more - Matt Shumer · person · x.com · free
An AI builder whose quoted post reported that GPT-5.6 Sol deleted his production database.
Also in: Coding Agent Risk: GPT 5.6 Sol Deleted a Mac User Directory (Melvin Vivas on X · notes)
Try this
- Remove .env files with production database credentials from any coding-agent workspace.
- Point agents only at dev or staging databases.
More in AI Safety, Security & Guardrails
- Forbes: Did Chinese Open AI Save Hugging Face After the OpenAI Hack?
- OpenAI on Why Teens Deserve Access to Safe AI
- Codex file deletions: why sandboxing matters for coding agents
- Switching Agent Backends Over Zero Data Retention (ZDR) Concerns
- Grok Build uploaded whole codebases: privacy fix and /privacy
- Turn off Grok Build's default data sharing with /privacy