Repository navigation

Release list

ToolsEnabled Site Studio 0.1.10 (prerelease) Pre-release

Pre-release

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

ToolsEnabled Site Studio 0.1.9 (beta) Pre-release

Pre-release

ToolsEnabled-Inc released this 13 Oct 23:26

v0.1.9

ef510ad

ToolsEnabled Site Studio 0.1.9

Published 2026-10-13. Source commit ef510adb1e36fec8b32e71ce0575f76cef194577 on main, tag v0.1.9.

Files in this release

File	SHA-256
`toolsenabled-site-studio-0.1.9.zip` (extracts to `site-studio/`)	`eb0cc0d4b036eca8b09b64b284d79539696440730fe406332a88ca765c940cb4`
`toolsenabled-site-studio-0.1.9.zip.sha256`	the line above, `sha256sum -c` format

Verify, then extract:

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

What changed since 0.1.8

This release tidies the Codex plugin manifest, .codex-plugin/plugin.json, for installs from this repository's own marketplace. The server, the tools, the /site-studio pane and its mod, and the Claude Code plugin are unchanged.

No Claude mod read as a Codex hook file. The Codex manifest declares "hooks": {}. Without a hooks field Codex reads hooks/hooks.json, which here is the Claude Code /site-studio mod and not a Codex hook file. An explicit hooks value replaces that default discovery, and an empty one adds no hooks.
Codex listing details. interface.websiteURL https://toolsenabled.ai/site-studio/, supportURL https://toolsenabled.ai/support/ and privacyPolicyURL https://toolsenabled.ai/privacy/, and developerName "ToolsEnabled, Inc.", as in author.
The package test that checks the Codex manifest now also checks the empty hooks object, the publisher and the three listing links.
Tool names, inputs, descriptions and annotations, the views, the pane and export are unchanged from 0.1.8.

What is in 0.1.9

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.

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.8. 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 (708,427 bytes, 102 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.9 and the plugin's MCP server connects. Codex was not run for this release: the Codex manifest follows OpenAI's published plugin documentation and was checked against the public openai/codex source, whose hooks loader reads hooks/hooks.json only when the manifest has no hooks value. 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

ToolsEnabled Site Studio 0.1.8 (beta) Pre-release

Pre-release

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.

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.

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

ToolsEnabled Site Studio 0.1.7 (beta) Pre-release

Pre-release

ToolsEnabled-Inc released this 13 Oct 18:17

v0.1.7

26f7988

ToolsEnabled Site Studio 0.1.7

Published 2026-10-13. Source commit 26f7988 on main, tag v0.1.7.

Files in this release

File	SHA-256
`toolsenabled-site-studio-0.1.7.zip` (extracts to `site-studio/`)	`3708d46b3433081197be760b167da24c753e493e62cdc24b8146eb4f5ea3f1b8`
`toolsenabled-site-studio-0.1.7.zip.sha256`	the line above, `sha256sum -c` format

Verify, then extract:

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

What changed since 0.1.6

This release fixes the five findings of a code review of 0.1.6.

Links written without quotes and ending in / keep their target. In <a href=/blog/>, common in minified site output, Site Studio took the last / as the end of the tag. Setting an attribute on such a link changed its target from /blog/ to /blog, removing it left its closing </a> behind, and setting its text failed with "node is not paired". It now reads such tags the way browsers do. Tags that really end in /, such as <br/> or <img src="a.png"/>, are read as before.
Undo keeps working on large sites. Each undo state is a full copy of the site, and with 24 MiB or more of files a single edit used to leave the dashboard with no Undo and no warning. Older undo and redo states are still dropped first to keep the saved state near 96 MiB, but the newest undo and the newest redo state now stay. They are dropped only when the saved state would otherwise exceed its 128 MiB limit, and then the result of that edit or action, and the dashboard, say so (undoPruned).
SVG drawings display as image files. When the source given to web_draw leaves out the SVG namespace, xmlns="http://www.w3.org/2000/svg" (and xmlns:xlink when xlink:href is used) is added to the root. Before, such a file was accepted and then showed as a broken image in the preview and in the exported site.
A checkpoint can no longer be named original (in any letter case), because changes original means the opened working copy. Before, a checkpoint with that name could not be chosen in the changes view. A saved checkpoint that already has the name is shown as "Imported checkpoint".
A first start that was cut off no longer blocks the state folder. If the very first start in a new state folder was killed before it saved its state (for example by a power loss), the next start used to refuse the folder as not empty until it was cleaned by hand. It now removes the half-written working copy and temporary state file, with a one-line notice, but only when they hold nothing but a copy of the site; anything else is refused and kept as before. doctor names such leftovers instead of reporting a non-empty folder.
Tool names, inputs, descriptions and annotations are unchanged from 0.1.6. Apart from the doctor row and the dashboard notice described above, the views, the /site-studio pane and export are unchanged too.

What is in 0.1.7

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.

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. 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. Eight new tests check the fixed behavior; all eight fail on 0.1.6 and pass on 0.1.7. A ninth checks the time budget of the one new text pattern. 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.7 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

ToolsEnabled Site Studio 0.1.6 (beta) Pre-release

Pre-release

ToolsEnabled-Inc released this 13 Oct 13:18

v0.1.6

1a3f777

ToolsEnabled Site Studio 0.1.6

Published 2026-10-13. Source commit 1a3f777 on main, tag v0.1.6.

Files in this release

File	SHA-256
`toolsenabled-site-studio-0.1.6.zip` (extracts to `site-studio/`)	`64706ddfcb9e342f6f3a2cca905bef597a44b6668152459262005220eaaf6b2f`
`toolsenabled-site-studio-0.1.6.zip.sha256`	the line above, `sha256sum -c` format

Verify, then extract:

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

What changed since 0.1.5

The test runner (node tools/run-tests.js) checks TMPDIR before it starts any test and stops with a message that names the problem. TMPDIR must be the absolute real path of an existing folder, not one reached through a symbolic link, and at most 62 bytes long. Before, a longer TMPDIR made Chrome exit because its lock socket path did not fit the Unix limit, and the fifteen browser tests failed with a bare read ECONNRESET; a relative or linked TMPDIR made the working-copy store refuse its copy with symbolic link refused, a deliberate guard, in many tests. The browser helper repeats the length check when a browser test file is run on its own.
The README's development section and docs/TESTING.md say how to set TMPDIR for the tests, for example TMPDIR=/tmp/ss, and why. A new test checks that the runner stops on each kind of unusable TMPDIR.
The plugin itself is unchanged from 0.1.5: the MCP server, its tools and annotations, the views, the /site-studio pane and export behave exactly as before.

What is in 0.1.6

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.

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: 266 tests, 0 failures, on Linux with Node 22.19.0, Google Chrome 154 headless for the fifteen browser tests and a short, real TMPDIR. 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.6 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

ToolsEnabled Site Studio 0.1.5 (beta) Pre-release

Pre-release

ToolsEnabled-Inc released this 13 Oct 11:07

v0.1.5

a79d870

ToolsEnabled Site Studio 0.1.5

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

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.

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/).

Assets 4

ToolsEnabled Site Studio 0.1.4 (beta) Pre-release

Pre-release

ToolsEnabled-Inc released this 13 Oct 06:34

v0.1.4

3fe105d

ToolsEnabled Site Studio 0.1.4

Published 2026-10-13. Source commit 3fe105d on main, tag v0.1.4.

Files in this release

File	SHA-256
`toolsenabled-site-studio-0.1.4.zip` (extracts to `site-studio/`)	`7d39f6b1d6d6d6a77e805cac47291a5b36d1fbb0aee908be16be876d957445b9`
`toolsenabled-site-studio-0.1.4.zip.sha256`	the line above, `sha256sum -c` format

Verify, then extract:

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

What changed since 0.1.3

Startup refuses a missing --export-dir parent folder before creating any state. An existing destination is still checked when the human confirms export, so a server can restart after an export.
The changes view names its baseline (the latest checkpoint by default, a named checkpoint, or original) and says when nothing changed since it; the README, install guide and skill tables say the same.
Non-absolute folder paths are refused on Linux and macOS with "requires an absolute path (expand ~ in your terminal first)"; the drive-or-share wording appears only on Windows.
The repository is its own plugin marketplace for Claude Code (.claude-plugin/marketplace.json) and Codex (.agents/plugins/marketplace.json); both files ship in the archive and the README gives the install commands. The Codex plugin is now named toolsenabled-site-studio like the Claude manifest, with homepage, repository and license fields; its skill name is toolsenabled-site-studio:toolsenabled-site-studio.
SECURITY.md carries the company-wide security policy and safe harbor above this release's security boundaries.
The README and install guide give the literal verify-and-extract steps, CHANGELOG dates the 0.1.3 entry (published 2026-10-13), and docs/TEST-REPORT.md records the 0.1.3 and 0.1.4 full-suite runs.

What is in 0.1.4

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, which now requires its parent folder to 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 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, 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, codex plugin marketplace add ToolsEnabled/toolsenabled-site-studio. Public plugin directories are not used.

What was tested

The full Node test suite passed on the release source and again on the files extracted from the ZIP above (264 tests, 0 failures, Linux, Node 22.19.0, Google Chrome 154 headless for the fifteen browser tests) on 2026-10-13. 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 claude plugin marketplace add plus claude plugin install toolsenabled-site-studio@toolsenabled-site-studio from a local clone succeeded in a scratch configuration with the plugin's MCP server connecting; 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

ToolsEnabled Site Studio 0.1.3 (beta) Pre-release

Pre-release

ToolsEnabled-Inc released this 13 Oct 04:42

v0.1.3

cb5631d

ToolsEnabled Site Studio 0.1.3

Published 2026-10-13. Source commit cb5631d on main, tag v0.1.3.

Files in this release

File	SHA-256
`toolsenabled-site-studio-0.1.3.zip` (extracts to `site-studio/`)	`bbe6de3d2abc34e8203f8e66bd6b2e6789789c0fe242ebc3da6b57758fea392b`
`toolsenabled-site-studio-0.1.3.zip.sha256`	the line above, `sha256sum -c` format

Verify, then extract:

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

What is in 0.1.3

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. 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 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. Marketplace and directory distribution remain deferred.

What was tested

The full Node test suite passed on the release source and again on the files extracted from the ZIP above (264 tests, 0 failures, Linux, Node 22, headless Chromium available for the browser tests) on 2026-10-12. Without a Chrome or Chromium named by SITE_STUDIO_CHROME, the 15 browser tests fail rather than skip; 0.1.4 states this in docs/TEST-REPORT.md. Native installation, real interactive pane behavior, marketplace/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

ToolsEnabled Site Studio 0.1.2 (beta) Pre-release

Pre-release

JoshuaPinckard released this 02 Oct 04:38

v0.1.2

d402953

ToolsEnabled Site Studio 0.1.2 (beta) is a reliability and packaging update to the static-site editor that any MCP agent can drive while you watch. Your original folder stays unchanged until you confirm an export. MIT licensed. This is a prerelease, published only here on GitHub Releases. It is not listed in any plugin marketplace or directory.

What changed

Crash recovery without manual cleanup. If Site Studio exits abnormally, the next start removes the leftover lock file (lease.json) itself and prints one line saying so. It does this only when the lock came from the same platform, the same hostname and, on Linux, the same PID namespace, and only after the process ID and the operating system's process start time (plus the boot ID on Linux) show the old process is gone. A Site Studio that is still running always keeps its lock, including across time zones, containers and several restarts at once. When a lock can't be verified, startup refuses and names the lock file and process ID. On Windows the check runs PowerShell from its full System32 path, never from the current folder or PATH.
Hidden attribute text previews correctly. Titles, alt text and other attribute values that use old-style references without a semicolon (&copy 2024, &#169) now preview the way browsers show them. This was checked against real Chromium. Export keeps your original bytes.
Large and dense pages preview. Preview work has firm limits (8 MiB of output, 2 MiB of decoded SVG text, 64 KiB per attribute). If a single attribute is too large, for example a big inline image, only that attribute is left out and the dashboard tells you. If a whole page can't be previewed, the dashboard says that too.
The two 0.1.2 items from 0.1.1's known limits are fixed. A long rejected search no longer stalls Site Studio for about 10 seconds per 2 MiB file; the case described for 0.1.1 now takes under a second. A small hostile SVG with expanding entities no longer uses a lot of memory: the tested 10 KB file now stays under 128 MiB, down from about 850 MiB.
Dashboard sessions. Renew dashboard session replaces the link and revokes the old link, session and preview access, and the current tab stays signed in after a reload. Move to another browser gives you a link to open elsewhere. If another local program interferes with preview cookies, Site Studio repairs them automatically twice, then offers Refresh preview.
Claude Code plugin packaging. The archive now contains a Claude Code plugin manifest with three folder settings (site, private state and export) and a workflow skill, next to the inline Codex manifest. For this release, register Site Studio for a single project with claude mcp add --scope local, as shown in docs/CLAUDE-INSTALL.md. That guide also says where each host logs the one-time dashboard link. Folder settings must be absolute paths; relative paths and ~ are refused.
A builder for an unsigned Claude Desktop bundle is included. No Desktop bundle is published, because native Desktop installation is not yet qualified.

Get started

Download toolsenabled-site-studio-0.1.2.zip and toolsenabled-site-studio-0.1.2.zip.sha256, then run sha256sum -c toolsenabled-site-studio-0.1.2.zip.sha256.
With Node.js 22 or later (no npm install), extract the ZIP and print the registration for your agent:
node tools/mcp-config.mjs --client claude|codex|cursor|claude-desktop|deepseek --site /absolute/path/to/static-site --data-dir /absolute/path/to/private-state --export-dir /absolute/path/to/new-folder
It only prints; it changes nothing. For Claude Code, run the printed command from your site's project directory.
Before giving the agent any work, open the one-time dashboard link from Site Studio's startup log yourself (docs/CLAUDE-INSTALL.md lists where each host writes it). Then ask, for example: "Read the site, update its headline, add a section, and show me the preview."

Tested on this exact release (source commit d402953, tag v0.1.2; ZIP SHA-256 b70970229c3f2697d571d50d5aaa462a3a47fad73691daa1edcde87a4573d2b5)

228 of 228 tests passed headless on Linux, from this public source and from the extracted ZIP.
The ZIP rebuilds byte for byte from this public source.
Plugin loading, no model calls: Codex 0.158 installed this exact ZIP as a plugin into a fresh, empty profile. It listed all 16 tools and used the configured site and state folders. Claude Code 2.1.287 validated the plugin manifest and started the server with the configured folders.
Real agents, through MCP only: on an earlier 0.1.2 candidate, Claude Code, Codex and DeepSeek Harness each read and edited the sample site and saved a checkpoint. The original folder was unchanged. Later changes (crash recovery, dashboard renewal, Windows path checks and docs) were verified without model calls.
Independent security review of every change since 0.1.1, over five review rounds: no open finding at Medium severity or above.

Known limits

Only Linux was tested. Native Windows and macOS are not qualified; their crash-recovery paths were exercised only by simulating them on Linux. On Windows, SystemRoot must be a full path, and PowerShell must be in its standard System32 folder.
Locks from older versions need one manual step. A lease.json left by a crash of Site Studio 0.1.1 (or an earlier 0.1.2 preview) doesn't record where it came from, so 0.1.2 won't remove it. Startup refuses and names the file and process ID. Make sure no Site Studio process is still using that state folder, then delete only that lease.json and restart. Your working copy and checkpoints are kept. 0.1.1 needed the same step.
The same manual step applies on a Mac whose hostname changed after a crash, for example after joining another network.
The packet checker for maintainers (tools/handoff.py) doesn't look inside some rare compression formats (LZMA-alone, lz4, lzip, .Z, brotli). It can also wrongly refuse ordinary text that looks like zlib data. Site Studio itself is not affected.
An extreme search can still pause Site Studio for a few seconds.
The preview runs no scripts. It doesn't render entity-based styles in some Illustrator SVGs, and it drops a tag that contains an invalid numeric character reference. Export keeps your original bytes.
Another program on the same computer can interfere with preview reads. It cannot read the preview or use the dashboard.
A process running as the same user can act as you. See SECURITY.md.

ToolsEnabled is not affiliated with or endorsed by Anthropic, OpenAI, DeepSeek, Cursor or NVIDIA.

Assets 4

ToolsEnabled Site Studio 0.1.1 (beta) Pre-release

Pre-release

JoshuaPinckard released this 01 Oct 20:54

v0.1.1

1cc56ba

Superseded by v0.1.2. Use 0.1.2 for new installs.

ToolsEnabled Site Studio 0.1.1 (beta) is a security and fidelity update to the static-site editor that any MCP agent can drive while you watch. Your original folder stays unchanged until you confirm an export. MIT licensed.

What changed

No secrets in preview URLs. Preview pages are now read with an HttpOnly, SameSite=Strict cookie that is issued only after the dashboard session is authenticated. Dashboard controls still require the dashboard's own session header. A cookie alone never authorizes pause, undo, restore or export. This closes the remaining preview referrer leaks from 0.1.0, including those under --allow-external.
Safer preview rewriting. Every opening tag in the preview is rebuilt and raw text is escaped, so hidden markup in attribute values can no longer change preview behavior.
SVG previews render correctly. SVG files are parsed as XML, so CDATA style sections and bounded internal DOCTYPE entities (as in Illustrator exports) now display.
Better search and CSS edits. web_find finds whole-character matches after a rejected case-folding candidate and never returns an offset inside a surrogate pair. Dense Unicode text searches faster. CSS rule edits respect escaped delimiters in selectors.
Legacy pages preview faithfully. Legacy doctypes and named entities are preserved in the preview. Exports always keep your original bytes.
Docs match the code. README, DESIGN and SECURITY now describe the preview protections accurately.

Get started

Download toolsenabled-site-studio-0.1.1.zip and toolsenabled-site-studio-0.1.1.zip.sha256, then run sha256sum -c toolsenabled-site-studio-0.1.1.zip.sha256.
With Node.js 22 or later (no npm install), extract the ZIP and print the registration for your agent:
node tools/mcp-config.mjs --client claude|codex|cursor|claude-desktop|deepseek --site /path/to/static-site --data-dir /path/to/private-state --export-dir /path/to/new-folder
It only prints; it changes nothing.
Ask your agent, for example: "Read the site, update its headline, add a section, and show me the preview." Open the one-time dashboard link from Site Studio's startup output to watch, pause, undo and export.

Tested on this exact release (source commit 1cc56ba, tag v0.1.1; ZIP SHA-256 e1a9719214e06b8c30cefdbe5d8f90df2f16f50433d5a1bc147cd7b6758191f9)

183 of 183 tests passed headless, from source and from the extracted ZIP.
The ZIP rebuilds byte for byte from this public source.
Real agents, through MCP only: Claude Code, Codex and DeepSeek Harness (DeepSeek V4.1 Flash through NVIDIA's OpenAI-compatible endpoint). Each one listed pages, read index.html, changed the headline, inserted a section, added a CSS rule and saved a checkpoint. The original folder was unchanged.
Independent security review of every change since 0.1.0, including the new cookie design: nothing at Medium severity or above.

Known limits

Two Low availability issues are planned for 0.1.2. One very long rejected search can make Site Studio unresponsive for about 10 seconds per 2 MiB file. A small hostile SVG with expanding entities can use a lot of memory while its preview renders. Neither one can read, change or control anything.
Another program on the same computer can block preview reads. It cannot read the preview or use the dashboard.
The preview runs no scripts and may not render some escaped CSS URLs. Export keeps your original bytes.
Only Linux was tested for this release; Windows and macOS are not yet separately qualified.
A process running as the same user can act as you. See SECURITY.md.

ToolsEnabled is not affiliated with or endorsed by Anthropic, OpenAI, DeepSeek, Cursor or NVIDIA.

Assets 4

Releases: ToolsEnabled/toolsenabled-site-studio

Release list