v0.2.0

RoutineKit 0.2.0

Capture a successful tool workflow, save it as a named tool, and replay it with fresh inputs and human approval.

Added

• Explicit local stdio MCP connections with an installed executable, a tool allowlist, and a connection review. No automatic sibling-server configuration or credential import.
• Save as Tool: typed routine_saved_* tools; scoped registration in DSH and dynamic tool discovery in MCP.
• Basic input/argument forms, result-field success checks, binding review, and a SKILL.md + routine.json ZIP download.
• A self-contained MCP Apps workbench. Tested in a browser with the official AppBridge SDK; individual desktop-host support is not claimed.
• A real filesystem MCP demo: write a note, read it back, change the file/content inputs, and check the returned content.
• Official MCP Registry metadata and a manually dispatched GitHub OIDC publishing workflow.

Verification

28 unit/integration tests and 9 browser E2E tests passed locally. The package was installed into an isolated environment, its real MCP stdio server and App resource were loaded, and official DSH 0.1.2-rc.1 installed, opened, discovered tools, and removed the packed plugin using an isolated DSH_HOME/profile/workspace. No existing user profiles or package-age exceptions were changed.

The source CI runs Node 22/24 on Windows/macOS/Linux, with official DSH installation verification on Node 22. Check the linked source run for the exact results.

The GIF/MP4 are actual workbench recordings with scripted calls to the official filesystem MCP server, not autonomous-model task-success claims.

Limits

Reviewed linear workflows and exact scalar bindings only. The workbench is loopback-only. Upstream MCP support is local stdio with structured JSON or one text result, not HTTP/OAuth/sampling/roots/elicitation forwarding. Upstream processes are trusted OS-user code, not sandboxed. Stop waits for the directly launched server to close; independently spawned grandchildren are not guaranteed to stop.

Fresh human approval remains mandatory. An exported routine does not include credentials, existing permissions, example input values, or raw recorded outputs; literal arguments can still contain private data. Review before sharing. DSH-native replay retains host guards; the launch may still use a host model, while the replay engine makes zero model calls.

Install

dsh plugin --profile web add routinekit

Node 22.19+ and DSH 0.1.2-rc.1 are the tested baseline. Wait for your configured package-age window after this release; do not lower it or accept a generated exception. See the README for standalone/MCP usage and the temporary-files tutorial.