Agent running tests in a repo copy still hit the live database via env vars
Stunning-Sherbet1853 · reddit · 2026-10-09
Two devs building a local-model desktop agent let it fix a bug in a repo copy — but pytest's temp instance read the data-folder path from the inherited environment and attached to the live database, marking an in-progress task failed. The agent's own token was also sitting in the env, handed to every command. Fixes: blocklist prefixed vars, clear them in test setup, add a regression test. They also note Codex CLI passes everything through by default, with allowlisting as opt-in. Open questions: blocklist vs allowlist, isolation without containers, and whether self-editing agents need special handling.
More from coding & agent
- PartyKit shuts down free hosted platform 2.5 years after Cloudflare acquisition — threepointone · 2026-10-09
- Run a Brand X Account With 3 AI Bots: Community Manager, Content Strategist, Analyst — FinanceYF5 · 2026-10-09
- Google's A2A protocol moves to neutral foundation alongside MCP under AAIF — SnooDingos9560 · 2026-10-09
- Who owns the job after the agent disconnects? A Kubernetes MCP architecture — stevenacreman · 2026-10-09
- LangChain Founder: Evals Work for Narrow Tasks but Break Down for Autonomous Agents — hwchase17 · 2026-10-09
- Deepkit author: Bun is rediscovering our decade-old ideas, agents could revive it — MarcJSchmidt · 2026-10-09