Skip to content

ToolsEnabled Site Studio 0.1.3 (beta)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@ToolsEnabled-Inc ToolsEnabled-Inc released this 13 Oct 04:42
· 21 commits to main since this release
v0.1.3
cb5631d

ToolsEnabled Site Studio 0.1.3

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

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

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, 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
Loading