I received a prompt: "To resume your session, restart Rovo Dev CLI with the --restore flag. ". But I don't know how to join this flag. I ran: "acli rovodev --restore" and reported the same error when I ran: "acli rovodev run --restore". So, how should I add this flag?
Hi @任飞翔 ,
I'm just moving this to the appropriate product/app group here on the forum.
Hopefully, Rovo experts can jump in to help out.
Cheers,
Tobi
You're awesome @Tomislav Tobijas thank you for keeping the forum organized (I can never seem to move posts very well). The Dev Cli Beta also has a community https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/Introducing-Rovo-Dev-CLI-AI-Powered-Development-in-your-terminal/ba-p/3043623
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oo nice! Seems I missed that one 👀
Being a member of so many groups, it's hard to keep track of 😅
Cheers for pointing it out @Dr Valeri Colon _Connect Centric_ !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just deleted the .agent.md file that made by rovodev generate. Although this solves the problem, it should obviously not be handled so simply. Because this file is useful to me. This includes the "UTF-8 encoding" encoding problem.
For Chinese window11, the default encoding of cmd and ps windows is "GB2132" or similar "GBK", which is not very certain. Why doesn't Microsoft directly use "UTF-8" encoding? I guess it's because of compatibility issues. Many early Chinese programs used "GB2132" encoding. If the system encoding is directly modified to "UTF-8", it will cause a lot of garbled characters to appear in many Chinese software, which is unrecognizable.
So, now, the problem is that many users cannot force "UTF-8" to be used directly.
Therefore, I left a description of this problem in .agent.md, asking rovodev not to try to run the ps1 file directly, because the encoding is different, and I will inevitably report an error. Instead, I run a .py file temporarily written in a few sections to perform debugging.
Then after deleting it, I have to chat with rovoder for a long time every time before starting other things.
In fact, the root of the problem is the encoding problem. The "UTF-8" problem is a bit strange. Logically speaking, the PowerShell command generally does not conflict with the encoding, but it reports an error every time and cannot be understood.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @任飞翔 — the correct usage is: acli rovodev run --restore
. If that still fails, the session file may be corrupted or affected by encoding issues. You're right—Windows defaulting to GBK causes UTF-8 problems. For now, set PYTHONUTF8=1
before running ACLI or use Windows Terminal with UTF-8 as default.
For more updates visit the Dev CLI Beta Community or consider submitting a support ticket.
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.