Skip to content

ToolsEnabled Site Studio 0.1.5 (beta)

Pre-release
Pre-release

Choose a tag to compare

@ToolsEnabled-Inc ToolsEnabled-Inc released this 13 Oct 11:07

ToolsEnabled Site Studio 0.1.5

Published 2026-10-13. Source commit a79d870 on main, tag v0.1.5.

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.5.zip (extracts to site-studio/) 4810f42ad70ef5feda58e7980899fc1c9e644ba1c9e0cbbe85062e16cac4dd78
toolsenabled-site-studio-0.1.5.zip.sha256 the line above, sha256sum -c format

Verify, then extract:

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

What changed since 0.1.4

  • Every MCP tool declares annotations: a short title, readOnlyHint, destructiveHint, idempotentHint for the nine tools that change the working copy or its checkpoints, and openWorldHint, which is false for every tool. Seven tools only read. The nine that change things are marked destructive, because an edit can overwrite or remove content and any change can drop the oldest undo states or timeline entries. Tool names, inputs and behavior are unchanged, and a test pins every value.
  • The README has a new section, "What this plugin runs, sends and reads". It covers the MCP server's command and what it reads, writes and sends; what each /site-studio pane hook does; the one program the pane starts, with its full command; what that program reads; the commands and skill; the tests the plugin directory flags; and the one maintainer script that uses the network.
  • The repository carries the plugin directory's listing icon. It is not part of the release archive.
  • The Claude plugin manifest names the documentation, privacy policy (https://toolsenabled.ai/privacy/) and support (https://toolsenabled.ai/support/) pages. The Claude, Codex and Desktop manifests use the product page https://toolsenabled.ai/site-studio/ as the homepage.
  • The README and install guide say that installing from the repository's own marketplace does not depend on any public plugin directory.
  • The README and docs/EXPORT-GATE.md describe agent export as a proposed design that is not implemented, without internal decision wording.
  • Tests: the processes the tests start get only the environment variables they need; the test files the plugin directory flagged read no environment variables; and the package test also passes in an extracted archive.

What is in 0.1.5

  • 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. In Codex, run codex plugin marketplace add ToolsEnabled/toolsenabled-site-studio. 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-13 the full Node test suite passed on the release source and again on the files extracted from the ZIP above: 265 tests, 0 failures, on Linux with Node 22.19.0 and Google Chrome 154 headless for the fifteen browser tests. 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.296 claude plugin validate --strict passes for the plugin and marketplace manifests, and the 54 hook tests pass. claude plugin marketplace add plus claude plugin install toolsenabled-site-studio@toolsenabled-site-studio from a local clone of the release commit succeeded in a scratch configuration: claude plugin list shows version 0.1.5 and the plugin's MCP server connects. The Codex marketplace file follows OpenAI's published format and 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/).