Problem Description

The --reset-session flag in the openclaw acp command causes a significant delay in the startup process. This leads to connection failures in clients like the Zed editor's ACP bridge integration, which are sensitive to startup latency.

Key Observations

• Using the --reset-session flag causes a failure with the error: Internal error: { "details": "gateway not connected" }.
• Removing the flag resolves the issue.
• The delay introduced by --reset-session exceeds the timeout limits of latency-sensitive clients like Zed.

Root Cause

The --reset-session flag triggers session cleanup and re-initialization, adding extra delay during the handshake process between the client and server.

Proposed Solution

Optimize the session reset process to minimize latency. Several approaches can be considered:

1. Async Initialization: Perform session re-initialization asynchronously, allowing the handshake process to proceed without waiting for cleanup to complete.
2. Priority Management: Enhance timeout configurations or enable a handshake bypass mechanism temporarily during session reset.
3. Conditional Behavior: Implement an adaptive behavior for --reset-session to detect latency-sensitive sessions and reduce delays automatically.

---

Next Steps

1. Investigate the code path for --reset-session flag in openclaw acp.
2. Evaluate the possibility of async initialization or timeout adjustment.
3. Test changes to ensure compatibility with latency-sensitive clients like Zed.
4. Validate against the existing test suite to ensure no regressions.