ToolsEnabled Slides 0.1.8 (beta)

ToolsEnabled Slides 0.1.8 (beta)

Published 2026-10-13. Source commit 16a404febadfe8dcdc29b822e92a73ab6c9c3416. It adds two commits to 0.1.7 (tag v0.1.7, commit 48178418d15d882ac7aa492c58540b1b98ae04e6): the fixes from the 2026-10-13 fresh-user re-test of 0.1.7, and the version change. The tools, studio, panes and the Claude Code and Codex plugin manifests are unchanged; one startup line of the server changes.

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

• A start of a workspace whose deck model exists but whose presentation.pptx is missing (a client's health check can stop the first start before its first render) now logs presentation.pptx is missing, rendering it for rev N to stderr. creating the initial presentation.pptx is printed only when the deck itself is new. Nothing else about the start changes; test/js/first-boot.test.js pins both lines.
• README no longer says that agent file tools can read the one-time studio link "even from mode-600 logs". The log's mode depends on the MCP host and your umask: Claude Code 2.1.296 wrote it as mode 644 under umask 022, readable by every local account. Open the link promptly, before assigning agent work, and never ask the agent to retrieve it. test/js/readme-studio-link.test.js pins the wording.
• test/js/dashboard-browser-session.test.js failed on a busy machine and passed alone: each of its waits (a real Chromium start, page loads, server state) allowed 10 s. The waits now go through test/helpers/until.js, 30 s each by default; SLIDES_TEST_WAIT_MS sets another deadline, and a wait that never holds names what it waited for. The checks are unchanged. test/js/until-helper.test.js covers the helper, and docs/TESTING.md describes the setting.
• tools/source-files.json lists the three new test files, so the source ZIP has 228 members (0.1.7: 225).

Files in this release

File	SHA-256
toolsenabled-slides-0.1.8.zip (677,411 bytes, the source distribution)	816c1b1f1e6b6719f3904103529beebcd3dc0389e488d57669dba22379421e95
toolsenabled-slides-0.1.8.zip.sha256	the line above, sha256sum -c format

Verify before extracting:

sha256sum -c toolsenabled-slides-0.1.8.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.8 (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.8. 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 install from the toolsenabled-slides marketplace in the /plugins browser (Codex). Both need the external runtime prepared as docs/CLAUDE-INSTALL.md describes.

What was tested

Full Linux suite on the release commit: FILES 112; FAILED 0; DISPLAY=unset, exit 0 (111 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: 154 node:test tests, 127 Python tests (6 Windows-only skips) and 692 scripted checks, all passing. Before the change, on the same machine, 0.1.7 gave FILES 110; FAILED 0; DISPLAY=unset with 149 node:test tests, 127 Python tests (6 Windows-only skips) and 692 scripted checks; the difference is the two new test files (five node:test tests). 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 112; 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, 37 discovered tools, 3 PPTX slides and real PPTX, PDF and PNG exports. 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, 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.8 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. Codex was not run for this release; its manifest is unchanged from 0.1.7. No native Windows/macOS/Desktop or production certificate trust is inferred.

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