Skip to content

ToolsEnabled Site Studio 0.1.4 (beta)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@ToolsEnabled-Inc ToolsEnabled-Inc released this 13 Oct 06:34
· 19 commits to main since this release
v0.1.4
3fe105d

ToolsEnabled Site Studio 0.1.4

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

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

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

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
Loading