- The launchd wrapper bug — anyone who set up a launchd-managed ruflo daemon before today's ruflo rename (when it was
still installed via claude-flow or @claude-flow/cli) is silently running stale code after every ruflo upgrade. The
fix is to point the wrapper at the bundled path inside ruflo, and ideally to ship a ruflo daemon install-launchd
subcommand that writes the wrapper correctly. This is a generalizable issue, not just my setup.
- v3.5.77 is out — worth checking with him whether 3.5.76/3.5.77 fix Issue A (ESM/createRequire) or Issue B (memory
ignores CLAUDE_FLOW_CWD). If yes, both workarounds in session-start.sh and the wrapper file can be retired and the
open issues closed.
Token-bloat-from-this-cleanup savings: ~10–30K per session (the duplicate @claude-flow/cli is no longer being
registered). Smaller than I originally estimated because most of the registry tokens were actually ruflo's own MCP
tools, not the duplicate. Still a real win, and the daemon-version-alignment is the bigger benefit anyway.
still installed via claude-flow or @claude-flow/cli) is silently running stale code after every ruflo upgrade. The
fix is to point the wrapper at the bundled path inside ruflo, and ideally to ship a ruflo daemon install-launchd
subcommand that writes the wrapper correctly. This is a generalizable issue, not just my setup.
ignores CLAUDE_FLOW_CWD). If yes, both workarounds in session-start.sh and the wrapper file can be retired and the
open issues closed.
Token-bloat-from-this-cleanup savings: ~10–30K per session (the duplicate @claude-flow/cli is no longer being
registered). Smaller than I originally estimated because most of the registry tokens were actually ruflo's own MCP
tools, not the duplicate. Still a real win, and the daemon-version-alignment is the bigger benefit anyway.