ToolsEnabled Sim 0.1.9 (beta)

ToolsEnabled Sim 0.1.9 (beta) adds a reviewer's "Try it" path to the README, makes SECURITY.md cite this repository's LICENSE for "as is", and moves the one test that runs a printed command in a shell into a file of its own. Code, physics and recorded trajectory bytes are unchanged from 0.1.8. MIT licensed.

What changed

• Try it. README has a "Try it" section with the shortest path from nothing to a working result: start a hub, install the plugin with the coordinator's connection file, then three prompts, each with the result it shows: /sim status opens the Sim pane (Tick 0 · 0/3 delivered · 0 collisions · score 0), a plain request to deliver amber's crate ends with 1 of 3 delivered, 0 collisions and score 100, and /toolsenabled-sim:step 60 advances one simulated second. No account or API key is needed.
• "As is" cites the LICENSE. SECURITY.md says Sim is provided "as is", without warranty of any kind, as this repository's LICENSE (MIT) says. It used to cite https://toolsenabled.ai/terms/, which covers only Fleet and the website.
• Shell-run test in its own file. The replay test that runs the printed capture command in a POSIX shell moved unchanged from test/audit-views.test.mjs to test/replay-capture.test.mjs, a file that makes no HTTP request of its own. Both files now record ticks through the plugin's MCP server (tools/mcp-client.mjs) instead of a direct HTTP call to the hub. The suite runs the same 129 tests as 0.1.8.
• Unchanged: runtime code, the MCP tool list, titles and hints, dependency versions and vendored bytes (Rapier 0.17.3, MuJoCo 3.14.0, Three.js 0.180.0, playwright-core 1.62.0).

Get started

1. Download toolsenabled-sim-0.1.9.zip and toolsenabled-sim-0.1.9.zip.sha256, then run sha256sum -c toolsenabled-sim-0.1.9.zip.sha256.
2. With Node.js 22 or later, run unzip toolsenabled-sim-0.1.9.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 try the Claude Code plugin, follow the README's "Try it" section. To connect your own agents, see docs/LIVE.md and docs/CLAUDE-INSTALL.md (marketplace commands, one CLAUDE_CONFIG_DIR per robot agent, per-agent private connection options).

Tested on this exact release (source commit 7377545fce4ce19aa53b289ced00fb8d768af99d, tag v0.1.9; ZIP SHA-256 7c4271b45adcea75b25af27cf01e703ee7c714ab1347bbf436db0d1c5fbdc38f; Linux, Node.js 22.19.0, Claude Code 2.1.296)

• 129 of 129 Node tests pass headless on source and on the extracted ZIP, the same 129 tests as 0.1.8, including actual Chromium rendering and the printed capture command run exactly as printed in a POSIX shell. All 14 packaging/scanner tests and the DeepSeek configuration test pass on source and on the extracted ZIP. The 44 plugin hook tests and strict Claude validation pass on source and on the extracted ZIP; strict validation also passes on plugin.json and the marketplace catalog.
• The ZIP rebuilds byte for byte three times from this clean commit, twice in the release clone and once in a fresh clone with dependencies from the lockfile's offline cache: 5,446,297 bytes, 142 files under one sim/ wrapper.
• From the extracted ZIP, 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, the same as 0.1.8.
• The README "Try it" path, run from the extracted ZIP against a running hub: the /sim status reader, launched as the plugin launches it, shows Tick 0 · 0/3 delivered · 0 collisions · score 0; the demo's goto, grab, release and step calls for amber through the plugin's MCP server end with 1 of 3 delivered, 0 collisions and score 100; the /toolsenabled-sim:step 60 preflight allows the step, which advances 60 ticks. A local Claude Code marketplace add and install of the extracted ZIP with the coordinator's connection file lists toolsenabled-sim 0.1.9, and claude mcp list shows its server Connected. 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.
• A Sim action starts only from your own prompt, at the terminal or through Remote Control. A headless claude -p run, a scheduled or relayed message, another session or another plugin cannot start one.
• A Git-backed install takes the repository's default branch at its current commit. Use the verified extracted ZIP for this exact release and offline dependencies. Catalog registration alone does not establish pane or MCP readiness.
• After a storage failure, the stopped run's recording can end in a partial record; replay cannot verify that run. Start a new hub, with a new run root or once the storage is fixed, to continue.
• The pinned Rapier compatibility initializer prints an upstream notice on stderr once per process. 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.