ToolsEnabled Sim 0.1.5 (beta)

ToolsEnabled Sim 0.1.5 (beta) fixes the public plugin-install route and fresh-user CLI diagnostics while preserving the pinned physics engines and recorded trajectory bytes. MIT licensed.

What changed

• Public plugin marketplaces. The repository and release ZIP include Claude Code and Codex marketplace catalogs for toolsenabled-sim. Add ToolsEnabled/toolsenabled-sim with claude plugin marketplace add or codex plugin marketplace add; Claude Code installs toolsenabled-sim@toolsenabled-sim. A Git-backed install needs npm ci --ignore-scripts --no-audit --no-fund in its installed plugin directory. The verified ZIP includes dependencies and can be added as a local marketplace.
• Connection configuration. All five client formats require an absolute existing connection file. The helper preserves that path without reading its private capability; client startup still checks ownership and connection contents.
• Empty events. An unbound offline observer gets an explicit visibility explanation instead of an unexplained blank pane. Private actions remain filtered; shared launcher commits remain visible.
• Capture and verification errors. Capture and artifact verification print one-line usage and errors. Capture refuses bare valued options and removes only output it freshly created when capture fails, including after writing frames; a pre-existing directory is retained.
• Honest prerequisites. No Claude Desktop bundle is attached. Capture uses SIM_CHROMIUM_EXECUTABLE or an already installed Playwright-cache Chromium; it never downloads a browser. The README explains Rapier 0.17.3's upstream initialization notice beside the quick start. PyYAML 6.x is a test prerequisite only.
• Physics unchanged. Dependency versions and vendored bytes are unchanged: Rapier 0.17.3, MuJoCo 3.14.0, Three.js 0.180.0 and playwright-core 1.62.0.

Get started

1. Download toolsenabled-sim-0.1.5.zip and toolsenabled-sim-0.1.5.zip.sha256, then run sha256sum -c toolsenabled-sim-0.1.5.zip.sha256.
2. With Node.js 22 or later, run unzip toolsenabled-sim-0.1.5.zip, cd sim, node tools/demo.mjs --output ./runs/demo, then node tools/replay.mjs ./runs/demo. For MuJoCo: node tools/demo.mjs --output ./runs/demo-mujoco --engine mujoco, then node tools/replay.mjs ./runs/demo-mujoco.
3. To connect your own agents, see docs/LIVE.md: node tools/live.mjs --root /absolute/run --work-record /absolute/work-record.json (add --engine mujoco for MuJoCo). See docs/CLAUDE-INSTALL.md for the marketplace commands and per-agent private connection options.

Tested on this exact release (source commit 2f47a39806a84b450d8b2eb8b46b0d4a56ec9a27, tag v0.1.5; ZIP SHA-256 87123dec2d4db33c3a1c46fa8a9839003fbc032b3dd7d90a32236540f0ce1800; Linux, Node.js 22.19.0)

• 114 of 114 Node tests pass headless on source and the extracted ZIP, including actual Chromium rendering and capture failure cleanup. The 42 plugin hook tests, DeepSeek configuration test and strict Claude marketplace validation also pass on both. All 14 packaging/scanner tests passed on source; 12 of 14 were rerun and passed from the ZIP. Two ZIP fixture tests were not rerun because they create Git commits in scratch repositories outside the permitted patch clone; no test was changed or weakened.
• The ZIP rebuilds byte for byte twice from this clean commit: 5,428,715 bytes, 141 files under one sim/ wrapper.
• The scripted demo delivers three crates with no collisions and replays byte-identically over 600 ticks on both engines. Trajectory SHA-256: Rapier 453aa41446485c2865437652a7c4a6256fb395b8ccf52dc7ae6ec35f4c8e53a5; MuJoCo 278254654043d0aa09299940eddb56eef083a0377fd0597868ba2cb10b7ea9d6.
• Configuration generation, stdio transport, marketplace source resolution and plugin hooks are tested locally. Real model-driven sessions, native Desktop installation and Codex's Plugins Directory installation remain separate integration qualifications.

Known limits

• Linux was tested. Native Windows is unsupported because Sim relies on POSIX file ownership checks. Native Claude Desktop installation and production bundle signing need separate qualification; no MCPB is attached.
• Git-backed catalogs contain source and need the dependency install above; use the verified extracted ZIP for offline dependencies. Catalog registration alone does not establish pane or MCP readiness.
• The pinned Rapier compatibility initializer prints an upstream notice on stderr once per process. Passing an object to its zero-argument wrapper does not remove it. Recorded physics bytes and MCP stdout are unaffected.
• Seven dependency files exceed 256 KiB; THIRD-PARTY.md lists the shipped files and licenses. No browser binary ships. Identical rendered frames require the same Chromium build and renderer.
• The handoff scanner cannot inspect keys hidden in raw deflate data without a recognizable header.
• One-tick live runs at the default recording cap have a practical ceiling of about 30,000 ticks; larger scenes or heavier traffic can stop sooner. The planner does not predict other robots' future paths; the coordinator schedules crossing traffic.
• Driver labels are supplied by the operator. Processes running as the same OS user can read private files and act as that user. See SECURITY.md. Security policy: https://toolsenabled.ai/security/; support: support@toolsenabled.ai.

ToolsEnabled is not affiliated with or endorsed by Anthropic, OpenAI, DeepSeek, Cursor, Google DeepMind or any other AI provider.