# ruflo v3.38.21 — v3.38.21 — MCP HTTP bridge memory-persistence fix

- Product: ruflo (https://whatsnew.fyi/product/ruflo)
- Vendor: ruflo
- Date: 2026-09-02
- Version: v3.38.21
- Original notes: https://github.com/ruvnet/ruflo/releases/tag/v3.38.21
- Permalink: https://whatsnew.fyi/product/ruflo/releases/v3.38.21

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Fixed entries stored via the bridge being unreadable after a bridge restart by correcting initializeMemoryDatabase() to seed the ControllerRegistry singleton with the dedicated agentdb-memory.db path instead of the memory.db path
- **fixed** — Relaxed agentic-flow-agent.test.ts assertion on result.duration from strictly greater than 0 to greater than or equal to 0 to prevent flaking under coarse CI clock resolution

##### Fixed

- **#3155** — `ruflo mcp start -t http`: entries stored via the bridge were unreadable after a bridge restart (`found:false`, `memory_list` empty), even though `.swarm/memory.db` held them and the CLI read them fine. Root cause: `initializeMemoryDatabase()` seeded the process-wide `ControllerRegistry` singleton with the sql.js-facing `memory.db` path instead of the dedicated `agentdb-memory.db` path. Fixed in #3156.
- **#3059** (CI) — `agentic-flow-agent.test.ts` asserted `result.duration` strictly `> 0`; under coarse CI clock resolution a ~1ms task's duration could legitimately read `0`, flaking the test-ratchet gate on `main`. Relaxed to `>= 0`.

##### Known, separately-tracked gap (not in this release)

`@claude-flow/mcp` is pinned to `3.0.0-alpha.10` in root/CLI `package.json` (bumped in the 3.38.20 release commit) but that exact version was never published standalone to npm — only `alpha.9` exists on the registry. This breaks a fresh `npm ci` inside the `ruvnet/ruflo` monorepo itself (confirmed failing on CI). It does **not** affect end users installing `ruflo`/`@claude-flow/cli` from npm, since `@claude-flow/mcp` ships bundled inside those tarballs. Filed for follow-up.