github-featured/omnigent-ai--omnigent
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity

docs(openclaw): reflect live-verified compatibility status (#3955)

Browse Source 
PR #3420 validated the OpenClaw Gateway ACP path end-to-end against a live
Gateway, but docs/openclaw.md still read as if streaming/final replies were
only protocol-matched and the integration provisional. Update the
compatibility section to state what live validation confirmed — streaming
assistant replies, native tool execution, ACP permission routing, and session
resume — and reframe the remaining Control-UI-sync gap as a known limitation
rather than an open question. Keep the note that CI cannot run OpenClaw.

Co-authored-by: Isaac

Signed-off-by: Pat Sukprasert <pattara.sk127@gmail.com>
This commit is contained in:
Pat Sukprasert
2026-08-03 21:50:46 +08:00
committed by GitHub
parent de0f62ea2d
commit 074a467efc
1 changed files with 19 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/openclaw.md
+19 -9
View File
@@ -99,15 +99,25 @@ servers.
### Compatibility status
The protocol-level path matches for initialization, session creation, prompts,
cancellation, and streaming updates. Manual validation against a live Gateway
has also confirmed the configured worktree, native shell/filesystem tools, and
Omni conversation resume. Bidirectional synchronization with the OpenClaw
Control UI and per-session Omnigent MCP are not supported by this integration.
This integration has been validated end-to-end against a live OpenClaw Gateway.
The full turn cycle works: initialization, session creation, prompts,
cancellation, and **streaming assistant replies** (final messages arrive in the
Omni conversation). Live validation also confirmed the configured worktree,
native shell/filesystem tool execution, ACP permission requests (approvals route
through ACP rather than OpenClaw's chat), and Omni conversation resume after
close.
Known limitation: bidirectional synchronization with the OpenClaw Control UI is
not supported. Omni owns the outer conversation; the Control UI is a separate
Gateway client, so messages entered there while Omni is offline are not imported
into the Omni conversation. Per-session Omnigent MCP is also unsupported (see
[Why `omnigent_mcp` must be false](#why-omnigent_mcp-must-be-false)).
OpenClaw cannot be installed or run in the project's managed development and CI
environments.
environments, so this path is not exercised by automated CI; changes to the ACP
client should be re-validated manually against a Gateway.
If session creation reports that `mcpServers` is unsupported, confirm that the
entry contains `omnigent_mcp: false` and restart the Omnigent session. If the
turn reaches OpenClaw but no final reply appears, capture both Omnigent and
OpenClaw logs and report the behavior before relying on the integration.
entry contains `omnigent_mcp: false` and restart the Omnigent session. If a turn
reaches OpenClaw but no final reply appears, capture both Omnigent and OpenClaw
logs and file an issue.