Bug when pressing ctrl c in rovodev cli

[jules1]

When I press Ctrl C to interrupt the input of the neural network, my input is blocked and the input bar is simply shown, but I can’t write anything there. Repeated ctrl c does nothing and only restarting the console helps

[Dr Valeri Colon _Connect Centric_]

@jules1 welcome to the community. This looks less like a terminal issue and more like a Rovo Dev CLI input handling bug. A few users have seen similar behavior where Ctrl+C doesn’t properly release the input state, leaving the prompt unresponsive. Restarting the CLI is the only reliable workaround right now. If you can, capture your CLI version and report it via /feedback—this likely needs a fix on the Atlassian side rather than a local workaround.

[Himanshu Tiwary]

Hi @jules1 ,

This issue might be related to how the RovoDev CLI handles process interruptions. When you press Ctrl + C, the process might not be correctly releasing the terminal for further input, or the process might be in a state where it's not responding to interrupt signals.

Here are a few steps you can try to resolve this:

Check for Process Locking:

Sometimes, processes may get stuck or in a state where they don't respond to Ctrl + C. If that happens, try checking if the process is still running in the background using ps aux | grep rovo (or equivalent) to kill the process manually.

Use a Different Interrupt Key:

Some terminals use different combinations to interrupt, such as Ctrl + Z (to suspend) followed by bg (to resume in the background) or kill to terminate the process.

Use kill Command:

If Ctrl + C is not working, you can try identifying the process ID (PID) of the neural network input using ps or top and then use kill -9 <PID> to terminate it.

Check for Console Buffer Issues:

If the console is not accepting input after the interrupt, there could be a buffer issue. Restarting the console is a temporary workaround, but ensuring that there is no hanging input buffer might help.

If this persists, it might help to check the RovoDev CLI documentation or reach out to the support team for a potential bug fix or update.

Let me know if this helps or if you're still encountering the problem! Also an up vote will be appreciated