Skip to content

ToolsEnabled Site Studio 0.1.8 (beta)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@ToolsEnabled-Inc ToolsEnabled-Inc released this 13 Oct 20:29
v0.1.8
5f91c1c

ToolsEnabled Site Studio 0.1.8

Published 2026-10-13. Source commit 5f91c1cf4da3715702f39993228cdc08018d8599 on main, tag v0.1.8.

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.8.zip (extracts to site-studio/) d61b1ea912dc7e7fd3bc6ea919c34e1759ae4f9dd474085a5991f7eb2c55a5f3
toolsenabled-site-studio-0.1.8.zip.sha256 the line above, sha256sum -c format

Verify, then extract:

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

What changed since 0.1.7

This release closes three documentation gaps found in a review against the Claude plugin directory policy. The server, the tools and the /site-studio pane are unchanged.

  • Try it. README has a "Try it" section with the shortest path from nothing to a working result: copy the bundled sample site, make a private state folder, install the plugin with the three folder options, then three prompts, each with the result it shows: listing the pages (about.html, index.html and styles.css at revision 0), changing the headline and saving the checkpoint first-edit (revision 1; the original site folder is unchanged), and the /site-studio history pane. No account or API key is needed. It replaces the one-line example under "Connect a client".
  • "As is" cites the LICENSE. SECURITY.md says Site Studio 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.
  • The skill no longer names the log path. The skill used to give the model the path of each host's log that holds the one-time dashboard link. It now tells the human to find the Site Studio dashboard session: line in their MCP host's log, as the README explains. The rest of the skill is unchanged.
  • Tool names, inputs, descriptions and annotations, the views, the pane and export are unchanged from 0.1.7.

What is in 0.1.8

  • 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: 275 tests, 0 failures, on Linux with Node 22.19.0, Google Chrome 154 headless for the fifteen browser tests and a short, real TMPDIR. These are the same 275 tests as in 0.1.7. 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 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 (706,643 bytes, 102 members). The README "Try it" path was run headless from the extracted ZIP: with a copy of the bundled sample site, a new private state folder and a new export folder, the plugin's MCP server listed the three files at revision 0; web_set_text on the <h1> and the checkpoint first-edit produced revision 1 while the original site folder stayed unchanged; and the /site-studio history pane reader, launched as the plugin launches it, listed the open, the text update and the checkpoint. claude plugin marketplace add plus claude plugin install toolsenabled-site-studio@toolsenabled-site-studio with those three folders 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.8 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/).

Assets 4
Loading