Chat On Steroids 2.0.1

Windows installers for both architectures are attached below. Download the one that matches your
PC, then reload the browser extension because the app and extension are versioned together.

• Chat-On-Steroids-Setup-x64.exe — Intel/AMD Windows PCs
• Chat-On-Steroids-Setup-arm64.exe — Windows on Arm
• Chat-On-Steroids-Extension.zip — standalone companion extension
• SHA256SUMS.txt — SHA-256 checksums for all release artifacts

2.0.1

2.0.1 is a hardening release after 2.0.0. The main changes are reusable worker conversations,
stronger crash/restart recovery, more reliable browser turn completion, faster bounded Computer Use
paths, and a large set of session, renderer, command and lifecycle fixes found during adversarial
testing.

Workers and browser recovery

• Workers now sleep and can be revived in the same ChatGPT conversation instead of being treated as
  disposable one-shot chats. Sleeping frees the worker slot; waking requires a free slot and reuses
  the exact existing tab when possible or reopens the stored conversation when necessary.
• Worker revival is durable across app/browser restarts and uses explicit claim/lease/ACK ownership so
  browser delivery and MCP liveness cannot duplicate or steal the same wake.
• Bridge recovery is fenced until durable command state is reconstructed. Restore now plans locally,
  reconciles broker state, performs the durable rewrite, and only then publishes commands and timers.
• Stale worker inbox rows, detached-worker cleanup and final-report delivery were tightened so a later
  wake cannot reinject already-finished work or lose the worker's terminal report.

Recording, Goal and session recovery

• Final assistant responses are detected more reliably in throttled/background tabs, including the
  conservative fallback used when ChatGPT's Fiber data omits a terminal marker.
• Session metadata is reconciled against newer durable event/message history after crashes, including
  read-only history/listing paths that must not accidentally mark an old session live.
• Retention runs throughout a long-lived app process and scans the complete process catalog rather than
  an arbitrary first 5,000 session folders.
• A transient sessions-directory EBUSY, EACCES or I/O failure no longer gets cached as an
  authoritative empty catalog for the rest of the process.

Commands and Computer Use

• exec_command supports related cmds batches in one shell session with bounded output and labeled
  per-command results. Batch framing now carries a fresh random id, so command output cannot imitate
  the wrapper's own exit markers and corrupt failure classification.
• Windows command startup honors explicit short yields, avoids loading the PowerShell profile by
  default, and caches stable shell/toolchain discovery work.
• Desktop automation keeps immutable recent frames/UIA snapshots, bounds large outputs and batches,
  improves helper lifecycle/retirement, and removes several fixed waits from common paths.

UI, setup and lifecycle

• Browser authorization and current browser presence are shown separately. Explicit app-side browser
  Disconnect can no longer be silently undone by the extension.
• Setup requires an approved filesystem root only when the enabled Core capabilities actually need one.
• The main window now fits smaller/DPI-scaled Windows work areas and can be resized/maximized.
• Session history is paged, live detail refresh uses bounded deltas, and root rename/settings fields no
  longer lose in-progress user edits to unrelated state pushes.
• Final application shutdown always reaches quit, and accepted MCP mutations are drained gracefully on
  ordinary disconnect rather than being force-cut by the final-shutdown deadline.

The detailed 2026-08-25 engineering log is in docs/bughunt-2026-08-25.md.

Beta despite the version number. Behaviour may still change between releases.