Troubleshoot problems with Rovo Dev CLI
Rovo Dev CLI is currently in beta
バグを報告
If you find something isn’t working in Rovo Dev CLI, report a bug.
Rovo Dev CLI stores logs in <user home dir>/.rovodev/rovodev.log
. It’s really helpful to include details from your log file when reporting a bug.
既知の問題
While Rovo Dev CLI is in beta, there are some bugs and issues we’re tracking.
Issue | 操作 |
---|---|
Error message “Failed to generate an LLM response” or “An unexpected error occurred, exiting” | Generic error message. If the problem persists, check the log file at |
Rovo Dev can make code changes without being asked to do so | Specify “Don’t make code changes” in your prompt. |
Rovo Dev CLI becomes unresponsive when running in a large codebase | Large codebases can cause problems for Rovo Dev. Try running Rovo Dev in sub-directories with fewer files. |
Cannot enter '@' symbol in username, which leads to error message “Invalid token during auth, Authentication failed” (Windows PowerShell) | Try to authenticate in Command Line instead of PowerShell. Or copy & paste the unscoped API token in a text file (e.g. token.txt) and reference the file in your auth command: |
Error message: “Failed to execute command” (Windows PowerShell) | Make sure user account has permissions to |
この内容はお役に立ちましたか?