Bug: HTTP API /tools/invoke returns "Tool not available: browser"

Summary

The browser tool cannot be invoked via HTTP API /tools/invoke, returning {"ok":false,"error":{"type":"not_found","message":"Tool not available: browser"}}. However, the same tool works correctly when called directly in a WebSocket session or from within the agent.

Steps to Reproduce

1. Start OpenClaw Gateway with browser plugin enabled
2. Call HTTP API:

   curl -X POST http://127.0.0.1:18789/tools/invoke \
     -H "Authorization: Bearer $GATEWAY_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{"tool":"browser","action":"status","args":{}}'

3. Observe response: {"ok":false,"error":{"type":"not_found","message":"Tool not available: browser"}}

Expected Behavior

The browser tool should be available via HTTP API and return its status, similar to other tools like sessions_list which work correctly.

Root Cause Analysis

The bug is in src/gateway/tools-invoke-http.ts:

const { agentId, tools } = resolveGatewayScopedTools({
    // ...
    disablePluginTools: isKnownCoreToolId(toolName),  // <-- Problem here
    // ...
});

The logic flow:

1. browser is defined in CORE_TOOL_DEFINITIONS with profiles: [] (see src/agents/tool-catalog.ts)
2. This makes isKnownCoreToolId("browser") return true
3. disablePluginTools is set to true, blocking all plugin tools from being loaded
4. However, browser's actual implementation comes only from the plugin (there is no createBrowserTool in core)
5. Result: browser tool is not found in the tools list

Evidence

• canvas (also profiles: []) returns tool_error instead of not_found because it has a core implementation (createCanvasTool)
• browser has NO core implementation - it relies entirely on the plugin
• Other tools like sessions_list work correctly via HTTP API

Suggested Fix

Modify src/gateway/tools-invoke-http.ts:

// Before (line ~153)
disablePluginTools: isKnownCoreToolId(toolName),

// After
disablePluginTools: isKnownCoreToolId(toolName) && toolName !== "browser",

Alternatively, consider removing browser from CORE_TOOL_DEFINITIONS since its implementation is plugin-only.

Environment

• OpenClaw version: 2026.4.15
• Platform: Windows
• Node.js: v24.x

Related Files

• src/gateway/tools-invoke-http.ts - HTTP API endpoint
• src/agents/tool-catalog.ts - CORE_TOOL_DEFINITIONS (browser entry)
• src/plugins/tools.ts - Plugin tool loading logic