conversation history

[Bug]: openclaw sessions list returns exit code 0 despite error output

[Bug]: Custom OpenAI-compatible provider works via direct /v1/chat/completions, but OpenClaw 2026.3.28 always fails with "Connection error"

OpenClaw 2026.3.28 fails on every chat turn for a custom OpenAI-compatible provider with “LLM request failed: network connection error”, even though direct /v1/models and /v1/chat/completions calls to the same endpoint succeed from the same Windows machine.

[Bug]: openclaw agents add TypeError

openclaw agents add ops 🦞 OpenClaw 2026.4.1 (da64a97) — No $999 stand required. ┌ Add OpenClaw agent │ ◇ Workspace directory │ /Users/lizhenzhong/.openclaw/workspace-ops │ ◇ Copy auth profiles from "main"? │ No │ ◇ Configure model/auth for this agent now? │ No 19:58:57+08:00 [agents/auth-profiles] inherited auth-profiles from main agent TypeError: Cannot read properties of undefined (reading 'resolveConfigured')

[Bug]: issue while adding Custom MCP server

[Bug]: openclaw gateway shut down suddenly without prompt

openclaw gateway crashed suddenly.

Gateway Service Installation Failure: Missing systemd Service File

The OpenClaw Gateway service fails to install with a systemd error indicating the service unit file does not exist. This affects users attempting to run the gateway as a systemd user service.

Ollama tries to pull when it shouldn't

ollama launch codex - ⚠ Model metadata for `gpt-oss:20b` not found. Defaulting to fallback metadata; this can degrade performance and cause issues.

lossless-claw plugin loads with provenance warning despite working correctly

openai-codex-responses provider sends oversized `instructions` field, gets 400 Bad Request

The `openai-codex` provider (targeting `chatgpt.com/backend-api/codex/responses`) does not cap the `instructions` field before sending. When workspace bootstrap files + system prompt + tool schemas exceed ~32 KiB, the API returns `{"detail":"Bad Request"}` (400). This makes GPT-5.4 unusable for agents with larger workspaces.

Responses API → Chat Completions bridge does not translate `developer` role to `system` for non-OpenAI providers

After unzipping the new version of ollama, 0.18.0, executing "ollama -v" does not display the version number

[Bug]: WhatsApp outbound sends fail with 'No active WhatsApp Web listener' despite channel being connected

When attempting to send outbound WhatsApp messages via `openclaw message send` or `sessions_send` RPC tool, the gateway returns `UNAVAILABLE: No active WhatsApp Web listener (account: default)` — even though `openclaw channels status` shows `linked, running, connected` and inbound messages + auto-replies work perfectly.

[Bug]: openclaw cron list closes with 1000 while cron scheduler is running (2026.3.13)

- Version: OpenClaw 2026.3.13 - Host: Linux VPS, root user, systemd user service - openclaw gateway status => RPC probe: ok, listener active on 127.0.0.1:18789 - openclaw cron list => gateway closed (1000 normal closure): no close reason Cron is actually active: /root/.openclaw/cron/jobs.json contains 6 jobs logs contain cron: started with jobs: 6 run logs exist under /root/.openclaw/cron/runs/*.jsonl

[Bug]: OpenClaw does not switch provider when changing model in UI, causing requests to be routed to the default provider

When multiple model providers (e.g., Azure OpenAI and Zhipu) are configured in OpenClaw, switching to a model from a non-default provider in the UI does not correctly update the routing. The request is still sent to the default provider, resulting in a "model not allowed" error.

Telegram: image/photo attachments fail with "Something went wrong" after 2026.4.x update

Sending any image via Telegram results in a generic error response: **"Something went wrong while processing your request. Please try again."** This began after updating from **2026.3.31 → 2026.4.2**. Images were working prior to the update.

Ollama fails to use a coding model that doesn't fit into Vulkan memory

plugins install: --trust flag undocumented / dangerous code blocks community plugins that use child_process

When trying to install a community plugin (`openclaw-codex-app-server`) that legitimately uses `child_process` (to spawn the Codex CLI), installation is blocked with no way to proceed: \`\`\` WARNING: Plugin "openclaw-codex-app-server" contains dangerous code patterns: Shell command execution detected (child_process) (src/client.ts:660) Plugin "openclaw-codex-app-server" installation blocked: dangerous code patterns detected \`\`\`

[Bug] Isolated cron sessions still cannot deliver to Telegram on v2026.3.28

Browser start reports CDP unreachable even while managed Chromium is live and /json/version responds

On this OpenClaw 2026.4.2 Linux host, the official managed browser lane for profile `openclaw` is degraded even though Chromium/CDP itself is healthy.