Skip to content

ToolsEnabled Site Studio 0.1.10 (prerelease)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@ToolsEnabled-Inc ToolsEnabled-Inc released this 14 Oct 20:06
v0.1.10
b50e154

ToolsEnabled Site Studio 0.1.10

Published 2026-10-14. Source commit b50e154a220614d4d96a7c78e0c92e9e1d2cb438 on main, tag v0.1.10.

Site Studio edits a static website through an MCP host using a private working copy, live browser preview, revision history and named checkpoints. The original remains unchanged until a confirmed export.

Files in this release

File SHA-256
toolsenabled-site-studio-0.1.10.zip (extracts to site-studio/) 3ae5612cea200c65cf5702287a4dc3000e294b6ef5a631a06fde60b07eef5b65
toolsenabled-site-studio-0.1.10.zip.sha256 the line above, sha256sum -c format

Verify, then extract:

sha256sum -c toolsenabled-site-studio-0.1.10.zip.sha256
unzip toolsenabled-site-studio-0.1.10.zip

What changed since 0.1.9

This release prepares the plugin for the Claude plugin directory's review and fixes what the fresh-user check of 0.1.9 found. The server, the tools, the /site-studio pane and its mod behave as in 0.1.9, and no feature was removed.

  • No host variable copied into the server's settings. The Claude Code plugin's .mcp.json and the Desktop manifest.json no longer copy SystemRoot from the host into the server's environment. Claude Code starts plugin servers with its own environment, so the server still sees SystemRoot wherever it is set; on Linux the entry was empty, and the server reads it only on Windows, which is not supported. The Codex manifest still forwards it by name, and the install guide no longer says that a host never passes its environment to an MCP process.
  • Tests restructured, same checks. The browser cookie test's second loopback server moved into test/session-helper.js, the reviewed tool-annotations test into test/tool-annotations.test.js, and two preview-cache child programs from inline program text into test/preview-cache-worker.js. The maintainer script tools/generate-release.py reads the release file through the new tools/release_fetch.py and still only compares the bytes.
  • Test fixes. The test runner test no longer fails with a TMPDIR of 37 to 62 bytes, and the Python test workers no longer leave tools/__pycache__ behind.
  • Codex description now matches the Claude Code listing: "Edit static sites in a private working copy, with checkpoints, local preview and human-controlled export."
  • README. The claude plugin configure form that sets the three folders (--values-stdin, or /plugin configure inside Claude Code; the bare command only lists them); the marketplace installs the repository's main branch, which each release moves to its release commit; the client helper names the absolute Node.js path, so rerun it after upgrading or switching Node.js; one plain sentence for each directory notice that stays; every host the tests name, and which test processes get a reduced environment and which the test runner's.

What is in 0.1.10

  • Linux-only release; Node.js 22 or newer. Native Windows is not supported. macOS and native desktop-client installation remain unqualified.
  • Read-only local views cover pages, search, history, checkpoints, changes, local link checks, dashboard instructions, advisory export checks and startup diagnostics. They do not perform export or repair. Pane keyboard handling and child-environment isolation are documented in the README. Real interactive-client qualification remains separate from headless checks.
  • Export stays a dashboard action with session authorization, a current revision and explicit confirmation. The destination is configured at startup, and its parent folder must already exist. Replacing the original retains a backup; exporting to a new folder leaves the original intact. Export does not deploy. Ordinary promotion/persistence failures roll back. A process or machine crash between folder renames may leave the original at the retained backup path; keep it for manual recovery and maintain independent backups of valuable sites.
  • Dashboard-secret scraping from stderr or host logs to automate confirmation is unsupported. Any HTTP client with the dashboard capability and the required request fields can confirm export; the server cannot distinguish an agent from a human capability-holder. The resulting human history entry is not an audit of agent authorization. An explicit human opt-in with an audited agent-export path is a documented proposal only and is not implemented in this release. See EXPORT-GATE.md.
  • Client configuration helpers: Claude Code, Claude Desktop, Codex, Cursor, DeepSeek Harness. These are equal configuration options; generation does not establish native installation or model-workflow qualification. Separate plugin manifests are included for Claude Code and Codex, and the repository is a plugin marketplace for both. In Claude Code, run claude plugin marketplace add ToolsEnabled/toolsenabled-site-studio, then claude plugin install toolsenabled-site-studio@toolsenabled-site-studio --config site_directory=/absolute/site --config data_directory=/absolute/private-state --config export_directory=/absolute/new-export; without the three settings the plugin installs but starts no server until you set them with /plugin configure or claude plugin configure toolsenabled-site-studio@toolsenabled-site-studio --values-stdin. In Codex, run codex plugin marketplace add ToolsEnabled/toolsenabled-site-studio. The marketplaces install the repository's main branch; this ZIP is the checksum-verified route. Installing from this repository's marketplace does not depend on any public plugin directory.

Preview disables site scripting and blocks external resources by default. A deliberate external-resource opt-in permits HTTPS references. Export preserves source behavior, so review the exported files before serving them. Local session controls are not a sandbox against processes running as the same OS user. See README.md and SECURITY.md.

What was tested

On 2026-10-14 the full Node test suite passed on the release source and again on the files extracted from the ZIP above: 276 tests, 0 failures, on Linux with Node 22.19.0, Google Chrome 154 headless for the fifteen browser tests and a 54-byte TMPDIR. They are the 0.1.9 release's 275 tests plus the Codex manifest test that a test-only commit after 0.1.9 put in a file of its own. Without SITE_STUDIO_CHROME those fifteen browser tests fail with the message Browser tests require SITE_STUDIO_CHROME set to a Chrome/Chromium executable; they are not skipped.

Claude Code 2.1.299 claude plugin validate --strict passes for the plugin and marketplace manifests on the release source and on the extracted files, and the 54 hook tests pass on both. The ZIP was built three times, twice from git archive copies of the release commit and once from the clone, and the three builds are byte-identical (719,922 bytes, 106 members). claude plugin marketplace add plus claude plugin install toolsenabled-site-studio@toolsenabled-site-studio with a copy of the bundled sample site, a new private state folder and a new export folder succeeded in a scratch configuration, from a local clone of the release commit and from the extracted ZIP: claude plugin list shows version 0.1.10 and the plugin's MCP server connects. Installed without the folder options, the server started only after the README's claude plugin configure … --values-stdin line. Codex was not run for this release, and the Codex marketplace file was not exercised in a Codex client. Native installation, real interactive pane behavior, public directory acceptance and production publisher trust are not established by this release.

Support and security contact: support@toolsenabled.ai (security policy: https://toolsenabled.ai/security/).

Assets 4
Loading