ToolsEnabled Sim 0.1.6 (beta)

ToolsEnabled Sim 0.1.6 (beta) makes the action commands run exactly as typed, gives every MCP tool a title and its hints, and documents what the plugin runs, sends and reads, while preserving the pinned physics engines and recorded trajectory bytes. MIT licensed.

What changed

• Action commands run as typed. Before any model turn, the eight /toolsenabled-sim: action commands still check that the arguments fit, that you typed the action yourself at the terminal or through Remote Control, and that this connection's role and mode allow it. They no longer replace your arguments with the check's data. If the check itself fails, the command is refused instead of running unchecked. A scenario path typed with repeated spaces is refused, and the model reads the checked scenario file with the normal Read approval.
• whoami in sim.status. The status reply names the caller's own role, agent and robot, never the connection capability. The action commands read the robot ID from it.
• Tool titles and hints. Every MCP tool has a plain-language title and declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint. sim.observe, sim.status and sim.assignments are read-only; the nine tools that change the shared world are marked destructive; no tool reaches beyond your computer.
• What the plugin runs, sends and reads. A new README section lists each hook, the one program the plugin starts (its own reader, under a cleared environment), the files it reads, and that it talks only to your hub on 127.0.0.1 and sends nothing to ToolsEnabled.
• Listing details. The plugin manifest names its documentation, privacy (https://toolsenabled.ai/privacy/) and support (https://toolsenabled.ai/support/) pages, and its homepage is https://toolsenabled.ai/sim/. The repository carries the plugin directory's listing icon; the release ZIP leaves it out.
• 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.6.zip and toolsenabled-sim-0.1.6.zip.sha256, then run sha256sum -c toolsenabled-sim-0.1.6.zip.sha256.
2. With Node.js 22 or later, run unzip toolsenabled-sim-0.1.6.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 ed4ddf7f5c778db329c0d724267cb42be1c1c4c7, tag v0.1.6; ZIP SHA-256 654a6ae1fcc333c8a8eb745ce7d7ed350e75bb00c5ff24e3f9341d137290885a; Linux, Node.js 22.19.0)

• 116 of 116 Node tests pass headless on source, including actual Chromium rendering and a test that lists every tool through the real server and pins its title and hints. All 14 packaging/scanner tests and the DeepSeek configuration test pass on source. 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 twice from this clean commit: 5,437,128 bytes, 141 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.5.
• A local Claude Code marketplace add and install from this commit lists toolsenabled-sim 0.1.6. Configuration generation, stdio transport 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.
• 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.
• Git-backed catalogs contain source and need npm ci --ignore-scripts --no-audit --no-fund in the installed plugin directory; 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. 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.