Session or Environment Issues: Sometimes, long-running sessions or environment-specific issues (like encoding or permissions) can cause the CLI to hang.
Platform-Specific Bugs: There have been fixes for PowerShell reliability and session encoding on Windows in recent releases.
Troubleshooting steps to help you!
Check the Log File: The CLI writes logs to ~/.rovodev/rovodev.log. Reviewing this file can provide clues about what’s causing the hang. You can open it with:
acli rovodev log
Try a Smaller Directory: If you’re running the CLI in a large repo, try switching to a smaller subfolder and running the command again.
Update to the Latest Version: Ensure both ACLI and Rovo Dev CLI are up to date. Many stability and bug fixes have been released recently.
Restart the CLI: If a session hangs, exit and restart the CLI. Sometimes, a fresh session resolves the issue.
Check for Platform-Specific Issues: If using Windows PowerShell, try running the CLI in a standard Command Prompt or another terminal.