When it cats a test file it asks permission to run every single line. This is really frustrating when there are a few hundred lines in the file. Allow always doesn't help as each line is different.
This is something that Rovo has decided to do on its own, it's not something I asked. Is there a way around it?
Thanks!
Ash
Hey @Ash McConnell
There was a similar question on the Rovo Dev's community space you might find useful: https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/When-Rovo-CLI-tool-is-running-multiline-cat-it-requires/td-p/3142127
Also, please use the Rovo Dev's community space for all Rovo Dev questions in the future :)
Kindest regards,
Jov
@Ash McConnell This is a known limitation of Rovo Dev’s command-approval model. Each dynamically generated bash command is treated as a separate execution, so when Rovo writes files line by line (for example using repeated cat or heredocs), it triggers a permission prompt for every variation—even if you select “Allow always.” This behavior is intentional today and command-string based, not task- or file-based. The most effective workaround is to explicitly instruct Rovo to generate the entire file in a single bash command using one heredoc, or to have it output the full file as plain text in chat and paste it manually. There’s currently no way to approve all commands for a task or disable this behavior globally, though it’s a known rough edge in Rovo Dev.
P.S. Meeeeeow. Hiissss.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.