Skip to content

Releases

Codex Decision 0.17.4

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 18 Nov 13:38
1f6101c

Decision runs with Codex on Windows and Remote WSL. Each workspace host keeps its own plugin data.

  • Qualifies Codex 26.1111.21308 and preserves the reviewed older patch profiles.
  • Tolerates unrelated links in the native Windows Codex plugin directory while securing Decision state.
  • Keeps the hook available on unreviewed Codex builds and reports composer compatibility separately.
  • Includes the verified integrated VSIX, standalone ZIP, and SHA-256 checksums.

Codex Decision 0.17.2

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 14 Nov 19:42

Custom-provider settings now pass response-model and CA-certificate fields through the Codex bridge. Automatic integration honors the configured data directory. Rust and JavaScript agree on built-in credential parsing, and credential writes use bounded Windows atomic-replacement retries. Package verification now checks embedded Linux and Windows versions.

The repository no longer needs Nx or an npm dependency installation. Native Cargo, Node, and Python runners retain conservative function selection and complete boundary checks. Retired dual-score replay, unused output fields, the cachebust command, an old bridge alias, dated test defaults, and permissive stress compatibility paths are removed. Development caches now use .cache/, and documentation and the bundled skill describe the current behavior.

Compatible Rust security dependencies are updated. The final RustSec scan reports no advisories or warnings. Historical user records, configuration migrations, active hook cache paths, credentials, and runtime recovery files remain supported.

Validation includes Linux and native Windows suites, Clippy, complete function-coverage collection, Chromium smoke and quality checks, interruption and publication recovery, both provider stress protocols, and exact ZIP/VSIX source verification. The synthetic matrix completed 618 cases and 900 requests with no required lines lost. The final packaged Windows installer and patch lifecycle passed against Codex 26.1007.21434.

Install the matching VSIX, then reload VS Code when convenient. Start a new local thread and review changed hooks in /hooks when prompted. Existing threads retain their recorded cache paths.

SHA-256:

99ccbb59ecb72a55e33409eeb1cffa33f28c83a74ff8a910f71725b90076c5db  codex-decision-0.17.2.zip
27c3a5d9c0bc3d79e651cafce301fdd62ad08c84fc5567779e5ea3e71882f771  codex-decision-0.17.2.vsix

Codex Decision 0.17.1

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 12 Nov 07:45

Fix installation-lock failures when Chime, Decision, and multiple VS Code windows start together.

Windows and Linux installers now wait for a complete bounded companion transaction. The parent deadline includes both lock acquisition and the CLI commands. This prevents the previous 15-second waits from exhausting every retry while a 90-second Codex command still holds the lock. Repeated interrupted Linux lock acquisition also reaches its deadline.

Validation: complete relevant Python and Node suites, native Windows installation and concurrent reuse, packaged PowerShell hook launchers, real Codex patch apply/restore, Chromium checks, and the successful Verify workflow. Regression cases cover slow owners and bounded expiry.

Install the VSIX and reload VS Code. Update Chime to 0.3.3 as well. Existing identities, data, trust records, active hook caches, and rollback files remain preserved. SHA-256 hashes are in SHA256SUMS.txt.

Codex Decision 0.17.0

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 11 Nov 13:14

Codex Decision 0.17.0 adds advisory workflows around the existing output filter and consolidates the documentation around current application behavior.

  • Compare observed Monitor/Filter model token usage with separate provider request and cache measurements. Reports preserve missing-data and delivery uncertainty.
  • Register native MCP tools for context ranking, failure triage, and completion verification. Ranking preserves every exact original candidate.
  • Use structured evidence and optional shared-reference prompt cache boundaries for advisory requests. Validate complete Score and Choice distributions.
  • Publish original failure evidence with advisory cause and priority in VS Code Test Explorer. Function coverage remains responsible for test selection.
  • Enable optional completion verification in Observe or Enforce mode. Enforce permits one continuation for a contradicted claim only with complete, current evidence. Verification starts off.
  • Use Nx to orchestrate native Cargo, Node, and Python suites with coverage-based function-level impact selection and full-suite fallback when evidence is uncertain.
  • Replace dated documentation and unused demo artifacts with focused setup, reference, architecture, operations, and development guides.

Install the integrated VSIX and reload VS Code. Review changed Decision hooks in /hooks. Run Decision: Register MCP Tools in Codex to register the tools, then start a new Codex chat. Use Decision: Configure Completion Verification to choose an optional review mode.

Validation includes native Linux and Windows tests, Node and Python suites, function-coverage collection, Chromium checks, synthetic provider and interruption/publication checks, and exact production-package verification. Native packaged checks exercise installation, concurrent reuse, both PowerShell launchers, MCP discovery, settings, measurement, and patch restoration against a reviewed Codex host.

The attached SHA256SUMS file identifies both release archives. Saved credentials and runtime recovery files are preserved during updates.

Codex Decision 0.16.2

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 07 Nov 11:07

Healthy installation checks now use two Codex CLI commands instead of three. A synthetic ready-check fixture reduced native Windows file reads from 57 to 35 and Python file opens from 68 to 35. Both paths reuse validated package data and retain existing cache and rollback behavior.

The installer and patch checker use bounded regular-file reads with opened-handle checks. Patch assets are limited to 32 MiB. Python CLI metadata streams under a 2 MB limit and the existing 90-second deadline, decodes as UTF-8, and discards private stderr. Failed children are stopped and reaped. Cache restoration applies restrictive directory permissions after restoring their children.

Package staging validates every required input before creating its output directory. VSIX verification also checks the extension identity. Windows CI now exercises bounded CLI reads and oversized patch rejection directly.

Install the VSIX through VS Code and reload the window. Review the updated hooks in /hooks, then start a new thread. Existing credentials, data, cached hook versions, and rollback files remain in place.

Full Windows, offline, browser and package verification.

Codex Decision 0.16.1

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 07 Nov 09:49

Codex Decision now supports Codex preview 26.51021.22027 alongside the reviewed stable builds. Different package version labels can reuse a reviewed profile only when all four original asset hashes match. Unknown or modified assets still fail verification before a patch write.

Decision and Chime 0.3.1 use one kernel lock per Codex runtime to serialize plugin registration. Temporary installation, patch, and WSL failures retry automatically. File-access refusals remain distinct. The installer deadline allows the bounded Codex CLI transaction to finish. Both Decision installers retain verified older hook caches after Codex refreshes the plugin, including failed refreshes, so existing thread paths remain available after the transaction.

Validation covers Rust, Node, Python, Chromium, native Windows, cross-companion lock contention, exact package contents, and background installation with the stable and preview Codex hosts. See the verification workflow.

Install the VSIX through VS Code and reload the window. Run Decision: Repair Integration if needed. Review the updated Decision hook in /hooks, then start a new Codex thread. Existing data and rollback files stay in place.

Codex Decision 0.16.0

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 05 Nov 15:58

Custom providers can now send a model alias and validate a different exact response model. Optional public PEM certificates support private HTTPS services with certificate and hostname verification enabled.

  • Configure the endpoint, request model, response model, authentication, and public CA in either connection form.
  • Keep certificate trust scoped to the custom connection. Changing its CA requires fresh saved credentials.
  • Preserve existing provider defaults and full-output handling when a request fails.
  • Use generic public examples. Package verification rejects embedded internal deployment URLs.

The integrated VSIX includes Windows and Linux x86_64 production runtimes. Automated Rust, Node, Python, browser, and native installation checks passed before publication.

Install codex-decision-0.16.0.vsix in Visual Studio Code, then reload the window to activate the update. Existing settings, credentials, and thread choices remain in place.

Codex Decision 0.15.2

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 27 Oct 08:51

Reduce repeated local work and add private diagnostics for usage audits.

  • Read the credential file once per settings request, with consistent provider status and key length.
  • Record current relevance, final guard, proposed omission, and prepared omission counts.
  • Reuse validated command and Lab output views within each hook invocation, including fallback.
  • Share unchanged composer and panel activity reads, with publication-safe invalidation and isolated results.
  • Add bounded metadata-only invocation/request logs and an offline audit command.

Validation: Linux Rust, Node, Python, formatting and Clippy passed. Windows Rust and the focused Node subset passed. Both packages passed exact-entry, source-byte, version, ELF and PE checks.

Install the VSIX in Visual Studio Code, then reload the window. The bundled hook is 0.15.2. Existing filtering settings, provider credentials, and originals remain in place. Codex can require review of the updated hook in /hooks; trust it there, then start a new thread. Prepared savings still do not establish delivered context savings.

0.15.1

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 26 Oct 08:01

Adds automatic updates from GitHub Releases, plus clearer recovery after Codex updates.

  • Checks for newer stable VSIX releases daily. Verifies the exact asset size and GitHub SHA-256 digest before installing through VS Code.
  • Adds Decision: Check for Updates. Set codexDecision.autoUpdate to false to use manual updates.
  • Offers Reload Window after installation. It does not interrupt work with a forced reload. Reload waits for temporary download cleanup.
  • Reports the loaded control and bundled hook versions. Unsupported Codex diagnostics now offer Check for Updates and explain manual VSIX recovery.
  • Handles Windows temporary directories on RAM drives and preserves changed or unknown temporary files.

On machines still running Decision 0.14.1, install this VSIX manually through VS Code → Extensions → … → Install from VSIX…. Reload VS Code, run Decision: Repair Integration, and reload after a successful repair. This one-time installation enables future automatic updates. Codex 26.1021.22027 is supported by the bundled hook runtime 0.15.0.

The VS Code control is 0.15.1; the hook runtime remains 0.15.0. The standalone CLI ZIP is unchanged and remains available in release 0.15.0. Provider settings, credentials, chat history, hook trust, and per-thread choices are preserved.

Validation: 219 Linux Node tests passed with four platform skips; all 16 Python checks passed; 37 focused native Windows tests passed. A real public GitHub VSIX download passed checksum and cleanup checks. The final VSIX passed the background Windows install, exact-cache, concurrent/repeated-check, hook, panel, patch, and restore test against Codex 26.1021.22027. No editor windows or real provider requests were needed.

If Codex still reports that its user interface could not start after updating and repairing, inspect its renderer logs. The older Decision compatibility refusal itself makes no Codex file changes. See recovery instructions.

0.15.0

Choose a tag to compare

@PhilippElhaus PhilippElhaus released this 24 Oct 08:37

Fixes Decision integration on Codex 26.1021.22027 and adds native Windows execution.

  • Verifies the newer Codex bundle layout with exact hashes and preserved rollback files.
  • Includes Windows x86_64 and Linux x86_64 hook runtimes in one VSIX. Native Windows needs no WSL or Python.
  • Follows Codex’s Windows/WSL setting and switches verified data-directory pointers while retaining each runtime’s data.
  • Fixes copied Linux paths, mixed-slash WSL UNC paths, dotted distro names, Windows path case, and inherited CODEX_HOME overlap.
  • Handles the default file owner of elevated Windows accounts and secures native Windows state and fixes staged result publication. WSL credential writes preserve the previous file if permission repair fails.
  • Adds a background-only package smoke test that opens no editor windows.

In Visual Studio Code, open Extensions (Ctrl+Shift+X), select … → Install from VSIX…, and choose the downloaded VSIX. If Windows opens Visual Studio VSIX Installer when you double-click the file, close it and use the VS Code menu. Reload VS Code after installation and review the updated hook in /hooks. If an old explicit data-directory override points at another runtime, clear codexDecision.dataDirectory and run Decision: Repair Integration.

Validation passed: 301 Linux Rust tests, 36 native Windows Rust tests, 207 Linux Node tests, 60 Windows Node checks, 16 Python checks, Clippy, browser checks, and the final VSIX’s background native installation/patch/restore test. Platform skips and the desktop-rendering limit are recorded in the verification report.

The VSIX, standalone ZIP, and SHA-256 manifest are attached. Prior releases remain available for rollback.