What happened?
I'm getting this error when running tasks in Gemini CLI:
..\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsPtyAgent.js:93
throw new Error('Cannot resize a pty that has already exited');
^
Error: Cannot resize a pty that has already exited
at WindowsPtyAgent.resize (--\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsPtyAgent.js:93:19)
at WindowsTerminal. (--\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsTerminal.js:131:26)
at Object.run (..\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsTerminal.js:167:50)
at ..\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsTerminal.js:73:32
at Array.forEach ()
at Socket. (..\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsTerminal.js:68:42)
at Socket.emit (node:events:531:35)
at addChunk (node:internal/streams/readable:561:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
at Readable.push (node:internal/streams/readable:392:5)
Node.js v22.20.0
What did you expect to happen?
bug fixed
Client information
- CLI Version: 0.13.0
- Git Commit: 230056c
- Session ID: 388f80a7-3ce6-4de2-b232-a306cc8ad788
- Operating System: win32 v22.20.0
- Sandbox Environment: no sandbox
- Model Version: auto
- Memory Usage: 183.2 MB
Login information
No response
Anything else we need to know?
No response
What happened?
I'm getting this error when running tasks in Gemini CLI:
..\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsPtyAgent.js:93
throw new Error('Cannot resize a pty that has already exited');
^
Error: Cannot resize a pty that has already exited
at WindowsPtyAgent.resize (--\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsPtyAgent.js:93:19)
at WindowsTerminal. (--\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsTerminal.js:131:26)
at Object.run (..\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsTerminal.js:167:50)
at ..\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsTerminal.js:73:32
at Array.forEach ()
at Socket. (..\AppData\Roaming\npm\node_modules@google\gemini-cli\node_modules@lydell\node-pty\windowsTerminal.js:68:42)
at Socket.emit (node:events:531:35)
at addChunk (node:internal/streams/readable:561:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
at Readable.push (node:internal/streams/readable:392:5)
Node.js v22.20.0
What did you expect to happen?
bug fixed
Client information
Login information
No response
Anything else we need to know?
No response