ToolsEnabled Slides 0.1.3 (beta)

ToolsEnabled Slides 0.1.3 (beta)

Published 2026-10-13. Source commit 49ce1ce7d507586a62fc18dee0ee04ff999c67a6, three commits on top of the public main 7850ed3a4b30e56bbb7212c9bb804c5123cebc47 (the 0.1.2 release plus the plugin-directory preparation).

This release provides Linux presentation editing over MCP, a local live studio, read-only Claude panes and Codex CLI views, slide locks, human dashboard controls, and PPTX/PDF/PNG export. Linux is the supported release scope. Native Windows shutdown, macOS, trusted production signing and native Desktop installation remain unqualified.

The MCP host supplies the agent. Slides does not make model calls or require a built-in online account or API key. The source ZIP contains no wheels, copied runtimes, workspace data, signing keys or packaging evidence. Prepare the Python runtime explicitly; Linux PDF/PNG also require LibreOffice.

Changes since 0.1.2 (see CHANGELOG.md):

• Every one of the 37 MCP tools declares a plain title and the readOnlyHint, destructiveHint, idempotentHint and openWorldHint annotations, reviewed against each tool's handler. Eight tools only read; the other 29 are marked destructive, ten of them newly and conservatively (ppt_add_*, ppt_note, ppt_lock, ppt_unlock, ppt_task_done, ppt_export: an edit clears redo and can drop the oldest undo state, a board post can drop old agent messages, an export trims its receipt list; an export still never overwrites a file). No tool reaches beyond this computer. Tool names, inputs and behavior are unchanged; docs/MCP.md lists the rules.
• Claude Code starts the MCP server as node ${CLAUDE_PLUGIN_ROOT}/slides-mcp.js, with the settings passed as environment variables and the same strict plugin-mode startup as the Codex manifest. The node on the PATH that Claude Code runs with must be Node.js 22 or newer; node_executable is still the Node.js the /slides panes run.
• The start-up error for a missing workspace no longer says "the Codex plugin".
• The repository carries the plugin directory's listing icon, and the source ZIP includes it.
• README: a new section, "What this plugin runs, sends and reads", lists the programs the plugin starts, what it reads and writes, what it sends and where, and the events the /slides mod handles. The install command shows the four required settings.
• The Claude plugin manifest names the documentation, privacy (https://toolsenabled.ai/privacy/) and support (https://toolsenabled.ai/support/) pages, and the Claude, Codex and Desktop manifests use https://toolsenabled.ai/slides/ as the homepage.
• Tests that start the server or the CLI next to placeholder hosts pass the child only the operating-system basics and the suite's own settings; new tests start the server exactly as .mcp.json does and pin every tool's annotations.

Files in this release

File	SHA-256
toolsenabled-slides-0.1.3.zip (659383 bytes, the source distribution)	e97aa22738642d1ffc33a70bf6c5a83187531bfb87780c01cf988d7a8adadc22
toolsenabled-slides-0.1.3.zip.sha256	the line above, sha256sum -c format

Verify before extracting:

sha256sum -c toolsenabled-slides-0.1.3.zip.sha256

The offline Python wheel bundle that README and docs/CLAUDE-INSTALL.md use is unchanged since 0.1.0 and is not re-attached here. Use the 0.1.0 asset, which works with 0.1.3 (same six pins): toolsenabled-slides-0.1.0-cp312-linux-x86_64-wheels.zip, SHA-256 a29454931420b8d9547eeb8d17c389a005cf0343a927d7a275f15eb3cab25fec.

No Claude Desktop bundle (.mcpb) is distributed with 0.1.3. An MCPB manifest is included in the source for future Desktop qualification; registry metadata and directory publication remain held until production-signed bytes and the required qualification are verified.

Plugin installation: claude plugin marketplace add ToolsEnabled/toolsenabled-slides, then claude plugin install -s local toolsenabled-slides@toolsenabled-slides --config python_executable="/absolute/private/Slides Runtime/bin/python" --config node_executable=/absolute/node --config workspace_directory="/absolute/decks/Project Update" --config port=4599 (Claude Code, with Node.js 22 or newer on its PATH; without the Python and workspace settings the plugin installs but starts no server); codex plugin marketplace add ToolsEnabled/toolsenabled-slides then codex plugin add toolsenabled-slides@toolsenabled-slides (Codex). Both need the external runtime prepared as docs/CLAUDE-INSTALL.md describes.

What was tested

Full Linux suite on the release commit: FILES 107; FAILED 0; DISPLAY=unset, exit 0 (106 direct test files plus fixture generation), with SUITE_PYTHON pointing at a runtime prepared by tools/setup-runtime.py from the 0.1.0 wheel bundle: 140 node:test tests, 127 Python tests (6 Windows-only skips) and 654 scripted checks, all passing. Selected in-suite results: tool annotations 2/2, golden tools/list 2/2, Claude package 6/6, security 10/10. The /slides mod's hook tests (claude plugin test): 33/33.

The same suite from the extracted ZIP (unzip, then node test/run.js inside slides/ with the same prepared runtime): FILES 107; FAILED 0; DISPLAY=unset, exit 0.

Strict real-LibreOffice lifecycle on the extracted ZIP: exit 0, ok: true, 9 named checks (initialize, golden tools/list with the new annotations, locks required, 3-slide MCP editing, attach and detach, real exports, import, EOF shutdown, lease released), 37 discovered tools, 3 PPTX slides, 3 PDF pages and 3 PNG images (1600 × 901 each). This is one strict lifecycle run with its retained exports and stderr, not coverage of every tool.

Marketplace: claude plugin validate --strict passes on the release tree, its plugin.json and its marketplace.json (Claude Code 2.1.296). In a scratch CLAUDE_CONFIG_DIR, claude plugin marketplace add from the clone followed by claude plugin install -s local toolsenabled-slides@toolsenabled-slides with the four settings listed the plugin at 0.1.3, and claude mcp list showed its server connected. The Codex marketplace file follows the published repo-marketplace format; Codex installation from it and the packaged-ZIP Codex host gate (tools/prove-codex-plugin.py) were not run for 0.1.3. No native Windows/macOS/Desktop or production certificate trust is inferred.

Support and security contact: support@toolsenabled.ai (security policy: https://toolsenabled.ai/security/).