Skip to content

ToolsEngine 0.1.8

Latest

Choose a tag to compare

@ToolsEnabled-Inc ToolsEnabled-Inc released this 15 Oct 11:13

ToolsEngine 0.1.8 adds native Windows installation checks and a self-distributed Codex plugin. Windows paths require fixed local NTFS, conservative raw ACL/owner and retained ancestor validation; unsafe/reparse/overlap paths fail closed. The plugin exposes eight file/public-web/status/discovery tools with browser and desktop control off, validates matching source/lock/native-helper bytes in a separately prepared durable runtime, and protects both physical program roots. Startup downloads nothing and does not change client approvals.

Validated source: 4396c25a09543a8b0a9ca9ad0e3888fd47b26e4a, including the ready OpenAI plugin branch. Two offline Linux builds each passed 254 tests, with 22 platform skips, across 55 files; both release archives and two npm packs reproduce byte-for-byte.

Native execution was tested on Windows 10 Pro 22H2 x64 build 19045, Node 22.14.0 and Windows PowerShell 5.1.19041.6456. Each elevated engineering and restricted medium run passed 10 native source tests, 10 actual ancestor cases and 11 final-archive acceptance steps. Checks include Unicode installation, all 3,868 installed files' raw/private/inherited ACLs, stdio/file/CRLF and path/hardlink/junction refusals, both launcher roots, helper-identity mismatch, EOF, damaged payload, interrupted-state refusal and uninstall preserving workspace. All installed files were current-user-owned in the medium run; the elevated run's administrator-owned files are recorded separately. The medium token measured integrity 8192, TokenElevation=false, privileged groups deny-only and only SeChangeNotifyPrivilege; both administrator-only canaries were denied.

A different worker followed the public docs from fresh folders in both contexts: 16/16 install/check/list/version, eight-tool stdio/file/refusal, recheck and uninstall checks passed each. Every run ended with zero owned processes and deleted its temporary task. The no-browser route and native plugin entry were exercised directly; no real Windows Codex host/model or console GUI was launched.

The complete native Windows regression does not pass. A second elevated engineering run attempted all 55 files: 276 tests, 232 passed, 27 failed and 17 skipped. It used three declared external test-fixture adaptations and a confined synthetic account profile; the published runtime and dependencies were unchanged. Failures include dedicated-profile cookie persistence and installer/profile or platform assumptions still being diagnosed. The first attempt also remains recorded: its first file reached a 600-second timeout during fixture cleanup after 16 successful subtests. No complete native-suite or filtered-user full-suite pass is claimed. The documented eight-tool no-browser qualification above remains the tested Windows scope; independent headless-browser acceptance is pending. Any published source correction will require a new patch release.

Owner acceptance remains pending for interactive browser/desktop features and the real Windows Codex client. Windows 11 is untested. Actual Codex 0.162.1 marketplace/model-task evidence covers Linux on the merged lead branch. This is self-distribution, with no OpenAI directory listing or approval claim. No product account or paid model API is required. Interrupted Windows install recovery remains manual. The npm .tgz is a downloadable asset; no npm registry publication was performed.

Download the matching platform archive and checksum, follow its INSTALL.txt, and read app/docs/CODEX.md for the separate plugin/runtime setup. Eight release files are attached, including both platform archives, npm source package, checksums and build report. Release assets are downloaded back and compared byte-for-byte as part of publication verification.