Autopilot Mode AssertionError in Copilot CLI #1743
Description
Describe the bug
Autopilot Mode AssertionError in Copilot CLI
When I run Copilot CLI in autopilot mode, I occasionally hit a problem – especially on more complex tasks.
- The command starts fine and executes for a while.
- After some time (usually during a write operation) an AssertionError is thrown with a long stack trace such as:
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
aB(t[TNe]===0);return}if(t[hU]&&!t[SNe]){t[hU](),t[hU]=null;return}if(t[ag]&&t[ag].resume(),t[Wgt])t[bU]=2;else
if(t[bU]===2){e?(t[bU]=1,queueMicrotask(()=>Zbn(t))):Zbn(t);continue}if(t[TNe]===0||t[BNe]>=(Wbn(t)||1))return;let
n=t[dX][t[uX]];if(t[rS].protocol==="https:"&&t[gU]!==n.servername){if(t[BNe]>0)return;t[gU]=n.servername,t[ag]?.destroy(new Edo("servername changed"),()=>{t[ag]=null,vgt(t)})}if(t[Sle]
)return;…
(stack trace continues through several minified modules)
- After the assertion, the screen starts flickering and eventually you see:
Execution failed: Error: Failed to get response from the AI model; retried 5 times (total retry wait time: 88.52313307094607 seconds) Last error: CAPIError: 503
{"error":{"message":"HTTP/2 GOAWAY connection terminated","type":"connection_error"}}
The process then begins retrying and burns through additional premium requests (e.g. Continuing autonomously (3 premium requests)), but never produces a result.
Additional notes
- This issue occurs much more frequently with opus‑4.6 models.
- I’ve almost never seen it when using the sonnet models.
Affected version
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
Additional context
No response