Is there any way to keep ROVO DEV running while performing tasks?

[Evan]

Is there any way to keep ROVO DEV running while performing tasks? Don't ask me whether I allow or deny! This seems a little cumbersome.

[Ignacio Ampuero · Accepted solution]

Hey!

As far as I've used rovodev, just the first time you use a tool it asks for your confirmation.
You can allow permissions to "always" if you trust the agent, on the first time you call a specific tool.
There are 7 tools in total which are used, so with 7 confirmations it wont ask you again anymore. 

• open_files - Open and view multiple files at once 
• expand_code_chunks - Show specific functions, classes, or line ranges in detail
• create_file - Create new files with content 
• delete_file - Remove files from the workspace 
• find_and_replace_code - Search and replace text in files
• grep_file_content - Search for patterns across all files using regex
• bash - Execute shell commands (bash/powershell depending on platform)

But if you want it a temporal solution, just allow it to use them for the session.
You can switch or fork sessions with the /session command so you can have a "always use tools session"

This prompt uses all or mostly all the tools without leaving trace
"Create a demo python file, populate it with random functions with placeholder names, then expand key code sections, search and replace some placeholder names with another placeholder names, grep the file for a sample placeholder function name, run a bash command to echo the file contents and finally delete the file"

So you can allow all the tools in one go.

[Dr Valeri Colon _Connect Centric_]

Hi @Evan — great question!

As of now, Rovo Dev CLI doesn’t support background or persistent execution of agents without user prompts. It’s designed to ask for confirmation (like "Allow" or "Deny") to ensure safe and intentional action execution during testing.

There’s no built-in “always allow” or persistent session flag yet, but consider submitting a feature request.

[Evan]

OK, I got it.