Skip to content

[Bug]: ACP --reset-session causes 'gateway not connected' in latency-sensitive clients (Zed) #10693

@zesty-clawd

Description

@zesty-clawd

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 with Internal 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

  1. Configure a remote OpenClaw Gateway.
  2. In Zed settings.json, configure an ACP extension using openclaw acp with the --reset-session flag.
  3. Observe the gateway not connected error.
  4. Remove the flag and observe success.

Environment

  • Gateway: macOS (Mac mini)
  • Client: Windows (Zed Editor)
  • OpenClaw Version: v2026.2.2-3

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingstaleMarked as stale due to inactivity

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions