Skip to content

Sentry v2.0.0 — Windows Stable

Choose a tag to compare

@Mert1026 Mert1026 released this 09 Nov 19:19
· 18 commits to main since this release
88eac22

Sentry v2.0.0 — Windows Stable

Major release. It adds staged QA, re-testing of earlier findings, project profiles, a library of 59 toolchain packs, ChatGPT as an opt-in agent, CLI parity and Bulgarian interface translations, and it removes the 1.x merge, verification and issue features.

Breaking change: database migration 7 is one-way. It drops the merge, verification, issue and retest tables and legacy retest runs. Full and Targeted runs, findings, evidence and exports are kept; issue and retest history is not. Back up your data before updating (step 4) and do not downgrade a migrated database to 1.x. Existing users: follow “Update an existing installation” below.

Supported installation: Windows 11 x64 + WSL2, Ubuntu preferred. This is an unsigned ZIP with online Linux bootstrap, not an MSI/MSIX or offline installer. Setup requires internet and the Linux prerequisites below. Provider credentials are configured in Desktop; provider usage charges are separate.

What's new

  • Staged QA flow with a frozen plan, per-check investigation, deepening, a hazard sweep and a report.
  • Re-test of earlier findings on the current revision, answered Passed, Not passed or Could not complete with the agent's reason.
  • Findings by revision and a project profile with per-agent notes.
  • Toolchains: 59 packs, project-pinned versions, custom add-ons and a per-run option to allow tool and SDK downloads.
  • ChatGPT as an opt-in agent next to OpenCode, DeepSeek and GLM.
  • CLI parity: run start --retest/--profile/--tools/--revision, project findings|profile|profile-build, toolchain status|install|remove.
  • Bulgarian translations including statuses and generated text; containment fixes for project copies and recovery.

Removed: run merge, issue and retest CLI commands and the merge, verification and issue pages.

1. WSL2 and Ubuntu

Run in PowerShell:

wsl.exe --list --verbose

If Ubuntu already exists, is initialized, and shows VERSION 2, keep it and continue. Otherwise run in PowerShell as Administrator:

wsl.exe --install -d Ubuntu

Restart if Windows requests it. Then use normal PowerShell:

wsl.exe --set-version Ubuntu 2
wsl.exe -d Ubuntu

Complete the Linux username/password prompts, then type exit to return to PowerShell. You do not need to remove WSL to install or update Sentry. See Microsoft WSL installation.

2. Linux prerequisites — commands from PowerShell

Skip this block if the selected Ubuntu already has Node >=22, pnpm 9.12.3, systemd user services, bubblewrap, and socat. Otherwise paste it into PowerShell. It installs packages inside Ubuntu using WSL root and the official NodeSource Node 22 repository when needed. If your distro has another name, change the Ubuntu selection in these blocks consistently.

& {
    $ErrorActionPreference = 'Stop'
    function Invoke-UbuntuRoot {
        param([string[]]$LinuxArguments)
        & wsl.exe -d Ubuntu -u root -- @LinuxArguments
        if ($LASTEXITCODE -ne 0) { throw 'Ubuntu prerequisite installation stopped. Resolve the error before continuing.' }
    }
    function Get-UbuntuVersion {
        param([string]$Tool)
        try {
            $version = & wsl.exe -d Ubuntu -- $Tool --version 2>$null
            if ($LASTEXITCODE -eq 0) { return ([string]$version).Trim() }
        } catch { }
        return ''
    }
    Invoke-UbuntuRoot -LinuxArguments @('apt-get', 'update')
    Invoke-UbuntuRoot -LinuxArguments @('apt-get', 'install', '-y', 'ca-certificates', 'curl', 'bubblewrap', 'socat', 'systemd', 'systemd-sysv')

    $nodeVersion = Get-UbuntuVersion -Tool 'node'
    if ($nodeVersion -notmatch '^v(\d+)\.' -or [int]$Matches[1] -lt 22) {
        Invoke-UbuntuRoot -LinuxArguments @('install', '-d', '-m', '700', '/root/.cache/sentry-bootstrap')
        Invoke-UbuntuRoot -LinuxArguments @('curl', '-fsSL', 'https://deb.nodesource.com/setup_22.x', '-o', '/root/.cache/sentry-bootstrap/node22.sh')
        Invoke-UbuntuRoot -LinuxArguments @('bash', '/root/.cache/sentry-bootstrap/node22.sh')
        Invoke-UbuntuRoot -LinuxArguments @('apt-get', 'install', '-y', 'nodejs')
    }
    $pnpmVersion = Get-UbuntuVersion -Tool 'pnpm'
    if ($pnpmVersion -cne '9.12.3') {
        Invoke-UbuntuRoot -LinuxArguments @('npm', 'install', '--global', 'pnpm@9.12.3')
    }
    $nodeVersion = Get-UbuntuVersion -Tool 'node'
    if ($nodeVersion -notmatch '^v(\d+)\.' -or [int]$Matches[1] -lt 22 -or
        (Get-UbuntuVersion -Tool 'pnpm') -cne '9.12.3') {
        throw 'Node >=22 or pnpm 9.12.3 is unavailable inside Ubuntu. Installation stopped.'
    }
    & wsl.exe -d Ubuntu -- systemctl --user show-environment
    if ($LASTEXITCODE -ne 0) {
        throw 'Ubuntu systemd user services are unavailable. Follow the systemd guidance below, then rerun this block.'
    }
    Write-Host 'Ubuntu prerequisites installed. Continue with Install Sentry below.'
}

If systemd user services are unavailable, follow Microsoft systemd guidance, preserving existing WSL configuration, and rerun the check.

3. Fresh install — download, verify, setup, and open

Paste the entire block into normal PowerShell from any folder, including System32. It automatically downloads the exact ZIP and checksum, verifies the pinned ZIP hash, manifest hash, full source identity, and every distribution file before executing the launcher, extracts into a separate version/source directory, sets up the matching runtime, provisions the pinned tools, and opens Desktop. A failure stops subsequent steps. Existing matching installation files are verified and reused; a tampered directory is refused.

& {
    $ErrorActionPreference = 'Stop'
    $name = 'sentry-2.0.0-88eac224c735-windows-x64'
    $expectedHash = 'dc30a28aa2c256edc0a172a267d5c800b8dbb2578e105d37ea45e42cc7b6361e'
    $expectedManifest = '7aa9da1773b14144374de91ce902de96db3fd75eb2f2f7ad6fa6d9836169c60d'
    $source = '88eac224c7357028b2d2aa440dbcdefd984f0d58'
    $download = Join-Path $env:USERPROFILE 'Downloads\Sentry-v2.0.0'
    $destination = Join-Path $env:LOCALAPPDATA 'Sentry\releases'
    $installation = Join-Path $destination $name
    $zip = Join-Path $download ($name + '.zip')
    $checksum = $zip + '.sha256'
    $url = 'https://github.com/Mert1026/Sentry/releases/download/v2.0.0/'

    New-Item -ItemType Directory -Path $download, $destination -Force | Out-Null
    Write-Host 'Downloading the official ZIP and checksum...'
    Invoke-WebRequest -UseBasicParsing -Uri ($url + $name + '.zip') -OutFile $zip
    Invoke-WebRequest -UseBasicParsing -Uri ($url + $name + '.zip.sha256') -OutFile $checksum

    if (-not (Test-Path -LiteralPath $zip -PathType Leaf) -or
        -not (Test-Path -LiteralPath $checksum -PathType Leaf)) {
        throw 'The ZIP or checksum file is missing. Installation stopped.'
    }
    $sidecarHash = ((Get-Content -LiteralPath $checksum -Raw).Trim() -split '\s+')[0]
    $actualHash = (Get-FileHash -LiteralPath $zip -Algorithm SHA256).Hash
    if ($sidecarHash -notmatch '^[a-fA-F0-9]{64}$' -or
        $sidecarHash -ine $expectedHash -or $actualHash -ine $expectedHash) {
        throw 'Checksum verification failed. Installation stopped.'
    }

    if (-not (Test-Path -LiteralPath $installation)) {
        Expand-Archive -LiteralPath $zip -DestinationPath $destination
    }
    $manifestPath = Join-Path $installation 'distribution.json'
    if ((Get-FileHash -LiteralPath $manifestPath -Algorithm SHA256).Hash -ine $expectedManifest) {
        throw 'Distribution manifest mismatch. Installation stopped.'
    }
    $manifest = Get-Content -LiteralPath $manifestPath -Raw | ConvertFrom-Json
    if ($manifest.sourceCommit -cne $source -or $manifest.version -cne '2.0.0' -or
        $manifest.runtimeProtocol -ne 1 -or $manifest.targetPlatform -cne 'windows-x64') {
        throw 'Release identity mismatch. Installation stopped.'
    }
    foreach ($file in $manifest.files.PSObject.Properties) {
        $path = Join-Path $installation $file.Name
        if ((Get-FileHash -LiteralPath $path -Algorithm SHA256).Hash -ine $file.Value) {
            throw ('Distribution file mismatch: ' + $file.Name)
        }
    }
    Write-Host 'Approved checksum, manifest, source identity and files verified.'

    $launcher = Join-Path $installation 'sentry.ps1'
    foreach ($step in @('version', 'setup', 'tools', 'open')) {
        Write-Host ('Sentry: ' + $step)
        if ($step -in @('setup', 'tools')) {
            & powershell.exe -NoProfile -ExecutionPolicy Bypass -File $launcher $step -Distro Ubuntu
        } else {
            & powershell.exe -NoProfile -ExecutionPolicy Bypass -File $launcher $step
        }
        if ($LASTEXITCODE -ne 0) {
            throw ('Sentry ' + $step + ' stopped. Resolve the reported error, then paste this block again.')
        }
    }
    Write-Host ('Installed at: ' + $installation)
    Write-Host 'Check Environment is Connected. Provider requests can incur charges.'
    $env:Path += ";$env:LOCALAPPDATA\Sentry\bin"
    Write-Host "Use sentry open, sentry status, sentry doctor or sentry version from any folder."
}

Keep the installed directory under %LOCALAPPDATA%\Sentry\releases; it is the application. Configure Settings → Providers, then check Environment is Connected and provider readiness. Installation/readiness checks do not start paid QA. A capabilities handshake alone does not establish runtime/provider readiness.

4. Update an existing installation — 1.x to v2.0.0

This update migrates your database one way: issue, retest and merge history from 1.x is dropped, and the migrated database cannot be used by 1.x. The backup below is your only way back. Run it first and keep it until you have checked your own history.

If your older installation has no registered sentry command, replace & sentry stop in the backup block with & powershell.exe -NoProfile -ExecutionPolicy Bypass -File "C:\path\to\previous-installation\sentry.ps1" stop, using its actual absolute path.

  1. Finish active QA/retests or explicitly cancel them, and wait until they settle. Check Environment for your actual distro/data root. Keep the previous matched archive/runtime.
  2. In PowerShell, run the stopped-backup block below. It uses the standard current-user profile/data locations; change $distro and $linuxData to the actual values if customized. Allow enough space for a full backup plus the new archive and runtime. You can select another backup drive by changing $backup.
  3. After backup succeeds, run the same complete v2.0.0 install block in step 3. It selects the new archive through setup and command registration. Do not extract over the old version or delete WSL/user data.
  4. Open a new PowerShell window, run the verification commands below, and inspect existing projects, completed history/results, exports, and provider settings in Desktop. Retain the stopped backup and previous matched installation until satisfied.
& {
    $ErrorActionPreference = 'Stop'
    # Use the distro and absolute data root shown by Sentry Environment.
    $distro = 'Ubuntu'
    $linuxData = (& wsl.exe -d $distro -- sh -c 'printf "%s/.local/share/sentry" "$HOME"').Trim()
    if ($LASTEXITCODE -ne 0 -or -not $linuxData.StartsWith('/')) { throw 'Cannot determine Linux data root.' }
    # If Environment shows a custom root, replace $linuxData above with that root.
    & sentry stop
    if ($LASTEXITCODE -ne 0) { throw 'Sentry must stop before backup.' }
    & wsl.exe -d $distro -- sh -c 'if pgrep -f "[a]pps/runtime/dist/host.js" >/dev/null; then exit 1; fi'
    if ($LASTEXITCODE -ne 0) { throw 'A runtime is still active. Close every Sentry instance first.' }
    $backup = Join-Path ([Environment]::GetFolderPath('MyDocuments')) ('Sentry Backup ' + (Get-Date -Format 'yyyyMMdd-HHmmss'))
    New-Item -ItemType Directory -Path $backup -ErrorAction Stop | Out-Null
    $linuxBackup = (& wsl.exe -d $distro -- wslpath -u ($backup.Replace('\', '/'))).Trim()
    if ($LASTEXITCODE -ne 0 -or -not $linuxBackup.StartsWith('/')) { throw 'Backup path translation failed.' }
    & wsl.exe -d $distro -- tar -czf ($linuxBackup + '/runtime-data.tar.gz') -C $linuxData .
    if ($LASTEXITCODE -ne 0) { throw 'Linux backup failed. Do not upgrade yet.' }
    & wsl.exe -d $distro -- tar -tzf ($linuxBackup + '/runtime-data.tar.gz') > $null
    if ($LASTEXITCODE -ne 0) { throw 'Linux backup verification failed.' }
    $profile = Join-Path $env:APPDATA '@qa\desktop'
    if (-not (Test-Path -LiteralPath $profile -PathType Container)) { throw 'Desktop profile not found; check the actual profile location.' }
    Copy-Item -LiteralPath $profile -Destination (Join-Path $backup 'desktop-profile') -Recurse -ErrorAction Stop
    foreach ($part in @('launcher', 'bin')) {
        $path = Join-Path $env:LOCALAPPDATA ('Sentry\' + $part)
        if (Test-Path -LiteralPath $path) { Copy-Item -LiteralPath $path -Destination (Join-Path $backup $part) -Recurse -ErrorAction Stop }
    }
    Write-Host ('Stopped backup saved at: ' + $backup)
}

After installing:

sentry version
sentry status
sentry doctor
sentry open
sentry cli capabilities --json
sentry cli project list --json
sentry cli agent list --json

Version must be 2.0.0, source must match the identity below, and Environment must be Connected. Setup is designed to keep canonical data and encrypted provider settings, but this release's update was only exercised on one machine that already held data from a development build, not on a published 1.0.2 installation. Check your own projects, history and provider settings after updating. A stopped backup contains private project data and encrypted credentials: keep it private. Binary rollback does not reverse database migration; restore a compatible stopped data/profile backup with its matching runtime and Desktop according to the recovery policy.

5. Everyday launcher commands

These are individual command examples. Once setup registers Sentry, they work from any folder in a new PowerShell or Command Prompt window.

Command Purpose
sentry open Open Desktop; required before operational CLI commands.
sentry stop Request graceful shutdown; wait for active work first.
sentry version Display installed archive version and full source identity.
sentry status Show archive identity/process summary; use Environment for runtime readiness.
sentry doctor Show diagnostics guidance without paid requests.
sentry setup -Distro Ubuntu Install/repair this archive's matching runtime; requires idle components.
sentry tools -Distro Ubuntu Provision pinned provider tools; requires idle components.
sentry register-command Register this selected archive's command after moving its directory.
sentry help Show launcher commands.
sentry cli --help Show operational CLI syntax.

If an already-open PowerShell cannot find the command:

$env:Path += ";$env:LOCALAPPDATA\Sentry\bin"
sentry version
sentry open

If you move the archive, invoke its full launcher path to register the new location:

& powershell.exe -NoProfile -ExecutionPolicy Bypass -File (Join-Path $env:LOCALAPPDATA "Sentry\releases\sentry-2.0.0-88eac224c735-windows-x64\sentry.ps1") register-command

Adjust that path to where you moved it. sentry update deliberately refuses in pinned archives; updates use the new release's verified installation block.

6. CLI examples — project import and readiness

The following are individual examples, not a script to execute top to bottom. Replace proj_ID, run_ID, rev_ID, and find_ID with actual IDs returned by commands. Replace source paths with existing folders. Keep Desktop open; credentials stay in Settings → Providers and are never supplied to the CLI.

sentry open
sentry cli capabilities --json
sentry cli agent list --json
sentry cli agent doctor opencode --json
sentry cli agent doctor deepseek --json
sentry cli agent doctor glm --json
sentry cli project add "C:\Projects\SampleApp" --json
sentry cli project list --json
sentry cli project show proj_ID --json
sentry cli project revisions proj_ID --json
sentry cli project doctor proj_ID --json
sentry cli project update proj_ID "C:\Projects\SampleApp" --json

Project add/update returns data.projectId and data.revisionId. Import copies files into managed WSL storage and creates an immutable revision; the source folder remains yours. Generated caches are skipped, but .gitignore is not an import policy. Large imports may require multiple copies; both Windows backing-drive capacity and Linux free space matter. Removing managed projects does not immediately shrink WSL's virtual disk; Desktop's reclamation action is separate OS maintenance.

7. CLI examples — Full QA, Targeted QA, and polling

Choose one start example. These execute real providers and may incur charges. --agents selects the provider set. Configure them first. Full scans the project; Targeted limits included relative paths. --instructions supplies additional run guidance.

sentry cli run start proj_ID --mode full --agents opencode,deepseek,glm --json
sentry cli run start proj_ID --mode targeted --agents deepseek --paths src/auth,src/api --json
sentry cli run start proj_ID --mode full --agents opencode --instructions "Check input validation" --wait --timeout-ms 1800000 --json
sentry cli run list proj_ID --json
sentry cli run show run_ID --json
sentry cli run status run_ID --json

Start is asynchronous by default: retain data.runId and data.operationId, then poll status. The runtime owns execution after the CLI exits. --wait observes the run until terminal status. --timeout-ms sets that run's time window (1000–43200000 ms, up to 12 hours); omitted keeps the default of 3 hours. An uncertain start response may mean the paid run already exists: inspect run list/Desktop before any retry. Do not blindly retry RUN_MAY_HAVE_STARTED. Closing a CLI process does not cancel a canonical run.

8. CLI examples — results, JSON/log exports, cancellation, deletion

Retrieve results after a terminal status. Exports use the canonical runtime bytes and write the chosen local output file; create its parent directory first.

$reports = Join-Path ([Environment]::GetFolderPath("MyDocuments")) "Sentry Reports"
New-Item -ItemType Directory -Path $reports -Force | Out-Null
sentry cli run result run_ID --json
sentry cli run export run_ID --format json --out (Join-Path $reports "result.json") --json
sentry cli run export run_ID --format log --out (Join-Path $reports "result.log") --json

Use these only when you intend to cancel/remove the selected item:

sentry cli run cancel run_ID --json
sentry cli project delete proj_ID --yes --json

Deletion permanently removes Sentry-managed project data and history while preserving the original source folder. Active-work safety gates still apply. Cancellation is explicit and separate from deletion.

9. CLI examples — findings by revision, re-test, profiles and toolchains

These commands list what each agent reported per revision, re-test earlier findings on the current revision, read or build project profiles and manage toolchains. Re-test and profile building use real providers and may incur charges. The 1.x issue, retest and run merge commands no longer exist.

sentry cli project findings proj_ID --json
sentry cli run start proj_ID --retest run_ID:find_ID --wait --json
sentry cli run start proj_ID --retest run_ID:find_ID,run_ID:find_ID --retest-with all --agents opencode,deepseek --json
sentry cli run start proj_ID --mode full --agents chatgpt --profile --tools --json
sentry cli project profile proj_ID --json
sentry cli project profile-build proj_ID --json
sentry cli toolchain status --json
sentry cli toolchain install pack_ID version --json

A re-test takes up to 12 findings. Each finding is answered PASSED (resolved), NOT PASSED (still there) or COULD NOT COMPLETE with the agent's reason; --json carries verdict as no_longer_reproduces, still_reproduces or cannot_tell. A re-test stores no findings of its own. ChatGPT is opt-in and is not part of the default agents.

10. Automation contract and errors

Always use --json for automation: stdout contains one JSON envelope; stderr contains human diagnostics. Parse stdout and branch on ok / error.code, never message wording. Capture the process exit status before running another command. run result returns canonical structured content inside data.result.

$responseText = sentry cli project list --json
$exitCode = $LASTEXITCODE
$response = $responseText | ConvertFrom-Json
if ($exitCode -ne 0 -or -not $response.ok) { throw ($response.error.code + ": " + $response.error.message) }
$response.data.projects

Optional informational client identity:

$env:SENTRY_CLI_CLIENT_NAME = "Automation client"
$env:SENTRY_CLI_CLIENT_VERSION = "1.0.0"
sentry cli capabilities --json
Exit Meaning
0 Command success.
1 Internal/transport/protocol failure, including Desktop not running.
2 Invalid arguments or forbidden command.
3 Project/run/finding/source not found.
4 Conflict/retryable state, uncertain start, or response/export size limit.
5 Findings present for applicable completed execution commands.
6 Execution/provider readiness failure.
7 Partial execution.
8 Cancelled execution.

An accepted asynchronous start is not proof the QA finished successfully. Use run status, run show, and run result. Common codes: SENTRY_DESKTOP_NOT_RUNNING → open Desktop; PROVIDER_NOT_READY → Settings/Environment; RUN_NOT_COMPLETE → poll; ACTIVE_RUN_EXISTS/PROJECT_LOCKED → settle active work; EXPORT_TOO_LARGE → canonical export exceeds the transport limit. JSON is never silently truncated. The canonical raw export limit is 6,000,000 bytes.

Production uses the Desktop named-pipe broker and the shared WSL runtime. It never creates a separate database and never selects direct/development transport from an environment override. Development simulation and the retired merge, verifier, issue and retest commands are unavailable in the packaged CLI. Client names and pipe scope are informational, not authentication; the documented trust boundary includes same-user processes and does not claim a custom current-user-only pipe ACL. See the complete CLI contract and command reference, also included as CLI.md in the ZIP.

Artifact identity and verification

  • Version: 2.0.0; target: windows-x64; runtime protocol: 1.
  • Source: 88eac224c7357028b2d2aa440dbcdefd984f0d58.
  • Git tree: daf4f9b4925f8595f40c3c0c2a798d87e7fe8378.
  • ZIP: sentry-2.0.0-88eac224c735-windows-x64.zip.
  • ZIP SHA256: dc30a28aa2c256edc0a172a267d5c800b8dbb2578e105d37ea45e42cc7b6361e.
  • Manifest SHA256: 7aa9da1773b14144374de91ce902de96db3fd75eb2f2f7ad6fa6d9836169c60d.
  • Complete verified manifest inventory: 335 files, including the production CLI and local guides.

Verification covers the hosted quality, launcher and Windows archive jobs on the release pull request, a clean build of this exact source, ZIP extraction and manifest verification, and a prepared-host check on one Windows 11 + WSL2 (Ubuntu) machine: setup of the matching 2.0.0 Linux runtime from the extracted archive, pinned tool installation, Desktop launch, and CLI capabilities and project list against the running Desktop with existing projects and runs intact. This is a prepared Windows/WSL host, not clean-machine provisioning. Updating from a published 1.0.2 installation was not separately exercised, and no paid-provider campaign or elevated disk compaction was run for this release. No old tag or release asset is replaced.

Runtime protocol 1, provider/model/tool pins (OpenCode 1.18.32, DeepSeek SDK 0.1.5-rc.2, Claude Code 2.1.270), credential encryption boundaries and revision hashes are unchanged; database migration 7 is not. Native Linux Desktop, macOS, signed installers, offline bootstrap and automatic updating remain outside this release.

See v2.0.0 notes and the installation/recovery guide. Included INSTALL.md and CLI.md link to this exact source.