Double Agent Issue
Diagnostic Data:
Environment: Windows 10. Gateway is registered as a Windows Scheduled Task (\OpenClaw Gateway) pointing to C:\Users\deane.openclaw\gateway.cmd.
Gateway Log (openclaw-2026-02-18.log): Shows Service is loaded but not running (likely exited immediately). and Runtime: stopped (state Ready).
Observations: Attempting to run the TS instance results in both agents "fighting" for connectivity. When one action is taken in one instance, the other goes offline.
Diagnosis Requested:
Is using the same Discord/Telegram tokens across two separate Gateway instances causing a WebSocket collision?
How can we run a separate TS instance without the Windows Scheduled Task for the Main instance overriding it or causing port/service conflicts?
What is the correct way to structure this "Triad" (Main + TS + Coordination Group) on a single Windows machine to avoid this "suicide loop"?
Environment: Windows 10. Gateway is registered as a Windows Scheduled Task (\OpenClaw Gateway) pointing to C:\Users\deane.openclaw\gateway.cmd.
Gateway Log (openclaw-2026-02-18.log): Shows Service is loaded but not running (likely exited immediately). and Runtime: stopped (state Ready).
Observations: Attempting to run the TS instance results in both agents "fighting" for connectivity. When one action is taken in one instance, the other goes offline.
Diagnosis Requested:
Is using the same Discord/Telegram tokens across two separate Gateway instances causing a WebSocket collision?
How can we run a separate TS instance without the Windows Scheduled Task for the Main instance overriding it or causing port/service conflicts?
What is the correct way to structure this "Triad" (Main + TS + Coordination Group) on a single Windows machine to avoid this "suicide loop"?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
