-
-
Notifications
You must be signed in to change notification settings - Fork 69k
[Bug]: ACP --reset-session causes 'gateway not connected' in latency-sensitive clients (Zed) #10693
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingstaleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Description
Using the --reset-session flag with openclaw acp causes connection failures in clients that are sensitive to startup latency, such as the Zed editor's ACP (Agent Client Protocol) bridge integration.
Context
When connecting a remote OpenClaw Gateway from a local client using Zed's ACP bridge:
- With
--reset-session: Connection consistently fails withInternal error: { "details": "gateway not connected" }. - Without
--reset-session: Connection succeeds immediately.
Analysis
The --reset-session flag triggers session cleanup and re-initialization on the server side. This adds a significant delay to the initial handshake. Clients like Zed appear to have a very strict timeout for ACP server startup; if the handshake (including the reset logic) takes too long, the client considers the gateway unreachable.
Steps to Reproduce
- Configure a remote OpenClaw Gateway.
- In Zed
settings.json, configure an ACP extension usingopenclaw acpwith the--reset-sessionflag. - Observe the
gateway not connectederror. - Remove the flag and observe success.
Environment
- Gateway: macOS (Mac mini)
- Client: Windows (Zed Editor)
- OpenClaw Version: v2026.2.2-3
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingstaleMarked as stale due to inactivityMarked as stale due to inactivity
Type
Fields
Give feedbackNo fields configured for issues without a type.