ToolsEnabled Slides 0.1.6 (beta)

ToolsEnabled Slides 0.1.6 (beta)

Published 2026-10-13. Source commit 628f9ffb7a8ae9004f6cb1dd9d82070386f65175. It adds two commits to 0.1.5 (tag v0.1.5, commit 402bf1c736c5c59dec729b5470f9187af0aafb14): documentation and test-layout fixes from a review against the Claude plugin directory policy, and the version change. The server, tools, studio and panes are unchanged.

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.5 (see CHANGELOG.md):

• README has a "Try it" section with the shortest path from nothing to a working result: prepare the external runtime from the 0.1.0 wheel bundle, make the folders, install the plugin with its four settings, then three prompts, each with the result it shows: Show me the deck. (one title slide at revision 0), adding a slide titled "Quarterly results" with three bullets (Claude locks s1 first because adding a slide changes the whole deck; two slides at revision 2), and exporting quarterly-results.pptx, a two-slide PowerPoint file in the workspace. No account or API key is needed.
• SECURITY.md says Slides 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 used to give the model the path of the Claude Code log that holds the one-time dashboard link. It now says that the human finds the link in the host's MCP log, as the README explains. The rest of the skill is unchanged.
• test/js/managed-presentation.test.js no longer runs a program itself. The python-pptx helper that writes a user deck moved unchanged to test/helpers/user-deck.js, so the test file that polls the local server over HTTP runs no child process. The test checks the same behaviour as before: with the 0.1.4 code restored it fails the same way.

Files in this release

File	SHA-256
toolsenabled-slides-0.1.6.zip (673146 bytes, the source distribution)	7c727ddba957a4db89b86084a9cfb570c380f84432a21834f3aa8f7f67f9c995
toolsenabled-slides-0.1.6.zip.sha256	the line above, sha256sum -c format

Verify before extracting:

sha256sum -c toolsenabled-slides-0.1.6.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.6 (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.6. 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 110; FAILED 0; DISPLAY=unset, exit 0 (109 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: 149 node:test tests, 127 Python tests (6 Windows-only skips) and 692 scripted checks, all passing. These are the same counts as 0.1.5 on the same machine before the change. The /slides mod's hook tests (claude plugin test): 33/33. With the 0.1.4 code that overwrote a user's presentation.pptx restored in a scratch copy, test/js/managed-presentation.test.js still fails as it did on 0.1.4.

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

Strict real-LibreOffice lifecycle on the extracted ZIP: exit 0, ok: true, 9 named checks (initialize, golden tools/list, 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.

The README "Try it" path, run headless from the extracted ZIP with the server started as .mcp.json starts it: ppt_show returns "Untitled Presentation" at revision 0 with one title slide; ppt_add_slide is refused until s1 is locked, then adds "Quarterly results", and ppt_set_bullets sets the three bullets (two slides at revision 2); ppt_export writes quarterly-results.pptx, which python-pptx reads back as the two slides.

Marketplace: claude plugin validate --strict passes on the release tree, its plugin.json, its marketplace.json and the extracted ZIP (Claude Code 2.1.296). In a scratch CLAUDE_CONFIG_DIR, claude plugin marketplace add of the extracted ZIP followed by claude plugin install -s local toolsenabled-slides@toolsenabled-slides with the four settings listed the plugin at 0.1.6 and printed the expected "2 userConfig options not yet set". claude mcp list showed its server connected. The ZIP was built twice, each in a fresh clone of the release commit, with byte-identical results. 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.6. No native Windows/macOS/Desktop or production certificate trust is inferred.

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