From 8c4df63db4ae062982e0ba812205758f199b0a60 Mon Sep 17 00:00:00 2001 From: mumuni-bot Date: Tue, 1 Sep 2026 21:24:06 +0000 Subject: [PATCH] docs: add critical fix for .env.clobbered-by-new-image - Root cause: Agent Zero loaded key from .env.clobbered-by-new-image - Not main .env file! - Both files must be updated when changing OpenRouter key - Added to prose contract for future reference --- agent-zero-fix-summary.prose.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/agent-zero-fix-summary.prose.md b/agent-zero-fix-summary.prose.md index 62980b2..ffe8720 100644 --- a/agent-zero-fix-summary.prose.md +++ b/agent-zero-fix-summary.prose.md @@ -95,6 +95,21 @@ sudo docker restart agent-zero **Result**: All services restarted cleanly, no more 401 errors. +### Fix 5: Update Stale `.env.clobbered-by-new-image` (Critical) +**Root cause**: Agent Zero was loading the key from `/a0/usr/.env.clobbered-by-new-image` (line 28) instead of the main `/a0/usr/.env` (line 72). The clobbered file still had the old, stale key. + +**Fix**: +```bash +KEY=$(grep "^API_KEY_OPENROUTER=" /a0/usr/.env | cut -d"=" -f2-) +sed -i "s|^API_KEY_OPENROUTER=.*|API_KEY_OPENROUTER=$KEY|" /a0/usr/.env.clobbered-by-new-image +``` + +**Lesson**: When updating Agent Zero's `.env`, check BOTH files: +- `/a0/usr/.env` (main) +- `/a0/usr/.env.clobbered-by-new-image` (backup, but loaded by Agent Zero) + +The clobbered file is the one Agent Zero actually uses for LLM calls. + --- ## Infrastructure Documentation