chore(sync): mirror docs from openclaw/openclaw@dcfd5913fd

This commit is contained in:
openclaw-docs-sync[bot] 2026-04-25 20:38:54 +00:00
parent 08088b2af7
commit 0b6eda0511
3 changed files with 19 additions and 2 deletions

View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "34fb96622eb69d11d95fb0ea90f755a73939842a",
"syncedAt": "2026-04-25T20:36:40.174Z"
"sha": "dcfd5913fd24a7fce8fe804bf687f4d4856a6652",
"syncedAt": "2026-04-25T20:37:22.632Z"
}

View File

@ -384,6 +384,11 @@ Important behavior:
milliseconds of idle time (default 10 minutes; set `0` to disable) and
one-shot embedded runs clean them up at run end
Runtime adapters may normalize this shared registry into the shape their
downstream client expects. For example, embedded Pi consumes OpenClaw
`transport` values directly, while Claude Code and Gemini receive CLI-native
`type` values such as `http`, `sse`, or `stdio`.
## Saved MCP server definitions
OpenClaw also stores a lightweight MCP server registry in config for surfaces

View File

@ -164,6 +164,18 @@ OPENCLAW_LIVE_CLI_BACKEND=1 \
pnpm test:live src/gateway/gateway-cli-backend.live.test.ts
```
Cheap Gemini MCP config smoke:
```bash
OPENCLAW_LIVE_TEST=1 \
pnpm test:live src/agents/cli-runner/bundle-mcp.gemini.live.test.ts
```
This does not ask Gemini to generate a response. It writes the same system
settings OpenClaw gives Gemini, then runs `gemini --debug mcp list` to prove a
saved `transport: "streamable-http"` server is normalized to Gemini's HTTP MCP
shape and can connect.
Docker recipe:
```bash