mirror of https://github.com/openclaw/openclaw.git synced 2026-03-26 17:32:16 +00:00

Files

Tak Hoffman 9c7823350b feat: add /tools runtime availability view (#54088 )

* test(memory): lock qmd status counts regression

* feat: make /tools show what the agent can use right now

* fix: sync web ui slash commands with the shared registry

* feat: add profile and unavailable counts to /tools

* refine: keep /tools focused on available tools

* fix: resolve /tools review regressions

* fix: honor model compat in /tools inventory

* fix: sync generated protocol models for /tools

* fix: restore canonical slash command names

* fix: avoid ci lint drift in google helper exports

* perf: stop computing unused /tools unavailable counts

* docs: clarify /tools runtime behavior

2026-03-24 21:09:51 -05:00

2.9 KiB

Raw Blame History

summary, read_when, title

summary

read_when

title

Loopback WebChat static host and Gateway WS usage for chat UI

Debugging or configuring WebChat access

WebChat

WebChat (Gateway WebSocket UI)

Status: the macOS/iOS SwiftUI chat UI talks directly to the Gateway WebSocket.

What it is

A native chat UI for the gateway (no embedded browser and no local static server).
Uses the same sessions and routing rules as other channels.
Deterministic routing: replies always go back to WebChat.

Quick start

Start the gateway.
Open the WebChat UI (macOS/iOS app) or the Control UI chat tab.
Ensure gateway auth is configured (required by default, even on loopback).

How it works (behavior)

The UI connects to the Gateway WebSocket and uses chat.history, chat.send, and chat.inject.
chat.history is bounded for stability: Gateway may truncate long text fields, omit heavy metadata, and replace oversized entries with [chat.history omitted: message too large].
chat.inject appends an assistant note directly to the transcript and broadcasts it to the UI (no agent run).
Aborted runs can keep partial assistant output visible in the UI.
Gateway persists aborted partial assistant text into transcript history when buffered output exists, and marks those entries with abort metadata.
History is always fetched from the gateway (no local file watching).
If the gateway is unreachable, WebChat is read-only.

Control UI agents tools panel

The Control UI /agents Tools panel has two separate views:
- Available Right Now uses tools.effective(sessionKey=...) and shows what the current session can actually use at runtime, including core, plugin, and channel-owned tools.
- Tool Configuration uses tools.catalog and stays focused on profiles, overrides, and catalog semantics.
Runtime availability is session-scoped. Switching sessions on the same agent can change the Available Right Now list.
The config editor does not imply runtime availability; effective access still follows policy precedence (allow/deny, per-agent and provider/channel overrides).

Remote use

Remote mode tunnels the gateway WebSocket over SSH/Tailscale.
You do not need to run a separate WebChat server.

Configuration reference (WebChat)

Full configuration: Configuration

Channel options:

No dedicated webchat.* block. WebChat uses the gateway endpoint + auth settings below.

Related global options:

gateway.port, gateway.bind: WebSocket host/port.
gateway.auth.mode, gateway.auth.token, gateway.auth.password: WebSocket auth (token/password).
gateway.auth.mode: "trusted-proxy": reverse-proxy auth for browser clients (see Trusted Proxy Auth).
gateway.remote.url, gateway.remote.token, gateway.remote.password: remote gateway target.
session.*: session storage and main key defaults.

2.9 KiB Raw Blame History