Pasos para restaurar Open Claw de mis backup | Friends of the Crustacean 🦞🤝 | Page 1

narrow dune Apr 28, 2026, 2:00 AM

#

Restaurar Open Claw de la ultima configuracion buena conocida

bronze bobcatBOT Apr 28, 2026, 2:02 AM

#

Sí — pero primero pásame tu versión:

openclaw --version

Mientras tanto, pasos seguros para restaurar la última config buena:

CONFIG="$(openclaw config file)"
echo "$CONFIG"

openclaw logs --follow
openclaw config validate
ls -lt "$CONFIG".last-good "$CONFIG".clobbered.* "$CONFIG".rejected.* 2>/dev/null | head

#

Si ves en logs algo como “Config auto-restored from last-known-good”, entonces openclaw.json ya fue restaurado automáticamente. No copies .clobbered.* encima: ese archivo suele ser la config rota/rechazada.

Si necesitas forzar restauración manual desde la última buena:

openclaw gateway stop

CONFIG="$(openclaw config file)"
cp -a "$CONFIG" "$CONFIG.before-manual-restore.$(date +%Y%m%d-%H%M%S)" 2>/dev/null || true
cp -a "$CONFIG.last-good" "$CONFIG"
chmod 600 "$CONFIG"

openclaw config validate
openclaw doctor
openclaw gateway start
openclaw status

#

Si estás restaurando desde un backup .tar.gz de OpenClaw:

openclaw backup verify /ruta/al/backup.tar.gz

Luego conviene extraerlo a una carpeta temporal primero, revisar el manifest.json, y copiar solo lo necesario con el gateway parado.

Docs útiles: https://docs.openclaw.ai/gateway/troubleshooting#gateway-restored-last-known-good-config y https://docs.openclaw.ai/cli/backup

narrow dune Apr 28, 2026, 2:03 AM

#

OpenClaw 2026.4.23 (a979721)

bronze bobcatBOT Apr 28, 2026, 2:03 AM

#

Perfecto, 2026.4.23 tiene soporte de last-good. Hazlo así:

CONFIG="$(openclaw config file)"
echo "$CONFIG"
ls -lh "$CONFIG" "$CONFIG.last-good" 2>/dev/null

Si existe openclaw.json.last-good, restaura:

openclaw gateway stop

CONFIG="$(openclaw config file)"
cp -a "$CONFIG" "$CONFIG.before-restore.$(date +%Y%m%d-%H%M%S)"
cp -a "$CONFIG.last-good" "$CONFIG"

#

chmod 600 "$CONFIG"

openclaw config validate
openclaw doctor
openclaw gateway start
openclaw status

Importante: no pegues aquí el contenido de openclaw.json, puede tener tokens/secrets.

Si estás restaurando desde un .tar.gz creado con openclaw backup create, primero verifica:

openclaw backup verify /ruta/a/tu-backup.tar.gz

#

Nota: openclaw backup en 2026.4.23 tiene create y verify, no un comando automático restore, así que la restauración del backup se hace copiando archivos manualmente con el gateway parado.

Docs: https://docs.openclaw.ai/gateway/troubleshooting#gateway-restored-last-known-good-config y https://docs.openclaw.ai/cli/backup

narrow dune Apr 28, 2026, 2:04 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ CONFIG="$(openclaw config file)"
echo "$CONFIG"
ls -lh "$CONFIG" "$CONFIG.last-good" 2>/dev/null
~/.openclaw/openclaw.json

bronze bobcatBOT Apr 28, 2026, 2:04 AM

#

Ese output indica que openclaw config file devolvió ~/.openclaw/openclaw.json, pero Bash no expande ~ dentro de una variable entre comillas, por eso el ls probablemente no encontró nada.

Prueba así:

CONFIG="$(openclaw config file)"
CONFIG="${CONFIG/#\~/$HOME}"
echo "$CONFIG"

ls -lh "$CONFIG" "$CONFIG.last-good" "$CONFIG".clobbered.* "$CONFIG".rejected.* 2>/dev/null || true

Si ahora aparece:

/home/alexifra/.openclaw/openclaw.json.last-good

#

restaura con:

openclaw gateway stop

cp -a "$CONFIG" "$CONFIG.before-restore.$(date +%Y%m%d-%H%M%S)"
cp -a "$CONFIG.last-good" "$CONFIG"
chmod 600 "$CONFIG"

openclaw config validate
openclaw doctor
openclaw gateway start
openclaw status

Si no aparece .last-good, dime qué sale del ls y buscamos el backup .tar.gz.

narrow dune Apr 28, 2026, 2:05 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ CONFIG="$(openclaw config file)"
CONFIG="${CONFIG/#~/$HOME}"
echo "$CONFIG"

ls -lh "$CONFIG" "$CONFIG.last-good" "$CONFIG".clobbered.* "$CONFIG".rejected.* 2>/dev/null || true
/home/alexifra/.openclaw/openclaw.json
-rw------- 1 alexifra alexifra 4.6K Apr 27 16:28 /home/alexifra/.openclaw/openclaw.json
-rw------- 1 alexifra alexifra 166 Apr 6 17:37 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-06T20-37-36-262Z
-rw------- 1 alexifra alexifra 263 Apr 6 17:50 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-06T20-50-41-887Z
-rw------- 1 alexifra alexifra 392 Apr 6 18:33 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-06T21-33-43-828Z
-rw------- 1 alexifra alexifra 413 Apr 6 19:57 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-06T22-57-07-000Z
-rw------- 1 alexifra alexifra 583 Apr 7 23:53 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-08T02-53-00-698Z
-rw------- 1 alexifra alexifra 413 Apr 7 23:55 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-08T02-55-41-267Z
-rw------- 1 alexifra alexifra 493 Apr 7 23:55 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-08T02-55-41-425Z
-rw------- 1 alexifra alexifra 971 Apr 8 00:20 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-08T03-20-45-036Z
-rw------- 1 alexifra alexifra 392 Apr 8 00:46 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-08T03-46-34-113Z
-rw------- 1 alexifra alexifra 5.1K Apr 24 20:25 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-24T23-25-52-639Z
-rw------- 1 alexifra alexifra 5.1K Apr 24 20:25 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-24T23-25-52-696Z
-rw------- 1 alexifra alexifra 5.2K Apr 24 20:38 /home/alexifra/.openclaw/openclaw.json.clobbered.2026-04-24T23-38-38-632Z
-rw------- 1 alexifra alexifra 4.6K Apr 27 16:28 /home/alexifra/.openclaw/openclaw.json.last-good

bronze bobcatBOT Apr 28, 2026, 2:06 AM

#

Bien — tienes .last-good y parece que ya coincide con el openclaw.json actual: ambos 4.6K y Apr 27 16:28. O sea, probablemente ya estás en la última config buena.

Verifícalo:

cmp -s "$CONFIG" "$CONFIG.last-good" && echo "OK: config actual = last-good" || echo "DIFERENTE"
openclaw config validate
openclaw doctor
openclaw status

Si cmp dice OK, no copies nada; ya está restaurado.

Si dice DIFERENTE, entonces sí puedes restaurar:

#

openclaw gateway stop
cp -a "$CONFIG" "$CONFIG.before-restore.$(date +%Y%m%d-%H%M%S)"
cp -a "$CONFIG.last-good" "$CONFIG"
chmod 600 "$CONFIG"
openclaw config validate
openclaw gateway start
openclaw status

Los .clobbered.* son configs rechazadas/rotas guardadas para inspección — no las restaures encima salvo que sepas exactamente qué cambio quieres recuperar.

narrow dune Apr 28, 2026, 2:08 AM

#

ahora el sistema de Open Claw se conecta con Discord al LLM, pero le escrbes, responde que lo esta buscando y no devuelve nada. Lo mejor es ir restaurando versiones anteriores, hasta encontrar una estable

bronze bobcatBOT Apr 28, 2026, 2:09 AM

#

Sí, pero lo haría metódico, no restaurando .clobbered.* a ciegas. Esos archivos son configs que OpenClaw marcó como problemáticas.

Primero guarda el estado actual:

mkdir -p ~/openclaw-backups
openclaw backup create --output ~/openclaw-backups --verify
openclaw update status
openclaw status --all

Antes de bajar versión, prueba una sesión limpia en Discord:

/new

#

y manda algo simple tipo “responde solo PONG”. Si vuelve a decir que busca y no termina, entonces mira logs mientras envías el mensaje:

openclaw logs --follow

Para probar versiones anteriores de OpenClaw:

openclaw update --tag 2026.4.22 --dry-run
openclaw update --tag 2026.4.22 --yes
openclaw gateway restart
openclaw --version
openclaw doctor
openclaw status

#

Si sigue igual, baja un paso más:

openclaw update --tag 2026.4.21 --dry-run
openclaw update --tag 2026.4.21 --yes
openclaw gateway restart
openclaw doctor
openclaw status

Cuando encuentres una versión estable, quédate ahí y comparte el error exacto de openclaw logs --follow; así vemos si era bug de versión, modelo, web search/tool-call, o sesión atascada.

Docs: https://docs.openclaw.ai/cli/update y https://docs.openclaw.ai/cli/backup

narrow dune Apr 28, 2026, 2:12 AM

#

02:11:31+00:00 warn agent/embedded {"subsystem":"agent/embedded"} {"event":"embedded_run_failover_decision","tags":["error_handling","failover","assistant","fallback_model"],"runId":"42b7412a-609c-4cf9-a9c1-35e1412e2e3b","stage":"assistant","decision":"fallback_model","failoverReason":"rate_limit","profileFailureReason":"rate_limit","provider":"google","model":"gemini-3-flash-preview","sourceProvider":"google","sourceModel":"gemini-3-flash-preview","profileId":"sha256:a94403a4f9d0","fallbackConfigured":true,"timedOut":false,"aborted":false,"status":429,"rawErrorPreview":"Google Generative AI API error (429): {\n "error": {\n "code": 429,\n "message": "Your project has exceeded its monthly spending cap. Please go to AI Studio at https://ai.studio/spend to manage your project spend cap. Learn more at https://ai.google.dev/gemini-api/docs/billing#project-spend-caps. ",\n "status": "RESOURCE_EXHAUSTED"\n }\n}","rawErrorHash":"sha256:d9e25fa16ac7","providerRuntimeFailureKind":"rate_limit"} embedded run failover decision
02:11:31+00:00 error diagnostic {"subsystem":"diagnostic"} lane task error: lane=main durationMs=19939 error="FailoverError: ⚠️ API rate limit reached. Please try again later."
02:11:31+00:00 error diagnostic {"subsystem":"diagnostic"} lane task error: lane=session:agent:main:discord:direct:1416148785159213106 durationMs=19941 error="FailoverError: ⚠️ API rate limit reached. Please try again later."
02:11:31+00:00 warn model-fallback/decision {"subsystem":"model-fallback/decision"} {"event":"model_fallback_decision","tags":["error_handling","model_fallback","candidate_failed"],"runId":"42b7412a-609c-4cf9-a9c1-35e1412e2e3b","decision":"candidate_failed","requestedProvider":"google","requestedModel":"gemini-3-flash-preview","candidateProvider":"google","candidateModel":"gemini-3-flash-preview","attempt":1,"total":3,"reason":"rate_limit","status":429,"errorPreview":"Google Generative AI API error (429): {\n "error": {\n "code": 429,\n "message": "Your project has exceeded its monthly spending cap. Please go to AI Studio at https://ai.studio/spend to manage your project spend cap. Learn more at https://ai.google.dev/gemini-api/docs/billing#project-spend-caps. ",\n "status": "RESOURCE_EXHAUSTED"\n }\n}","errorHash":"sha256:d9e25fa16ac7","nextCandidateProvider":"openrouter","nextCandidateModel":"moonshotai/kimi-k2.6","isPrimary":true,"requestedModelMatched":true,"fallbackConfigured":true} model fallback decision
02:11:51+00:00 warn model-fallback/decision {"subsystem":"model-fallback/decision"} {"event":"model_fallback_decision","tags":["error_handling","model_fallback","candidate_succeeded"],"runId":"42b7412a-609c-4cf9-a9c1-35e1412e2e3b","decision":"candidate_succeeded","requestedProvider":"google","requestedModel":"gemini-3-flash-preview","candidateProvider":"openrouter","candidateModel":"moonshotai/kimi-k2.6","attempt":2,"total":3,"isPrimary":false,"requestedModelMatched":false,"fallbackConfigured":true,"previousAttempts":[{"provider":"google","model":"gemini-3-flash-preview","reason":"rate_limit","status":429,"errorPreview":"Google Generative AI API error (429): {\n "error": {\n "code": 429,\n "message": "Your project has exceeded its monthly spending cap. Please go to AI Studio at https://ai.studio/spend to manage your project spend cap. Learn more at https://ai.google.dev/gemini-api/docs/billing#project-spend-caps. ",\n "status": "RESOURCE_EXHAUSTED"\n }\n}","errorHash":"sha256:d9e25fa16ac7"}]} model fallback decision

bronze bobcatBOT Apr 28, 2026, 2:13 AM

#

Esto ya no parece problema de versión/config. El log es bastante claro:

Google/Gemini está fallando por límite de gasto mensual:

Your project has exceeded its monthly spending cap
status: RESOURCE_EXHAUSTED / 429

OpenClaw intenta fallback y el fallback sí tuvo éxito a las 02:11:51. Así que yo no bajaría versiones todavía; primero quita Google como modelo primario o sube el spending cap en AI Studio.

Haz esto:

openclaw models status
openclaw models fallbacks list

Luego elige un modelo no-Google de los que ya tengas configurados:

#

openclaw models list
openclaw models set <provider/model>
openclaw gateway restart

Después en Discord manda:

/new

y prueba:

responde solo PONG

#

Si quieres arreglar Google en vez de cambiar modelo: entra en AI Studio/Billing y sube o resetea el monthly spending cap del proyecto Gemini.

Si después de cambiar a un modelo no-Google sigue “buscando” y no devuelve mensaje, entonces el siguiente paso es mirar el log después de candidate_succeeded, porque ahí ya sería un problema de entrega Discord/sesión, no de LLM.

narrow dune Apr 28, 2026, 2:14 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ openclaw models status
openclaw models fallbacks list

🦞 OpenClaw 2026.4.23 (a979721) — If it's repetitive, I'll automate it; if it's hard, I'll bring jokes and a rollback plan.

Config : ~/.openclaw/openclaw.json
Agent dir : ~/.openclaw/agents/main/agent
Default : google/gemini-3.1-flash-lite-preview
Fallbacks (1) : openrouter/moonshotai/kimi-k2.6
Image model : -
Image fallbacks (0): -
Aliases (3) : gemini-flash-lite -> google/gemini-3.1-flash-lite-preview, gemini-flash -> google/gemini-3-flash-preview, OpenRouter -> openrouter/auto
Configured models (6): openrouter/free, google/gemini-3.1-flash-lite-preview, google/gemini-3-flash-preview, openrouter/auto, openrouter/@preset/asistente-diario, openrouter/moonshotai/kimi-k2.6

Auth overview
Auth store : ~/.openclaw/agents/main/agent/auth-profiles.json
Shell env : off
Providers w/ OAuth/tokens (0): -

brave effective=env:BSAwl7-5...x7NCmChU | env=BSAwl7-5...x7NCmChU | source=env: BRAVE_API_KEY
google effective=profiles:~/.openclaw/agents/main/agent/auth-profiles.json | profiles=1 (oauth=0, token=0, api_key=1) | google:default=AIzaSyCx...1ghdoEJY | env=AIzaSyCx...1ghdoEJY | source=env: GEMINI_API_KEY
openai effective=profiles:~/.openclaw/agents/main/agent/auth-profiles.json | profiles=1 (oauth=0, token=0, api_key=1) | openai:default=sk-proj-...fRb8ZXEA | env=sk-proj-...pSn135wA | source=env: OPENAI_API_KEY
openrouter effective=profiles:~/.openclaw/agents/main/agent/auth-profiles.json | profiles=1 (oauth=0, token=0, api_key=1) | openrouter:default=sk-or-v1...23d8c66e | env=sk-or-v1...23d8c66e | source=env: OPENROUTER_API_KEY
perplexity effective=env:sk-or-v1...23d8c66e | env=sk-or-v1...23d8c66e | source=env: OPENROUTER_API_KEY

OAuth/token status

none

🦞 OpenClaw 2026.4.23 (a979721) — One CLI to rule them all, and one more restart because you changed the port.

Fallbacks (1):

openrouter/moonshotai/kimi-k2.6

bronze bobcatBOT Apr 28, 2026, 2:14 AM

#

Ahí está el problema: tu default sigue siendo Google:

Default: google/gemini-3.1-flash-lite-preview

y tu Google está bloqueado por spending cap. Cambia el default a OpenRouter:

openclaw models set openrouter/moonshotai/kimi-k2.6
openclaw models status
openclaw gateway restart

Luego en Discord prueba con sesión limpia:

#

/new

y después:

responde solo PONG

Si quieres usar tu preset diario como default, también podrías probar:

openclaw models set openrouter/@preset/asistente-diario
openclaw gateway restart

#

Yo empezaría con openrouter/moonshotai/kimi-k2.6 porque ya vimos en logs que ese fallback sí llegó a funcionar.

narrow dune Apr 28, 2026, 2:18 AM

#

verifiquemos los tar.gz de bacup que tenemos en el sistema

bronze bobcatBOT Apr 28, 2026, 2:18 AM

#

Sí. Para localizarlos sin tocar nada:

find "$HOME" -type f \( -name "*openclaw*backup*.tar.gz" -o -name "*.tar.gz" \) \
  -printf '%TY-%Tm-%Td %TH:%TM  %10s  %p\n' 2>/dev/null | sort -r | head -50

Si salen muchos .tar.gz, filtra solo backups de OpenClaw:

find "$HOME" -type f -name "*.tar.gz" -print 2>/dev/null | while read -r f; do
  if tar -tzf "$f" 2>/dev/null | grep -q 'manifest.json'; then
    echo "$f"
  fi
done

#

Luego verifica cada candidato:

openclaw backup verify "/ruta/al/backup.tar.gz"

Si quieres hacerlo en lote:

find "$HOME" -type f -name "*.tar.gz" -print 2>/dev/null | while read -r f; do
  echo "== $f =="
  openclaw backup verify "$f" >/tmp/openclaw-verify.out 2>&1 && echo "OK" || cat /tmp/openclaw-verify.out
done

Pega aquí solo las rutas/nombres y fechas, no el contenido del backup.

narrow dune Apr 28, 2026, 2:21 AM

#

/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T17-42-06.456Z-openclaw-backup.tar.gz
2026-04-20 04:00 2844376 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/workspace_full.tar.gz
2026-04-20 04:00 1719 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/config_essentials.tar.gz
2026-04-19 04:00 2843608 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-19/workspace_full.tar.gz
2026-04-19 04:00 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-19/config_essentials.tar.gz
2026-04-15 04:00 2842975 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-15/workspace_full.tar.gz
2026-04-15 04:00 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-15/config_essentials.tar.gz
2026-04-14 04:00 2842927 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-14/workspace_full.tar.gz
2026-04-14 04:00 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-14/config_essentials.tar.gz
2026-04-13 04:00 2842257 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-13/workspace_full.tar.gz
2026-04-13 04:00 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-13/config_essentials.tar.gz
2026-04-12 20:29 2966515508 /home/alexifra/.openclaw/backups/Backup-Full-2026-04-12-Validado/system_config.tar.gz
2026-04-12 20:29 2842244 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-12/workspace_full.tar.gz
2026-04-12 20:29 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-12/config_essentials.tar.gz
2026-04-12 20:27 2842244 /home/alexifra/.openclaw/backups/Backup-Full-2026-04-12-Validado/workspace.tar.gz
2026-04-10 07:25 1069838390 /home/alexifra/.openclaw/backups/Backup-Full-2026-04-10-last-email_draft.txt/system_config.tar.gz
2026-04-10 07:25 2841684 /home/alexifra/.openclaw/backups/Backup-Full-2026-04-10-last-email_draft.txt/workspace.tar.gz
2026-04-09 10:21 639831459 /home/alexifra/.openclaw/backups/Backup-Diario-2026-04-09-1021/system_config.tar.gz
2026-04-09 10:21 2840626 /home/alexifra/.openclaw/backups/Backup-Diario-2026-04-09-1021/workspace.tar.gz
2026-04-09 10:21 4862 /home/alexifra/.openclaw/backups/Backup-Diario-2026-04-09-1021/scripts.tar.gz
2026-04-08 16:16 209740519 /home/alexifra/.openclaw/backups/Backup-Gemini-3.1-Flash-Lite-2026-04-08-1616/system_config.tar.gz
2026-04-08 16:16 2837099 /home/alexifra/.openclaw/backups/Backup-Gemini-3.1-Flash-Lite-2026-04-08-1616/workspace.tar.gz
2026-04-08 16:16 2276 /home/alexifra/.openclaw/backups/Backup-Gemini-3.1-Flash-Lite-2026-04-08-1616/scripts.tar.gz
2026-04-08 03:36 131560 /home/alexifra/.openclaw/backups/Backup-Autoplus-2026-04-08/workspace.tar.gz
2026-04-08 03:36 1781 /home/alexifra/.openclaw/backups/Backup-Autoplus-2026-04-08/scripts_usuario.tar.gz
2026-04-08 02:15 131560 /home/alexifra/.openclaw/backups/autenticacion-Google-Workspace-OK-2026-04-08-0215/workspace.tar.gz
2026-04-08 02:15 910 /home/alexifra/.openclaw/backups/autenticacion-Google-Workspace-OK-2026-04-08-0215/user_scripts.tar.gz
2026-04-06 19:48 50069504 /home/alexifra/.openclaw/backups/pre-restore-completo-2026-04-06-1948.tar.gz
2026-04-06 19:30 133505 /home/alexifra/.openclaw/backups/pre-restore-hoy.tar.gz
2026-04-05 10:39 49807360 /home/alexifra/.openclaw/backups/system-backup-2026-04-05.tar.gz
2026-03-31 13:08 2250 /home/alexifra/.openclaw/backups/state-2026-03-31_13-10-google-drive-autorizacion-ok.tar.gz
2026-03-26 00:13 209192 /home/alexifra/.openclaw/snapshots/workspace-2026-03-26_00-13-40-stability-gog-telegram.tar.gz
2026-03-26 00:13 3790 /home/alexifra/.openclaw/backups/state-2026-03-26_00-13-40-gog-telegram.tar.gz

bronze bobcatBOT Apr 28, 2026, 2:22 AM

#

Tienes varios. El mejor candidato primero es este, porque parece backup oficial de OpenClaw:

/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T17-42-06.456Z-openclaw-backup.tar.gz

Verifícalo así:

openclaw backup verify "/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T17-42-06.456Z-openclaw-backup.tar.gz"

Para los otros .tar.gz hechos a mano, usa verificación de integridad:

for f in \

#

  /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/config_essentials.tar.gz \
  /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-19/config_essentials.tar.gz \
  /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-15/config_essentials.tar.gz \
  /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-14/config_essentials.tar.gz \
  /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-13/config_essentials.tar.gz
do
  echo "== $f =="
  tar -tzf "$f" >/dev/null && echo "OK" || echo "ERROR"
done

Y para ver qué contienen sin extraer encima de nada:

tar -tzf /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/config_essentials.tar.gz

#

Mi recomendación: no restaures system_config.tar.gz todavía; son enormes y pueden pisar muchas cosas. Primero revisemos/restauremos solo config_essentials.tar.gz o el backup oficial del 20 de abril.

narrow dune Apr 28, 2026, 2:24 AM

#

pego nuevamente la lista completa ny dime cuales son los mas recientes

bronze bobcatBOT Apr 28, 2026, 2:25 AM

#

Claro. Pega la lista completa y te la ordeno.

Por lo que ya mandaste, los más recientes son:

2026-04-20 17:42 — backup oficial OpenClaw
/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T17-42-06.456Z-openclaw-backup.tar.gz
2026-04-20 04:00 — config essentials
/home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/config_essentials.tar.gz
2026-04-20 04:00 — workspace full
/home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/workspace_full.tar.gz
2026-04-19 04:00 — config essentials
/home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-19/config_essentials.tar.gz
2026-04-19 04:00 — workspace full

#

/home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-19/workspace_full.tar.gz

Para restaurar config, los que más importan son los config_essentials.tar.gz y el backup oficial 2026-04-20T17-42...openclaw-backup.tar.gz. Los workspace_full son memoria/workspace, no tanto conexión/modelos.

narrow dune Apr 28, 2026, 2:26 AM

#

2026-04-20 15:24 3964867423 /home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-22-13.136Z-openclaw-backup.tar.gz
2026-04-20 15:08 3964867439 /home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-06-34.084Z-openclaw-backup.tar.gz
2026-04-20 14:44 3964867343 /home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T17-42-06.456Z-openclaw-backup.tar.gz
2026-04-20 04:00 2844376 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/workspace_full.tar.gz
2026-04-20 04:00 1719 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/config_essentials.tar.gz
2026-04-19 04:00 2843608 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-19/workspace_full.tar.gz
2026-04-19 04:00 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-19/config_essentials.tar.gz
2026-04-15 04:00 2842975 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-15/workspace_full.tar.gz
2026-04-15 04:00 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-15/config_essentials.tar.gz
2026-04-14 04:00 2842927 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-14/workspace_full.tar.gz
2026-04-14 04:00 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-14/config_essentials.tar.gz
2026-04-13 04:00 2842257 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-13/workspace_full.tar.gz
2026-04-13 04:00 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-13/config_essentials.tar.gz
2026-04-12 20:29 2966515508 /home/alexifra/.openclaw/backups/Backup-Full-2026-04-12-Validado/system_config.tar.gz
2026-04-12 20:29 2842244 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-12/workspace_full.tar.gz
2026-04-12 20:29 1720 /home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-12/config_essentials.tar.gz
2026-04-12 20:27 2842244 /home/alexifra/.openclaw/backups/Backup-Full-2026-04-12-Validado/workspace.tar.gz
2026-04-10 07:25 1069838390 /home/alexifra/.openclaw/backups/Backup-Full-2026-04-10-last-email_draft.txt/system_config.tar.gz
2026-04-10 07:25 2841684 /home/alexifra/.openclaw/backups/Backup-Full-2026-04-10-last-email_draft.txt/workspace.tar.gz
2026-04-09 10:21 639831459 /home/alexifra/.openclaw/backups/Backup-Diario-2026-04-09-1021/system_config.tar.gz
2026-04-09 10:21 2840626 /home/alexifra/.openclaw/backups/Backup-Diario-2026-04-09-1021/workspace.tar.gz
2026-04-09 10:21 4862 /home/alexifra/.openclaw/backups/Backup-Diario-2026-04-09-1021/scripts.tar.gz
2026-04-08 16:16 209740519 /home/alexifra/.openclaw/backups/Backup-Gemini-3.1-Flash-Lite-2026-04-08-1616/system_config.tar.gz
2026-04-08 16:16 2837099 /home/alexifra/.openclaw/backups/Backup-Gemini-3.1-Flash-Lite-2026-04-08-1616/workspace.tar.gz
2026-04-08 16:16 2276 /home/alexifra/.openclaw/backups/Backup-Gemini-3.1-Flash-Lite-2026-04-08-1616/scripts.tar.gz
2026-04-08 03:36 131560 /home/alexifra/.openclaw/backups/Backup-Autoplus-2026-04-08/workspace.tar.gz
2026-04-08 03:36 1781 /home/alexifra/.openclaw/backups/Backup-Autoplus-2026-04-08/scripts_usuario.tar.gz
2026-04-08 02:15 131560 /home/alexifra/.openclaw/backups/autenticacion-Google-Workspace-OK-2026-04-08-0215/workspace.tar.gz
2026-04-08 02:15 910 /home/alexifra/.openclaw/backups/autenticacion-Google-Workspace-OK-2026-04-08-0215/user_scripts.tar.gz
2026-04-06 19:48 50069504 /home/alexifra/.openclaw/backups/pre-restore-completo-2026-04-06-1948.tar.gz
2026-04-06 19:30 133505 /home/alexifra/.openclaw/backups/pre-restore-hoy.tar.gz
2026-04-05 10:39 49807360 /home/alexifra/.openclaw/backups/system-backup-2026-04-05.tar.gz
2026-03-31 13:08 2250 /home/alexifra/.openclaw/backups/state-2026-03-31_13-10-google-drive-autorizacion-ok.tar.gz
2026-03-26 00:13 209192 /home/alexifra/.openclaw/snapshots/workspace-2026-03-26_00-13-40-stability-gog-telegram.tar.gz
2026-03-26 00:13

bronze bobcatBOT Apr 28, 2026, 2:26 AM

#

Los más recientes son estos, en orden:

2026-04-20 15:24 — más reciente
/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-22-13.136Z-openclaw-backup.tar.gz
2026-04-20 15:08
/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-06-34.084Z-openclaw-backup.tar.gz
2026-04-20 14:44
/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T17-42-06.456Z-openclaw-backup.tar.gz
2026-04-20 04:00 — backup manual de config/workspace
/home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/config_essentials.tar.gz
/home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-20/workspace_full.tar.gz
2026-04-19 04:00
/home/alexifra/.openclaw/backups/Backup-Seguro-2026-04-19/config_essentials.tar.gz

#

Yo verificaría primero los 3 backups oficiales de GoogleDrive, empezando por el más reciente:

for f in \
"/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-22-13.136Z-openclaw-backup.tar.gz" \
"/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-06-34.084Z-openclaw-backup.tar.gz" \
"/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T17-42-06.456Z-openclaw-backup.tar.gz"
do
  echo "== $f =="
  openclaw backup verify "$f"
done

Si esos verifican bien, el candidato principal es el 2026-04-20T18-22-13.136Z.

narrow dune Apr 28, 2026, 2:27 AM

#

restauremos el numero 1 y vamos probando, si esta ok lo dejamos ahi. Si no funciona probamos el numero 2. Y asi sucesivamente

bronze bobcatBOT Apr 28, 2026, 2:28 AM

#

Sí. Hagámoslo seguro y reversible con el backup #1:

ARCHIVE="/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-22-13.136Z-openclaw-backup.tar.gz"

openclaw backup verify "$ARCHIVE"

Si dice OK, crea un backup del estado actual antes de tocar nada:

mkdir -p ~/openclaw-restore-safety
openclaw backup create --output ~/openclaw-restore-safety --verify

Ahora restaura el backup #1 completo:

#

openclaw gateway stop

TS="$(date +%Y%m%d-%H%M%S)"
mv ~/.openclaw ~/.openclaw.before-restore-$TS

TMP="$(mktemp -d)"
tar -xzf "$ARCHIVE" -C "$TMP"

# Copia el estado .openclaw desde el backup oficial
rsync -a "$TMP"/*/payload/posix/home/alexifra/.openclaw/ ~/.openclaw/

chmod 700 ~/.openclaw
chmod 600 ~/.openclaw/openclaw.json 2>/dev/null || true

openclaw config validate

#

openclaw doctor
openclaw gateway start
openclaw status

Luego prueba en Discord:

/new

y:

responde solo PONG

#

Si no funciona, volvemos atrás o probamos el #2. Para volver al estado anterior:

openclaw gateway stop
mv ~/.openclaw ~/.openclaw.failed-restore-$TS
mv ~/.openclaw.before-restore-$TS ~/.openclaw
openclaw gateway start

Ojo: si el backup #1 también usa Google/Gemini como default, el problema del spending cap seguirá. En ese caso la restauración no lo arregla; habrá que dejar OpenRouter como modelo default.

narrow dune Apr 28, 2026, 2:31 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ ARCHIVE="/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-22-13.136Z-openclaw-backup.tar.gz"

openclaw backup verify "$ARCHIVE"

🦞 OpenClaw 2026.4.23 (a979721) — Give me a workspace and I'll give you fewer tabs, fewer toggles, and more oxygen.

Backup archive OK: /home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-22-13.136Z-openclaw-backup.tar.gz
Archive root: 2026-04-20T18-22-13.136Z-openclaw-backup
Created at: 2026-04-20T18:22:13.136Z
Runtime version: 2026.4.15
Assets verified: 1
Archive entries scanned: 5821

bronze bobcatBOT Apr 28, 2026, 2:31 AM

#

Perfecto: el backup #1 está sano. Nota importante: fue creado con OpenClaw 2026.4.15, y tu runtime actual es 2026.4.23. Aun así podemos restaurar el estado; después vemos si también conviene bajar versión.

Antes de mover ~/.openclaw, haz backup actual:

mkdir -p ~/openclaw-restore-safety
openclaw backup create --output ~/openclaw-restore-safety --verify

Luego restaura #1:

ARCHIVE="/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-22-13.136Z-openclaw-backup.tar.gz"

openclaw gateway stop

#

TS="$(date +%Y%m%d-%H%M%S)"
mv ~/.openclaw ~/.openclaw.before-restore-$TS

TMP="$(mktemp -d)"
tar -xzf "$ARCHIVE" -C "$TMP"

rsync -a "$TMP"/*/payload/posix/home/alexifra/.openclaw/ ~/.openclaw/

chmod 700 ~/.openclaw
chmod 600 ~/.openclaw/openclaw.json 2>/dev/null || true

openclaw config validate
openclaw doctor
openclaw gateway start
openclaw status

#

Si rsync no está instalado, usa:

cp -a "$TMP"/*/payload/posix/home/alexifra/.openclaw ~/.openclaw

Después prueba Discord con:

/new

y:

responde solo PONG

narrow dune Apr 28, 2026, 2:49 AM

#

voy a ir pegando por parte el resultado

bronze bobcatBOT Apr 28, 2026, 2:49 AM

#

Perfecto, pega las partes.

No pegues tokens completos, claves API ni contenido de openclaw.json entero. Si aparece algo tipo sk-..., AIza..., DISCORD_TOKEN, etc., redáctalo.

Lo que más me interesa ver tras la restauración:

openclaw config validate
openclaw doctor
openclaw status
openclaw models status

y si falla al probar Discord, las últimas líneas de:

#

openclaw logs --follow

narrow dune Apr 28, 2026, 2:50 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ ARCHIVE="/home/alexifra/GoogleDrive/OpenClawBackups/2026-04-20T18-22-13.136Z-openclaw-backup.tar.gz"

openclaw gateway stop

🦞 OpenClaw 2026.4.23 (a979721) — I speak fluent bash, mild sarcasm, and aggressive tab-completion energy.

Stopped systemd service: openclaw-gateway.service
alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ TS="$(date +%Y%m%d-%H%M%S)"
mv ~/.openclaw ~/.openclaw.before-restore-$TS

TMP="$(mktemp -d)"
tar -xzf "$ARCHIVE" -C "$TMP"

rsync -a "$TMP"/*/payload/posix/home/alexifra/.openclaw/ ~/.openclaw/

chmod 700 ~/.openclaw
chmod 600 ~/.openclaw/openclaw.json 2>/dev/null || true

openclaw config validate
openclaw doctor
openclaw gateway start
openclaw status

🦞 OpenClaw 2026.4.23 (a979721) — Welcome to the command line: where dreams compile and confidence segfaults.

Config valid: ~/.openclaw/openclaw.json

🦞 OpenClaw 2026.4.23 (a979721) — I've read more man pages than any human should—so you don't have to.

bronze bobcatBOT Apr 28, 2026, 2:50 AM

#

Bien: la config restaurada valida correctamente ✅

Parece que openclaw doctor siguió corriendo o el paste se cortó justo después. Espera a que termine y pega la siguiente parte desde doctor, gateway start y status.

Si se quedó colgado más de 2–3 minutos, abre otra terminal y mira:

openclaw gateway status
openclaw logs --tail 80

Después de que arranque, revisa el modelo:

openclaw models status

#

Si el backup restauró Google como default, cámbialo otra vez a OpenRouter antes de probar Discord:

openclaw models set openrouter/moonshotai/kimi-k2.6
openclaw gateway restart

narrow dune Apr 28, 2026, 2:51 AM

#

┌ OpenClaw doctor
│
◇ Update ──────────────────────────────────────────────────────────────────────────────────╮
│ │
│ This install is not a git checkout. │
│ Run openclaw update to update via your package manager (npm/pnpm), then rerun doctor. │
│ │
├───────────────────────────────────────────────────────────────────────────────────────────╯
│
◇ Doctor warnings ────────────────────────────────────────────────────────────────────────╮
│ │
│ - channels.discord.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is │
│ empty — all group messages will be silently dropped. Add sender IDs to │
│ channels.discord.groupAllowFrom or channels.discord.allowFrom, or set groupPolicy to │
│ "open". │
│ │
├──────────────────────────────────────────────────────────────────────────────────────────╯
│
◇ Archive 1 orphan transcript file in ~/.openclaw/agents/main/sessions? This only renames them to *.deleted.<timestamp>.
│ Yes
│
◇ State integrity ─────────────────────────────────────────────────────────────────────────╮
│ │
│ - 1/5 recent sessions are missing transcripts. │
│ Verify sessions in store: openclaw sessions --store │
│ "/home/alexifra/.openclaw/agents/main/sessions/sessions.json" │
│ Preview cleanup impact: openclaw sessions cleanup --store │
│ "/home/alexifra/.openclaw/agents/main/sessions/sessions.json" --dry-run │
│ Prune missing entries: openclaw sessions cleanup --store │
│ "/home/alexifra/.openclaw/agents/main/sessions/sessions.json" --enforce --fix-missing │
│ - Found 1 orphan transcript file in ~/.openclaw/agents/main/sessions. │
│ These .jsonl files are no longer referenced by sessions.json, so they are not part of │
│ any active session history. │
│ Doctor can archive them safely by renaming each file to *.deleted.<timestamp>. │
│ Examples: e66a0a9e-3268-4bc4-a83b-9e417947d75f.jsonl │
│ │
├───────────────────────────────────────────────────────────────────────────────────────────╯
│
◇ Doctor changes ──────────────────────────────────────────────────────────────────────╮
│ │
│ - Archived 1 orphan transcript file in ~/.openclaw/agents/main/sessions as .deleted │
│ timestamped backups. │
│ │
├───────────────────────────────────────────────────────────────────────────────────────╯
│
◇ Security ─────────────────────────────────╮
│ │
│ - No channel security warnings detected. │
│ - Run: openclaw security audit --deep │
│ │
├────────────────────────────────────────────╯
│
◇ Skills status ────────────╮
│ │
│ Eligible: 19 │
│ Missing requirements: 36 │
│ Blocked by allowlist: 0 │
│ │

bronze bobcatBOT Apr 28, 2026, 2:51 AM

#

Bien, doctor no muestra nada fatal. Pero sí aparece una causa muy probable para Discord:

channels.discord.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty
— all group messages will be silently dropped

Como estás probando desde Discord en servidor/thread, eso puede hacer que no responda.

Para permitir mensajes de grupos/servidor Discord:

openclaw config set channels.discord.groupPolicy open
openclaw config validate
openclaw gateway start
openclaw status

#

Luego prueba en Discord:

/new

y después:

responde solo PONG

Si prefieres mantener allowlist en vez de open, hay que agregar IDs a channels.discord.groupAllowFrom o channels.discord.allowFrom; pero para probar rápido, groupPolicy open es lo más simple.

Después revisa también el modelo:

#

openclaw models status

Si sigue en Google/Gemini, cámbialo:

openclaw models set openrouter/moonshotai/kimi-k2.6
openclaw gateway restart

narrow dune Apr 28, 2026, 2:51 AM

#

◇ Plugins ──────╮
│ │
│ Loaded: 50 │
│ Imported: 1 │
│ Disabled: 53 │
│ Errors: 0 │
│ │
├────────────────╯
│
◇
│
◇ Gateway ──────────────╮
│ │
│ Gateway not running. │
│ │
├────────────────────────╯
│
◇ Gateway connection ─────────────────────────────╮
│ │
│ Gateway target: ws://127.0.0.1:18789 │
│ Source: local loopback │
│ Config: /home/alexifra/.openclaw/openclaw.json │
│ Bind: loopback │
│ │
├──────────────────────────────────────────────────╯
│
◇ Gateway ───────────────────────────────────────────────────────────────╮
│ │
│ Runtime: stopped (state inactive, sub dead, last exit 0, reason 1) │
│ Service is loaded but not running (likely exited immediately). │
│ File logs: /tmp/openclaw/openclaw-2026-04-27.log │
│ Logs: journalctl --user -u openclaw-gateway.service -n 200 --no-pager │
│ Restart attempts: /home/alexifra/.openclaw/logs/gateway-restart.log │

bronze bobcatBOT Apr 28, 2026, 2:52 AM

#

Eso puede ser normal: doctor lo vio parado porque acabábamos de hacer openclaw gateway stop. Ahora toca arrancarlo y ver si se queda vivo.

Ejecuta:

openclaw config set channels.discord.groupPolicy open
openclaw models set openrouter/moonshotai/kimi-k2.6

openclaw gateway start
sleep 5
openclaw gateway status
openclaw status

Si dice otra vez “service loaded but not running / exited immediately”, pega estas salidas:

#

journalctl --user -u openclaw-gateway.service -n 200 --no-pager
tail -n 200 ~/.openclaw/logs/gateway-restart.log
tail -n 200 "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)"

No pegues tokens/API keys si aparecen.

narrow dune Apr 28, 2026, 2:52 AM

#

◇ Start gateway service now?
│ Yes
Restarted systemd service: openclaw-gateway.service
Run "openclaw doctor --fix" to apply changes.
│
└ Doctor complete.

🦞 OpenClaw 2026.4.23 (a979721) — Your AI assistant, now without the $3,499 headset.

Restarted systemd service: openclaw-gateway.service

🦞 OpenClaw 2026.4.23 (a979721) — Making 'I'll automate that later' happen now.

│
◇
│
◇
OpenClaw status

Overview
┌──────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item │ Value │
├──────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ OS │ linux 6.6.87.2-microsoft-standard-WSL2 (x64) · node 22.22.1 │
│ Dashboard │ http://127.0.0.1:18789/ │
│ Tailscale │ off │
│ Channel │ stable (default) │
│ Update │ available · pnpm · npm update 2026.4.26 │
│ Gateway │ local · ws://127.0.0.1:18789 (local loopback) · unreachable (connect ECONNREFUSED 127.0.0.1:18789) │
│ Gateway service │ systemd installed · enabled · running (pid 6563, state active) │
│ Node service │ systemd not installed │
│ Agents │ 1 · no bootstrap files · sessions 11 · default main active 7d ago │
│ Memory │ 15 files · 36 chunks · sources memory · plugin memory-core · vector ready · fts ready · cache on (38) │
│ Plugin compatibility │ none │
│ Probes │ skipped (use --deep) │
│ Events │ none │
│ Tasks │ 0 active · 0 queued · 0 running · 3 issues · audit 7 warn · 7 tracked │
│ Heartbeat │ 30m (main) │
│ Sessions │ 11 active · default gemini-3.1-flash-lite-preview (200k ctx) · ~/.openclaw/agents/main/sessions/sessions.json │
└──────────────────────┴───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

bronze bobcatBOT Apr 28, 2026, 2:52 AM

#

Buen avance: el servicio systemd está “running”, pero el Gateway todavía sale unreachable / ECONNREFUSED. Puede estar arrancando lento o fallando dentro del proceso. Además el modelo volvió a Gemini.

Haz esto en orden:

openclaw models set openrouter/moonshotai/kimi-k2.6
openclaw config set channels.discord.groupPolicy open
openclaw gateway restart

sleep 10
openclaw gateway status
openclaw status --deep

Si sigue ECONNREFUSED, necesitamos logs:

#

journalctl --user -u openclaw-gateway.service -n 120 --no-pager
tail -n 120 ~/.openclaw/logs/gateway-restart.log
tail -n 160 "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)"

El dato clave ahora: systemd está vivo pero el puerto 18789 no escucha, así que no sigas restaurando backups todavía; primero veamos por qué el gateway no abrió el puerto.

narrow dune Apr 28, 2026, 2:52 AM

#

Security audit
Summary: 0 critical · 6 warn · 1 info
WARN Reverse proxy headers are not trusted
gateway.bind is loopback and gateway.trustedProxies is empty. If you expose the Control UI through a reverse proxy, configure trusted proxies so local-client c…
Fix: Set gateway.trustedProxies to your proxy IPs or keep the Control UI local-only.
WARN Exec security=full is configured
Full exec trust is enabled for: main.
Fix: Prefer tools.exec.security="allowlist" with ask prompts, and reserve "full" for tightly scoped break-glass agents only.
WARN Some configured models are below recommended tiers
Smaller/older models are generally more susceptible to prompt injection and tool misuse. - openai/gpt-4.1-mini (Below GPT-5 family) @ agents.defaults.model.fal…
Fix: Use the latest, top-tier model for any bot with tools or untrusted inboxes. Avoid Haiku tiers; prefer GPT-5+ and Claude 4.5+.
WARN Potential multi-user setup detected (personal-assistant model warning)
Heuristic signals indicate this gateway may be reachable by multiple users: - channels.discord.groupPolicy="allowlist" with configured group targets Runtime/pr…
Fix: If users may be mutually untrusted, split trust boundaries (separate gateways + credentials, ideally separate OS users/hosts). If you intentionally run shared-user access, set agents.defaults.sandbox.mode="all", keep tools.fs.workspaceOnly=true, deny runtime/fs/web tools unless required, and keep personal/private identities + credentials off that runtime.
WARN plugins.allow contains entries with no matching installed plugin
The following plugins.allow entries do not correspond to any installed plugin: google, openrouter, openai, memory-core, perplexity. Phantom entries could be ex…
Fix: Remove unused entries from plugins.allow, or verify the expected plugins are installed.
WARN Plugin installs include unpinned npm specs
Unpinned plugin install records: - camofox-browser (@askjo/camofox-browser)
Fix: Pin install specs to exact versions (for example, @scope/pkg@1.2.3) for higher supply-chain stability.
Full report: openclaw security audit
Deep probe: openclaw security audit --deep

bronze bobcatBOT Apr 28, 2026, 2:52 AM

#

Ese audit no muestra nada que explique el ECONNREFUSED. Son warnings de seguridad/config, pero no son el bloqueo principal.

Ahora necesitamos confirmar si el gateway realmente levantó el puerto. Corre esto:

openclaw gateway status
openclaw status --deep

Si sigue unreachable, pega logs:

journalctl --user -u openclaw-gateway.service -n 120 --no-pager
tail -n 120 ~/.openclaw/logs/gateway-restart.log
tail -n 160 "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)"

#

También cambia ya el default fuera de Gemini:

openclaw models set openrouter/moonshotai/kimi-k2.6
openclaw models status

Una vez el gateway esté reachable, probamos Discord.

narrow dune Apr 28, 2026, 2:53 AM

#

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Discord │ ON │ OK │ token config (MTQ4…ODoE · len 72) · accounts 1/1 │
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

Sessions
┌─────────────────────────────────────────────────────────────────────┬────────┬─────────┬───────────────────────────────┬─────────────────────────────────┐
│ Key │ Kind │ Age │ Model │ Tokens │
├─────────────────────────────────────────────────────────────────────┼────────┼─────────┼───────────────────────────────┼─────────────────────────────────┤
│ agent:main:discord:direct:14161… │ direct │ 7d ago │ gpt-4.1-mini │ 12k/200k (6%) · 🗄️ 97% cached │
│ agent:main:main │ direct │ 7d ago │ gpt-4.1-mini │ 24k/1049k (2%) │
│ agent:main:cron:e1bbd455-4c44-4… │ direct │ 8d ago │ gpt-4.1-mini │ 6.7k/1048k (1%) │
│ agent:main:cron:e1bbd455-4c44-4… │ direct │ 8d ago │ gpt-4.1-mini │ 6.7k/1048k (1%) │
│ agent:main:cron:9079932c-034f-4… │ direct │ 8d ago │ gpt-4.1-mini │ 7.0k/1048k (1%) │
│ agent:main:cron:e1bbd455-4c44-4… │ direct │ 8d ago │ gpt-4.1-mini │ 6.7k/1048k (1%) · 🗄️ 21% cached │
│ agent:main:discord:channel:1482… │ group │ 9d ago │ gemini-3.1-flash-lite-preview │ 136k/1049k (13%) │
│ agent:main:subagent:6e75854b-45… │ direct │ 20d ago │ gemini-3-flash-preview │ 36k/1049k (3%) · 🗄️ 80% cached │
│ agent:main:discord:channel:1416… │ group │ 25d ago │ gemini-3.1-flash-lite-preview │ unknown/200k (?%) │
│ agent:main:discord:channel:1482… │ group │ 25d ago │ gemini-3.1-flash-lite-preview │ unknown/200k (?%)
Update available (npm 2026.4.26). Run: openclaw update
Next steps:
Need to share? openclaw status --all
Need to debug live? openclaw logs --follow
Fix reachability first: openclaw gateway probe

bronze bobcatBOT Apr 28, 2026, 2:53 AM

#

Genial: Discord ya aparece ON / OK. Eso es buena señal.

Ahora hay dos ajustes importantes:

El default todavía parece volver a Gemini en sesiones de grupo.
Hay sesiones viejas de Discord con Gemini; conviene probar con sesión nueva.

Ejecuta:

openclaw models set openrouter/moonshotai/kimi-k2.6
openclaw models status
openclaw gateway restart
sleep 5
openclaw status --deep

#

Luego en el Discord donde pruebas:

/new

Después:

responde solo PONG

Si responde, dejamos el backup #1 y ya está.

Si no responde, pega solo las últimas líneas de:

#

openclaw logs --follow

especialmente desde que envías el mensaje.

narrow dune Apr 28, 2026, 2:55 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ openclaw models set openrouter/moonshotai/kimi-k2.6
openclaw models status
openclaw gateway restart
sleep 5
openclaw status --deep

🦞 OpenClaw 2026.4.23 (a979721) — One CLI to rule them all, and one more restart because you changed the port.

Config overwrite: /home/alexifra/.openclaw/openclaw.json (sha256 497e5c3c2659f89f8f929cf064a9d12c0486f8dd7eeaea57a9715316ec97433d -> 7dfe927efa20d4d6827cc75b13e8ad64a31b0072def227af15a65dbc9f2081fc, backup=/home/alexifra/.openclaw/openclaw.json.bak)
Updated ~/.openclaw/openclaw.json
Default model: openrouter/moonshotai/kimi-k2.6

🦞 OpenClaw 2026.4.23 (a979721) — I can run local, remote, or purely on vibes—results may vary with DNS.

Config : ~/.openclaw/openclaw.json
Agent dir : ~/.openclaw/agents/main/agent
Default : openrouter/moonshotai/kimi-k2.6
Fallbacks (2) : openrouter/auto, openai/gpt-4.1-mini
Image model : -
Image fallbacks (0): -
Aliases (4) : GPT -> openai/gpt-5.1-codex, gpt -> openai/gpt-5.4, gemini-lite -> google/gemini-3.1-flash-lite-preview, gemini-flash -> google/gemini-3-flash-preview
Configured models (8): openai/gpt-5.1-codex, openai/gpt-5.4, openrouter/free, google/gemini-3.1-flash-lite-preview, google/gemini-3-flash-preview, openrouter/auto, openai/gpt-4.1-mini, openrouter/moonshotai/kimi-k2.6

Auth overview
Auth store : ~/.openclaw/agents/main/agent/auth-profiles.json
Shell env : off
Providers w/ OAuth/tokens (0): -

brave effective=env:BSAwl7-5...x7NCmChU | env=BSAwl7-5...x7NCmChU | source=env: BRAVE_API_KEY
google effective=env:AIzaSyCx...1ghdoEJY | env=AIzaSyCx...1ghdoEJY | source=env: GEMINI_API_KEY
openai effective=profiles:~/.openclaw/agents/main/agent/auth-profiles.json | profiles=1 (oauth=0, token=0, api_key=1) | openai:default=sk-proj-...fRb8ZXEA | env=sk-proj-...pSn135wA | source=env: OPENAI_API_KEY
openrouter effective=env:sk-or-v1...6a9c8da7 | env=sk-or-v1...6a9c8da7 | source=env: OPENROUTER_API_KEY
perplexity effective=env:sk-or-v1...6a9c8da7 | env=sk-or-v1...6a9c8da7 | source=env: OPENROUTER_API_KEY

OAuth/token status

none

bronze bobcatBOT Apr 28, 2026, 2:56 AM

#

Perfecto: el default ya quedó en OpenRouter/Kimi ✅

Parece que el paste se cortó antes de gateway restart / status --deep. Pega la parte siguiente cuando termine.

Si no salió nada más, corre:

openclaw gateway restart
sleep 10
openclaw status --deep
openclaw gateway status

Y prueba en Discord con:

#

/new

Luego:

responde solo PONG

Si responde, yo dejaría este backup #1 + modelo OpenRouter como estado bueno.

narrow dune Apr 28, 2026, 2:57 AM

#

El agente no responde. mensaje. La aplicacion no respondio

bronze bobcatBOT Apr 28, 2026, 2:57 AM

#

Ok, entonces no cambiemos más backups todavía. Ahora toca ver por qué no respondió: puede ser que el Gateway no esté reachable, que Discord esté descartando el mensaje por allowlist, o que el run falle.

Pega estas salidas:

openclaw gateway status
openclaw status --deep

Y luego mira logs mientras mandas un mensaje en Discord:

openclaw logs --follow

En Discord manda:

#

/new

y después:

responde solo PONG

Pega las líneas nuevas del log desde ese momento.

También confirma este ajuste, porque antes doctor avisó que grupos se descartaban:

openclaw config get channels.discord.groupPolicy

#

openclaw config get channels.discord.groupAllowFrom
openclaw config get channels.discord.allowFrom

Si groupPolicy sigue en allowlist y las listas están vacías, arregla con:

openclaw config set channels.discord.groupPolicy open
openclaw gateway restart

narrow dune Apr 28, 2026, 2:59 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ openclaw gateway status
openclaw status --deep

🦞 OpenClaw 2026.4.23 (a979721) — It's not "failing," it's "discovering new ways to configure the same thing wrong."

│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-27.log
Command: /usr/bin/node /home/alexifra/.local/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: running (pid 6726, state active, sub running, last exit 0, reason 0)
Connectivity probe: ok
Capability: admin-capable

Listening: 127.0.0.1:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

🦞 OpenClaw 2026.4.23 (a979721) — Gateway online—please keep hands, feet, and appendages inside the shell at all times.

│
◇
│
◇
│
◇
OpenClaw status

Overview

bronze bobcatBOT Apr 28, 2026, 2:59 AM

#

Gateway está bien ahora: running, probe OK, listening 127.0.0.1:18789 ✅

Entonces el problema ya no es arranque. Necesitamos ver si Discord está descartando el mensaje o si el agente falla al generar/enviar.

Primero confirma la policy:

openclaw config get channels.discord.groupPolicy
openclaw config get channels.discord.groupAllowFrom
openclaw config get channels.discord.allowFrom

Si groupPolicy no es open, ponlo:

openclaw config set channels.discord.groupPolicy open

#

openclaw gateway restart

Luego logs en vivo:

openclaw logs --follow

Con eso abierto, manda en Discord:

/new

y después:

#

responde solo PONG

Pega las líneas nuevas del log. Ahí veremos si llega el mensaje, si lo filtra la allowlist, si llama al modelo, o si falla al enviar la respuesta.

narrow dune Apr 28, 2026, 3:00 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ openclaw config get channels.discord.groupPolicy
openclaw config get channels.discord.groupAllowFrom
openclaw config get channels.discord.allowFrom

🦞 OpenClaw 2026.4.23 (a979721) — Claws out, commit in—let's ship something mildly responsible.

allowlist

🦞 OpenClaw 2026.4.23 (a979721) — I'm the middleware between your ambition and your attention span.

Config path not found: channels.discord.groupAllowFrom

🦞 OpenClaw 2026.4.23 (a979721) — The only open-source project where the mascot could eat the competition.

Config path not found: channels.discord.allowFrom

bronze bobcatBOT Apr 28, 2026, 3:00 AM

#

Ahí está: Discord está en allowlist y no hay listas configuradas, así que los mensajes de servidor/thread se descartan.

Cámbialo a open:

openclaw config set channels.discord.groupPolicy open
openclaw config validate
openclaw gateway restart
sleep 5
openclaw config get channels.discord.groupPolicy
openclaw status --deep

Debe salir:

#

open

Luego prueba en Discord:

/new

y después:

responde solo PONG

Si responde, el backup #1 queda bien y el problema era la policy restaurada desde backup.

narrow dune Apr 28, 2026, 3:01 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ openclaw config set channels.discord.groupPolicy open
openclaw config validate
openclaw gateway restart
sleep 5
openclaw config get channels.discord.groupPolicy
openclaw status --deep

🦞 OpenClaw 2026.4.23 (a979721) — Hot reload for config, cold sweat for deploys.

Config overwrite: /home/alexifra/.openclaw/openclaw.json (sha256 7dfe927efa20d4d6827cc75b13e8ad64a31b0072def227af15a65dbc9f2081fc -> cbd0a3c4f246b5e09edfb5e9a517ff6ed33f04a5cf1d9051322dedbfe70e03af, backup=/home/alexifra/.openclaw/openclaw.json.bak)
Updated channels.discord.groupPolicy. Restart the gateway to apply.

🦞 OpenClaw 2026.4.23 (a979721) — I'll refactor your busywork like it owes me money.

Config valid: ~/.openclaw/openclaw.json

🦞 OpenClaw 2026.4.23 (a979721) — I read logs so you can keep pretending you don't have to.

Restarted systemd service: openclaw-gateway.service

🦞 OpenClaw 2026.4.23 (a979721) — Open source means you can see exactly how I judge your config.

open

bronze bobcatBOT Apr 28, 2026, 3:02 AM

#

Perfecto — groupPolicy ya está en open ✅

Parece que el paste se cortó antes del status --deep, pero ya tenemos el cambio importante aplicado.

Ahora prueba en Discord:

/new

Luego:

responde solo PONG

Si todavía sale “La aplicación no respondió”, corre logs en vivo:

#

openclaw logs --follow

manda otra vez responde solo PONG, y pega las líneas nuevas. Ahí ya debería verse si llega el mensaje y qué falla.

narrow dune Apr 28, 2026, 3:03 AM

#

sigue sin responder

#

03:01:15+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] starting provider
03:01:16+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord channel users resolved: 1416148785159213106
03:01:16+00:00 error gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] channel exited: Failed to resolve Discord application id
03:01:16+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] auto-restart attempt 1/10 in 5s
03:01:21+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ health 199ms conn=da46a8d8…4c8d id=e3793b54…9a9d
03:01:21+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] starting provider
03:01:21+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord channel users resolved: 1416148785159213106
03:01:22+00:00 error gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] channel exited: Failed to resolve Discord application id
03:01:22+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] auto-restart attempt 2/10 in 11s
03:01:33+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] starting provider
03:01:33+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord channel users resolved: 1416148785159213106
03:01:33+00:00 error gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] channel exited: Failed to resolve Discord application id
03:01:33+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] auto-restart attempt 3/10 in 21s
03:01:55+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] starting provider
03:01:55+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord channel users resolved: 1416148785159213106
03:01:56+00:00 error gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] channel exited: Failed to resolve Discord application id
03:01:56+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] auto-restart attempt 4/10 in 41s
03:02:38+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] starting provider
03:02:38+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord channel users resolved: 1416148785159213106
03:02:38+00:00 error gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] channel exited: Failed to resolve Discord application id
03:02:38+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] auto-restart attempt 5/10 in 82s
03:04:02+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] starting provider
03:04:02+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} discord channel users resolved: 1416148785159213106
03:04:03+00:00 error gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] channel exited: Failed to resolve Discord application id
03:04:03+00:00 info gateway/channels/discord {"subsystem":"gateway/channels/discord"} [default] auto-restart attempt 6/10 in 176s

bronze bobcatBOT Apr 28, 2026, 3:04 AM

#

Creo que ya encontramos el siguiente bloqueo: groupPolicy=open permite el servidor, pero Discord sigue con “mention gating” por defecto. O sea: en canales/threads de servidor, OpenClaw normalmente no responde salvo que menciones al bot o esté configurado requireMention: false.

Para probar rápido, no uses /new por ahora. Eso puede disparar un slash command nativo y Discord muestra “La aplicación no respondió”.

Prueba con mensaje normal en el canal/thread:

@mibot responde solo PONG

Si responde, el fix permanente es desactivar requireMention para tu servidor:

openclaw config set 'channels.discord.guilds.<GUILD_ID>.requireMention' false --strict-json
openclaw config validate
openclaw gateway restart

#

Reemplaza <GUILD_ID> por el ID de tu servidor Discord.

Si quieres diagnosticarlo en logs:

openclaw logs --follow

manda el mensaje normal con mención al bot, y pega las líneas nuevas si sigue sin responder. Ahí debería verse si lo descarta por mention-gating, auth, o error de envío.

#

Ese log ya es el bloqueo real:

channel exited: Failed to resolve Discord application id

Esto no es LLM ni groupPolicy ya. El provider de Discord ni siquiera queda conectado: intenta arrancar, usa el token, pero no puede consultar a Discord el Application ID del bot. Causas típicas:

token Discord restaurado desde backup está viejo/revocado
token corresponde a otra app/bot
la variable/env del token no está disponible para systemd
Discord API/proxy/red bloquea la llamada

Haz esto:

#

openclaw channels status --probe
openclaw config get channels.discord.token

⚠️ No pegues el token si aparece completo.

Mi recomendación: reponer el token actual desde Discord Developer Portal.

Discord Developer Portal → tu aplicación → Bot → copia token actual o reset token.
En la terminal:

openclaw config set channels.discord.token "PEGA_AQUI_EL_TOKEN_NUEVO"
openclaw config validate
openclaw gateway restart

#

sleep 10
openclaw channels status --probe
openclaw logs --tail 80

Cuando esté bien, ya no debe aparecer Failed to resolve Discord application id; debería quedarse Discord ON/OK sin reinicios.

Después probamos de nuevo el mensaje normal.

narrow dune Apr 28, 2026, 3:06 AM

#

no responde nada

bronze bobcatBOT Apr 28, 2026, 3:06 AM

#

Sí, porque el canal Discord está cayéndose antes de escuchar mensajes:

Failed to resolve Discord application id

Mientras ese error exista, el bot no va a responder nada en Discord.

Haz esta verificación:

openclaw channels status --probe

Y necesitamos arreglar el token. Reponlo desde Discord Developer Portal:

#

openclaw config set channels.discord.token "TOKEN_NUEVO_DE_DISCORD"
openclaw config validate
openclaw gateway restart
sleep 10
openclaw channels status --probe
openclaw logs --tail 80

No pegues el token aquí.

Si prefieres usar variable de entorno en vez de guardar token plano:

openclaw config set channels.discord.token --ref-provider default --ref-source env --ref-id DISCORD_BOT_TOKEN

#

pero entonces asegúrate de que el servicio systemd tenga DISCORD_BOT_TOKEN disponible. Para salir rápido del bloqueo, usa temporalmente openclaw config set channels.discord.token "TOKEN_NUEVO...".

narrow dune Apr 28, 2026, 3:07 AM

#

alexifra@LAPTOP-VIVOBOOK-ALEXIFRA:~$ openclaw channels status --probe

🦞 OpenClaw 2026.4.23 (a979721) — Ah, the fruit tree company! 🍎

│
◇
Gateway reachable.

Discord default: enabled, configured, stopped, disconnected, token:config, probe failed, error:Failed to resolve Discord application id

Tip: status --deep adds gateway health probes to status output (requires a reachable gateway).

bronze bobcatBOT Apr 28, 2026, 3:07 AM

#

Confirmado: Gateway OK, Discord roto por token/app lookup.

Estado actual:

Discord default: stopped, disconnected
error: Failed to resolve Discord application id

Siguiente paso: reemplazar el token de Discord por uno válido.

En Discord Developer Portal:

Abre tu aplicación/bot.
Ve a Bot.
Reset Token o copia el token actual.
En tu terminal:

#

openclaw config set channels.discord.token "TOKEN_NUEVO"
openclaw config validate
openclaw gateway restart
sleep 10
openclaw channels status --probe

Debe cambiar a algo tipo connected / OK y ya no mostrar Failed to resolve Discord application id.

Después prueba de nuevo en Discord.

narrow dune Apr 28, 2026, 3:10 AM

#

"TOKEN_NUEVO" va entre comillas o sin comillas ?

#Pasos para restaurar Open Claw de mis backup