Cannot run acli rovodev run on Japanese Windows: cp932 codec can't decode byte 0x94 (want to avoid s

[Miya]

Hi,

I’m trying to run Rovo Dev using Atlassian CLI (acli) on Windows, but I’m consistently blocked by a cp932 decoding error.

Environment:

- OS: Windows 11 (Japanese locale)

- Shell: PowerShell

- Atlassian CLI: latest Windows binary (acli.exe)

- Install method: official standalone binary

- Locale / encoding: default Japanese Windows (cp932)

- Constraint: I would like to avoid switching the OS or PowerShell global encoding to UTF‑8,

  because this machine is also used for other legacy systems that depend on cp932.

Command:

acli.exe rovodev run
Error:

Failed to start Rovo Dev CLI: 'cp932' codec can't decode byte 0x94 in position 3189: illegal multibyte sequence Error handling beta customer site selection.

What I’ve tried:
- Reinstalling acli.exe from the official Atlassian site
- Removing the following directories completely:
- %USERPROFILE%\.rovodev
- %LOCALAPPDATA%\rovodev
- %USERPROFILE%\.atlassian
- %USERPROFILE%\.acli
- Running with Python UTF‑8 enabled for the session:
         $env:PYTHONUTF8 = "1" acli.exe rovodev run

- Running from both PowerShell and a clean session

- Confirmed that the error happens during “beta customer site selection”, before Rovo Dev actually starts Even after clearing all Rovo Dev / Atlassian-related configs, the same cp932 decoding error occurs. It looks like Rovo Dev (or acli) is reading some config or metadata using the OS default encoding instead of UTF‑8, and fails before any user interaction.

My question:

   - Is there a supported way to run Rovo Dev / acli on Japanese Windows without switching the entire OS or PowerShell to UTF‑8?

   - Is there a known workaround to force UTF‑8 decoding only for Rovo Dev / acli internals?   

   - Or is this a known limitation / bug when using Rovo Dev on non‑UTF‑8 Windows locales? Any guidance or confirmation would be greatly appreciated. If needed, I can also share more logs or test a patched build. Thanks.

[Dr Valeri Colon _Connect Centric_]

@Miya welcome to the community.  This looks like a Windows encoding issue, not something you did wrong. Rovo Dev/ACLI doesn’t handle cp932 well in some cases, especially during startup. Right now there’s no clean way to force UTF-8 just for the CLI without changing system settings. I’d treat this as a bug—best next step is to raise it with Atlassian Support with your setup and error details.