From reverse engineering
to building a real app

node -v
npm -v

npx.cmd rea-agents@latest setup --client codex
npx.cmd -y rea-agents@latest doctor --client codex --json

Codex Desktop does not require the codex command to be available on your PowerShell PATH. Optional native binary-analysis engines such as Ghidra are generally not necessary for examining Electron JavaScript.

Option 1 — Search with PowerShell

First check the common Xmind installation locations:

$paths = @(
  "$env:LOCALAPPDATA\Programs\Xmind\resources\app.asar"
  (Join-Path $env:ProgramFiles 'Xmind\resources\app.asar')
  (Join-Path ([Environment]::GetFolderPath('ProgramFilesX86')) 'Xmind\resources\app.asar')
)
$paths | Where-Object { Test-Path -LiteralPath $_ }

To find .asar files in common installation folders for other applications, use this command. The recursive scan may take a few minutes:

$roots = @(
  (Join-Path $env:LOCALAPPDATA 'Programs')
  $env:ProgramFiles
  ([Environment]::GetFolderPath('ProgramFilesX86'))
) | Where-Object { $_ -and (Test-Path -LiteralPath $_) } | Select-Object -Unique

foreach ($root in $roots) {
  Get-ChildItem -LiteralPath $root -Filter *.asar -File -Recurse -ErrorAction SilentlyContinue |
    Select-Object -ExpandProperty FullName
}

This prompt asks Codex to locate the target package and stop before any reverse engineering begins.

Option 2 — Use your browser's folder picker

On supported Chrome and Edge versions, you can explicitly choose an application folder. The browser can see matching filenames and relative paths, but cannot expose the absolute Windows drive path to this page.

Paths are not uploaded or stored. Editing either field instantly updates the prompts displayed below.

Find the underlying error

npx.cmd -y rea-agents@latest doctor --client codex --json

If REA tools are unavailable, first fully quit and restart Codex. If the problem persists, give Codex this diagnostic prompt: