device allocation

[Bug]: Why tools.profile (coding) allowlist contains unknown entries ?

2026.3.14, tools.profile (coding) allowlist contains unknown entries (apply_patch, image). These entries are shipped core tools but unavailable in the current runtime/provider/model/config. What matter? Why?

[Bug]: openclaw --profile <name> devices list fails with gateway closed (1000) / handshake timeout on 2026.3.13

When using a non-default profile / secondary gateway, `openclaw --profile <name> devices list` fails with: gateway connect failed: Error: gateway closed (1000): [openclaw] Failed to start CLI: Error: gateway closed (1000 normal closure): no close reason

[Skills] 37 "Skipping skill path that resolves outside its configured root" warnings from built-in extensions

```markdown

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

[Bug]: v0.17.0 4*2080ti 22G Qwen3.5 RPC call to sample_tokens timed out.

[Bug]: Regression since 2026.3.22: agent replies “I’ll do it now” but execution stalls; once triggered it persists across new sessions until downgrade

After updating from 2026.3.22 (also reproduced on 2026.3.23, 2026.3.24, 2026.3.31), the main agent intermittently enters a broken state: - It sends an acknowledgement like “I’ll do it now” - Then actual execution does not proceed (or appears stuck/misaligned) - Once this state appears, it does **not** recover by creating a new session - Gateway restart may temporarily recover once, but issue returns quickly - Only downgrading to an older version reliably recovers behavior This is a high-impact regression because user-visible intent/response and actual execution diverge.

Ollama desktop app respawns ollama.exe serve after manual process termination on Windows

[Bug]: SessionManager.fileEntries grows unbounded in memory, causing 1.4GB+ heap growth in long-running sessions

There's a slow leak hiding in the persistence layer that most people are working around without knowing what's causing it. `SessionManager.fileEntries` is an in-memory array that mirrors every line written to the JSONL session transcript. Every message, tool call, tool result, and metadata entry gets pushed to it. Nothing ever removes them. Over hours of normal use, this array quietly accumulates hundreds of thousands of objects, eventually holding 1.4GB+ of retained heap. V8 can't collect any of it because SessionManager holds a live reference to the array for the lifetime of the process. The tricky part: the LLM context window stays bounded. `replaceMessages()` keeps `Agent._state.messages` at a manageable size during compaction. So from the model's perspective, everything looks fine. But underneath, `fileEntries` is a parallel data structure in the persistence layer that compaction never touches. Two layers, only one with a ceiling. This is likely the root cause behind multiple reported memory and session-bloat issues, including #6190, #13758, #2254, and #20910, which all share the same symptom pattern. It's a contributing factor in several others (see Related Issues below).

[Bug/Troubleshoot] Permission Denied / File does not exist

[Feature]: Multi-provider credential pools for cross-provider failover and rotation

localePrefix: "as-needed" causes 308 redirects on locale subpaths in Next.js 16 (Turbopack) - middleware never called

[Bug]: `vertex_ai/gemini-embedding-2-preview` routes to `:predict` endpoint, returns `FAILED_PRECONDITION`

[Bug]: session_send does not work for sandboxed agents

After enabling sandbox mode for all my agents except the main agent, my agents are no longer able to send messages to each other. `sessions_send` does not work (times out). The non-sandbox agent (main) does not have this issue. This suggests a sandbox-specific regression in session cross-session routing.

[0.17.5][macOS Apple Silicon] model runner unexpectedly stopped (EOF/exit status 2) on /api/generate

message tool: 'No active WhatsApp Web listener' error despite channel showing connected

The \message\ tool consistently returns \Error: No active WhatsApp Web listener (account: default)\ when attempting to send outbound messages, even though inbound messages are flowing normally and \openclaw channels status\ reports the WhatsApp channel as connected.

openclaw gateway restart fails to restart service (SIGTERM instead of SIGUSR1)

When running `openclaw gateway restart`, the Gateway service stops but fails to restart. Only a manual system restart (or computer reboot) restores the service.

[Bug]: Stale plugin config entry emits noisy warning on every CLI invocation with no way to clean it up

feat: pass requesterSenderId and senderIsOwner to ChannelAgentToolFactory

nonInteractivePermissions needs an 'allow' option — currently only deny/fail

Anthropic 'out of extra usage' error misclassified as format instead of billing