[BUG] 对话报错

[Yang-strive]

Problem (one or two sentences)

当我发送对话的时候，会报错

Context (who is affected and when)

发送对话的时候就会看到，就是说根本不能对话

Reproduction steps

1. 对话框输入任何内容，点击发送
2. 就会出来错误信息：

API流式传输失败
$0.0000
API请求失败
Command failed with ENOENT: powershell (Get-CimInstance -ClassName Win32_OperatingSystem).caption
spawnSync powershell ENOENT

3. 将powershell (Get-CimInstance -ClassName Win32_OperatingSystem).caption命令拿到cmd窗口运行也是会报错：

powershell (Get-CimInstance -ClassName Win32_OperatingSystem).caption
Microsoft : 无法将“Microsoft”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写，如果包括路径，请确
保路径正确，然后再试一次。
所在位置 行:1 字符: 1

• Microsoft Windows 10 家庭中文版

•   + CategoryInfo          : ObjectNotFound: (Microsoft:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
  
  

Expected result

对话报错

Actual result

对话报错

Variations tried (optional)

No response

App Version

3.36.2

API Provider (optional)

None

Model Used (optional)

N/A

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

API流式传输失败
$0.0000
API请求失败
Command failed with ENOENT: powershell (Get-CimInstance -ClassName Win32_OperatingSystem).caption
spawnSync powershell ENOENT

[roomote]

I'm looking into this issue. The error indicates that PowerShell is failing to execute on Windows, specifically when trying to get the OS caption. I'll explore the codebase to understand how this command is being used and propose a fix.

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause

The error occurs because the os-name package (v6.0.0) uses windows-release internally, which attempts to execute a PowerShell command to get the Windows OS caption. The command fails with ENOENT when PowerShell is not available or not in the system PATH.

Proposed Solution

1. Add error handling in system-info.ts: Wrap the osName() call in a try-catch block to gracefully handle failures
2. Provide a fallback: When osName() fails, fall back to using Node's built-in os.platform() and os.release() to construct a basic OS description
3. Ensure the app continues to work: The OS name is just informational metadata, so a failure to get the detailed name shouldn't break the entire application

Implementation Details

I will modify src/core/prompts/sections/system-info.ts to:

// Try to get detailed OS name, fall back to basic info if it fails
let osInfo: string;
try {
  osInfo = osName();
} catch (error) {
  // Fallback when os-name fails (e.g., PowerShell not available on Windows)
  const platform = os.platform();
  const release = os.release();
  osInfo = `${platform} ${release}`;
}

This approach will:

• Fix the immediate issue for users without PowerShell in their PATH
• Maintain the detailed OS information for users where it works
• Ensure the application remains functional regardless of system configuration

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[Yang-strive]

同意

[mrubens]

@roomote go for it

[roomote]

I've seen your comment and will explore a potential fix. I'll open a PR to share progress.

[roomote]

Opened a PR with my attempt at addressing this. Feedback welcome! #9897