ToolsEnabled Sim 0.1.10 (beta)

ToolsEnabled Sim 0.1.10 (beta) tidies the Codex plugin manifest for installs from this repository's own marketplace: Codex no longer tries to read the Claude Code /sim mod as a Codex hook file, and the Codex listing gets its website, support and privacy links, the full publisher name, a shorter description and a brand color with enough contrast. Code, physics and recorded trajectory bytes are unchanged from 0.1.9. MIT licensed.

What changed

• No Claude mod read as a Codex hook file. .codex-plugin/plugin.json declares "hooks": {}. Without a hooks field Codex reads hooks/hooks.json, which here is the Claude Code /sim mod and not a Codex hook file. An explicit hooks value replaces that default discovery, and an empty one adds no hooks. Claude Code is unaffected.
• Codex listing details. interface.websiteURL https://toolsenabled.ai/sim/, supportURL https://toolsenabled.ai/support/ and privacyPolicyURL https://toolsenabled.ai/privacy/; developerName "ToolsEnabled, Inc."; shortDescription "Coordinate warehouse robots" (27 characters; the limit is 30); brandColor #2fb8a4 (2.47:1 against white) with brandColorDark #4ddbc6.
• Wording. README and docs/CLAUDE-INSTALL.md say to install Sim from the toolsenabled-sim marketplace in Codex's /plugins browser. They used to say "the Plugins Directory", which is the name of OpenAI's public directory; Sim is not listed there.
• Unchanged: runtime code, the MCP tool list, titles and hints, the Claude Code plugin and its /sim mod, 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.10.zip and toolsenabled-sim-0.1.10.zip.sha256, then run sha256sum -c toolsenabled-sim-0.1.10.zip.sha256.
2. With Node.js 22 or later, run unzip toolsenabled-sim-0.1.10.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 54529a1e99536ea8ced380d553bf7bb5ca2052ba, tag v0.1.10; ZIP SHA-256 4336819a72e6752981f0a386a1451b601fc2d94c2b1470523eb2e0c1d68cb02c; 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.9, including actual Chromium rendering and the printed capture command run exactly as printed in a POSIX shell. The package test now also checks the Codex manifest's empty hooks object, publisher, description length and listing links. 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,447,079 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.9.
• A local Claude Code marketplace add and install of the extracted ZIP with the coordinator's connection file lists toolsenabled-sim 0.1.10, and claude mcp list shows its server Connected.
• Codex was not run for this release. The Codex changes follow OpenAI's published plugin documentation and were checked against the public openai/codex source: its hooks loader reads hooks/hooks.json only when the manifest has no hooks value. Real model-driven sessions, native Desktop installation and installation from Codex's /plugins browser 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.