Describe the bug
Summary
GitHub Copilot CLI v1.0.31 enters an infinite React/Ink render loop immediately after startup and the main pane becomes unresponsive. The log floods
with "Maximum update depth exceeded". Downgrading to v1.0.28 immediately resolves the problem. Note: on this PC the loop can occur even when launched outside a
repository.
Environment
- OS: Windows 11
- PowerShell: pwsh 7.6.0
- Node.js (bundled): v24.11.1
- Copilot CLI: 1.0.31 (broken) / 1.0.28 (works)
- Terminal: Windows Terminal 1.24.10921.0
- IDE: VS Code Insiders 1.117.0 (IDE MCP bridge)
- Logs: ~/.copilot/logs/
Reproduction
- npm install -g @github/copilot@1.0.31 (mailto:copilot@1.0.31)
- Run copilot in a terminal (or VS Code integrated terminal)
- Within ~1–2s the main pane freezes and process log shows repeated "Maximum update depth exceeded" errors
Key observations
- Same machine and repo: v1.0.31 worked at ~05:27 UTC, but from ~06:13 UTC onward every v1.0.31 session entered the loop — suggests a server-side change
triggered the regression.
- Downgrading to v1.0.28 fixes it immediately.
- On this machine, loop can occur even outside a repo (repository=undefined).
Log excerpts (attachments not available; excerpts pasted)
- First broken session (approx)
2026-04-17T06:13:21.331Z [INFO] Starting Copilot CLI:
1.0.31
2026-04-17T06:13:22.554Z [INFO] [Octokit] GET /repos/.../pulls?... - 200
2026-04-17T06:13:22.670Z [ERROR] Maximum update depth exceeded. ... ← first render-loop (670ms after Octokit)
(continues ~1/sec — ~285 occurrences)
- Latest broken session (approx)
2026-04-17T14:24:22.888Z [INFO] Starting Copilot CLI:
1.0.31
2026-04-17T14:24:24.410Z [ERROR] [Octokit] GET /repos/.../pulls?... - 403
2026-04-17T14:24:26.275Z [ERROR] GitHub MCP server configured after authentication
2026-04-17T14:24:27.037Z [ERROR] Maximum update depth exceeded. ...
(continues — thousands of occurrences in worst sessions)
Workaround npm install -g @github/copilot@1.0.28 (mailto:copilot@1.0.28)
Analysis / Hypothesis A React/Ink UI bug in v1.0.31 (likely a useEffect updating a value that is a dependency, causing a self-triggering update loop). The
change from working→broken on the same binary suggests a server-side response difference may be the trigger.
Affected version
GitHub Copilot CLI 1.0.31.
Steps to reproduce the behavior
No response
Expected behavior
No response
Additional context
No response
Describe the bug
Summary
GitHub Copilot CLI v1.0.31 enters an infinite React/Ink render loop immediately after startup and the main pane becomes unresponsive. The log floods
with "Maximum update depth exceeded". Downgrading to v1.0.28 immediately resolves the problem. Note: on this PC the loop can occur even when launched outside a
repository.
Environment
Reproduction
Key observations
triggered the regression.
Log excerpts (attachments not available; excerpts pasted)
2026-04-17T06:13:21.331Z [INFO] Starting Copilot CLI:
1.0.31
2026-04-17T06:13:22.554Z [INFO] [Octokit] GET /repos/.../pulls?... - 200
2026-04-17T06:13:22.670Z [ERROR] Maximum update depth exceeded. ... ← first render-loop (670ms after Octokit)
(continues ~1/sec — ~285 occurrences)
2026-04-17T14:24:22.888Z [INFO] Starting Copilot CLI:
1.0.31
2026-04-17T14:24:24.410Z [ERROR] [Octokit] GET /repos/.../pulls?... - 403
2026-04-17T14:24:26.275Z [ERROR] GitHub MCP server configured after authentication
2026-04-17T14:24:27.037Z [ERROR] Maximum update depth exceeded. ...
(continues — thousands of occurrences in worst sessions)
Workaround npm install -g @github/copilot@1.0.28 (mailto:copilot@1.0.28)
Analysis / Hypothesis A React/Ink UI bug in v1.0.31 (likely a useEffect updating a value that is a dependency, causing a self-triggering update loop). The
change from working→broken on the same binary suggests a server-side response difference may be the trigger.
Affected version
GitHub Copilot CLI 1.0.31.
Steps to reproduce the behavior
No response
Expected behavior
No response
Additional context
No response