What happened?
When the AI agent is currently thinking or executing tools in the background, entering shell mode by typing an exclamation mark (!) works as expected. The UI indicates that pressing Escape will leave shell mode.
However, pressing Escape does not actually exit shell mode. Instead, it seems to propagate the interrupt signal up, causing the ongoing background agent request to be cancelled ("Request cancelled"), while the input field remains stuck in shell mode.
What did you expect to happen?
Pressing Escape while in the ! shell input mode should clear the input field and return the user to the standard chat input mode, without cancelling the agent's ongoing background execution.
Client information
Client Information
CLI Version: 0.30.0
OS: darwin
Login information
N/A
Anything else we need to know?
Reproduction Steps:
- Send a complex request to the Gemini CLI that will take some time to process.
- While the agent is working, type
! to enter shell mode.
- Observe the UI prompt indicating to press Escape to exit.
- Press
Escape.
- Notice that the shell mode is not exited, but the agent's background task is terminated with a "Request cancelled" message.
What happened?
When the AI agent is currently thinking or executing tools in the background, entering shell mode by typing an exclamation mark (
!) works as expected. The UI indicates that pressingEscapewill leave shell mode.However, pressing
Escapedoes not actually exit shell mode. Instead, it seems to propagate the interrupt signal up, causing the ongoing background agent request to be cancelled ("Request cancelled"), while the input field remains stuck in shell mode.What did you expect to happen?
Pressing
Escapewhile in the!shell input mode should clear the input field and return the user to the standard chat input mode, without cancelling the agent's ongoing background execution.Client information
Client Information
Login information
N/A
Anything else we need to know?
Reproduction Steps:
!to enter shell mode.Escape.