CLI 0.2.3
2026-09-01 · Tag @steamharness/cli/v0.2.3 · npm
New Features
- Local MCP endpoint:
steamharness mcp <workflow-dir>exposes every entrypoint as a standard stdio MCP tool. - Related project access:
--related-projectexplicitly enables mutually confirmed related-project KV access. - MCP lifecycle reporting: hosted by the headless Desktop launcher, the CLI reports complete snapshots over dedicated IPC. See CLI.
Breaking Changes
- The
--grant-data-accessand KanbandataSourcesgrant flows are removed. Migration: project-group dependencies now come from mutually confirmedsteamHarness.projectInfo.relatedProjects. workspace upload --createrequires a predeclared top-level UUID anddataStorage.mode. Migration: Server no longer assigns or writes back project IDs.
Added
- Added
steamharness mcp <workflow-dir>, exposing every entrypoint as a standard stdio MCP tool. - Added a repeatable
--related-project <alias>=<absolute-project-dir>option for local runs.
Changed
- Changed local
kv.*andpersistentValue.*to bind directly to the current project instead of a global scope. - Changed headless Desktop-hosted MCP runs to report full lifecycle snapshots for one runId over dedicated IPC.
- Changed stdio stdout to carry only JSON-RPC, keeping input, args, report, stdout, and stderr in the snapshot.
Fixed
- Fixed MCP form elicitation terminating the waiting run and recording a diagnostic on invalid or failed responses.
- Fixed the OpenAI Responses internal runner no longer writing AI SDK compatibility warnings to
stderr. - Fixed
steamharness structurevalidating the completeprojectInfocontract before analysis, exiting1on unsupported fields.