Hey, thanks for the detailed report. Your diagnosis is spot on. This is an ABI mismatch between the Node runtime inside the Windows agent-cli and the native better-sqlite3 binary, which makes exec-daemon crash and the worker exit with code 1 right after registration. That’s why it gets stuck on “Waiting for a worker” forever. Your note about HTTP/1.1 being a red herring is also correct. This issue isn’t network-related.
This is something we’re already tracking on Windows. There are similar threads here: 1, 2. I’ve passed this report to the team as well, with all the details.
Unfortunately, there’s no user-side workaround right now. Like you noticed, regenerating agent-cli reproduces the same mismatch because the incompatible binary ships as part of the bundle. I also wouldn’t recommend trying a manual npm rebuild on managed files since it’ll likely just make things more confusing.
I can’t share an exact timeline yet, but I’ll reply in the thread once there’s an update.