Repository navigation
Claude Workflow 0.2.3
Important
Superseded by Claude Workflow v0.2.4. Install v0.2.4 unless you are reproducing older behavior.
Claude Workflow 0.2.3 makes optional shared-gateway upgrades deterministic across shells and working directories.
What changed
- Runtime revisions now follow the gateway's configuration precedence and track installed sources, the selected Node.js and Codex executables, and the effective Codex home instead of the literal
PATH. - Equivalent shell environments and comment-only configuration edits keep a healthy daemon running. Meaningful changes to executables, configuration, credentials, providers, or gateway policy still mark it stale.
- Shared Codex catalog probes and app-server processes use the managed state directory as their deterministic working directory.
setup --sharedfails before startup when a cwd-relativePATHwould select a different Codex executable. Set an absoluteULTRATHINK_GATEWAY_CODEX_COMMANDfor a stable repo-local wrapper.- The README and setup guidance have been rewritten for a standalone audience, including Linux/WSL notes and a bounded coverage procedure for very large files and diffs.
- Lifecycle-free GitHub installation introduced in v0.2.2 remains intact.
Install or upgrade
npm install --global --allow-git=root \
git+https://github.com/yshaaban/claude-workflow.git#v0.2.4
claude-workflow setupSetup reconciles an already-running owned shared gateway and leaves a stopped gateway stopped. Pass --shared to start it explicitly.
Shared-mode users on v0.2.2 should upgrade. The normal per-session launcher is unaffected by the false-stale condition. npm registry publication is not required.