#No getting any response back

1 messages · Page 1 of 1 (latest)

whole vessel
#

My bot just hangs when ever sending a message, it never reaches my openrouter

  "auth": {
    "profiles": {
      "openrouter:default": {
        "provider": "openrouter",
        "mode": "api_key"
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "openrouter/hunter-alpha",
        "fallbacks": [
          "openrouter/moonshotai/kimi-k2.5"
        ]
      },
      "models": {
        "openrouter/auto": {
          "alias": "OpenRouter"
        },
        "openrouter/hunter-alpha": {},
        "openrouter/openai/gpt-oss-20b": {},
        "openrouter/moonshotai/kimi-k2.5": {}
      },
      "workspace": "/home/openclaw/.openclaw/workspace",
      "memorySearch": {
        "enabled": true,
        "provider": "gemini"
      },
      "compaction": {
        "mode": "safeguard"
      },
      "heartbeat": {
        "every": "6h"
      }
    },
    "list": [
      {
        "id": "main",
        "model": "openrouter/hunter-alpha"
      }
    ]
  },
  "tools": {
    "profile": "coding",
    "web": {
      "search": {
        "enabled": true,
        "provider": "gemini",
        "gemini": {
          "apiKey": "...",
          "model": "gemini-2.5-flash-lite"
        }
      }
    }
  },
  "hooks": {
    "internal": {
      "enabled": true,
      "entries": {
        "boot-md": {
          "enabled": true
        },
        "session-memory": {
          "enabled": true
        }
      }
    }
  },
  "plugins": {
    "allow": [
      "memory-openviking",
      "whatsapp"
    ],
    "slots": {
      "memory": "memory-openviking"
    },
    "entries": {
      "whatsapp": {
        "enabled": true
      },
      "memory-openviking": {
        "enabled": true,
        "config": {
          "mode": "local",
          "configPath": "/home/openclaw/.openviking/ov.conf",
          "port": 1933
        }
      },
      "memory-core": {
        "enabled": false
      },
      "memory-lancedb": {
        "enabled": false
      }
    }
  }
}
desert pantherBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

frozen lanceBOT
#

Two things jump out in that config that can make it look like the bot is “hanging” and never even getting to OpenRouter:

1) Your OpenRouter auth profile has no key

This block:

"auth": { "profiles": { "openrouter:default": { "provider": "openrouter", "mode": "api_key" } } }

only declares “use API key mode” — it does not provide the secret.

You still need OPENROUTER_API_KEY to exist on the gateway host (and if you run the gateway as a service, it usually won’t inherit your shell env).

Quick fix options (pick one):

  • Put it in ~/.openclaw/.env on the gateway host:
# 
"memorySearch": { "enabled": true, "provider": "gemini" }

…but the only Gemini key in your config is under tools.web.search.gemini.apiKey, which is separate from memory search. If memory search runs early in the pipeline, it can block/fail before the LLM request.

Fast test: temporarily set memorySearch.enabled: false and restart gateway. If it starts replying, you’ve found the blocker. Then properly configure Gemini for memory search (e.g. GEMINI_API_KEY / the memorySearch key field per docs).

What I need from you to pinpoint it (copy/paste outputs)

Run these on the gateway host:

openclaw --version
openclaw status --all
# 
openclaw models status
openclaw channels status

Then:

openclaw logs --follow

…and send one message while the log tail is running. Paste the ~30-60 lines around the attempt (tokens are redacted in status --all already).

That’ll tell us immediately whether it’s (a) missing OpenRouter creds, (b) stuck in memory search / OpenViking, or (c) channel gating (pairing/allowlist) preventing the agent run.

whole vessel
#

Im not sure if something changed with the latest update, i was using open viking on 2026.11.3, and it works when I disable the plugin but doesn't when I enable it

frozen lanceBOT
#

Yeah, that symptom (“works with plugin disabled, hangs with it enabled”) is almost always: the memory plugin call is blocking before the LLM step, so the run never gets to OpenRouter.

A few targeted checks that will tell us exactly where it’s stuck:

1) Check plugin load + schema issues (fast)

Run:

openclaw plugins doctor
openclaw plugins info memory-openviking

Paste the output. info will show the plugin’s configSchema (so we can confirm whether configPath / port are still valid keys in the current plugin version).

Docs: https://docs.openclaw.ai/cli/plugins

2) Make sure the plugin is updated to match your OpenClaw version

#

If you recently updated OpenClaw but not the plugin, update plugins too:

openclaw plugins update memory-openviking
# or
openclaw plugins update --all
openclaw gateway restart

(Plugin API/schema changes between OpenClaw versions can absolutely cause exactly this kind of “hang”.)

3) Isolate whether it’s the slot (memory) or just “plugin enabled”

For a super clean A/B test, keep the plugin enabled but don’t route memory to it:

  • keep plugins.entries.memory-openviking.enabled: true
  • temporarily set:
# 
  plugins: { slots: { memory: "memory-core" } }

If that fixes the hang, the culprit is specifically calls into OpenViking as the active memory backend (very likely the session-memory hook).

4) Grab the one log line that proves it

Tail logs, send one message, and paste what happens right before it stalls:

openclaw logs --follow

If it’s OpenViking connectivity (port/service down, wrong bind address, no timeout, etc.) we’ll see it immediately in the log around the memory hook/plugin call.