PR: ruvnet/RuView#1387 Announcement page: https://claude.ai/code/artifact/0d3a1b19-b3b0-4a69-be73-183c9e42ce59 Interactive capabilities showcase: https://claude.ai/code/artifact/7dfda175-a64f-4a2a-b01f-f3469d1a85d5
A compiled, PyO3-bound wifi-densepose pip package for passive WiFi-CSI sensing now ships three opt-in SOTA extras, each proven bit-identical to the native Rust core via a SHA-256 parity harness.
Today RuView and Cognitum.one moved two vendor integrations from research into reproducible, simulator-first Rust betas. Both integrations label synthetic data explicitly and stop short of claiming physical-hardware validation before the boards and vendor SDKs arrive.
metaharness@0.3.2 is now available on npm.
Meta-Proxy is an opt-in local Rust sidecar for a loopback, Claude-compatible routing endpoint. It is not bundled into the npm package and is never downloaded during normal harness scaffolding.
npx metaharness@latest proxy install --yes
| # Ruflo v3.32.2 ? stable Codex, hooks, security, and plugin integration update | |
| Ruflo v3.32.2 is a stable release. It contains no alpha tag and is published as `latest` for `ruflo`, `claude-flow`, and `@claude-flow/cli`. | |
| ## Why a release was required | |
| The reported Codex failures came from immutable cached plugin versions and an MCP cold-start budget that was too short: | |
| - `ruflo-core/0.2.2/hooks/hooks.json` and `ruflo-cost-tracker/0.26.0/hooks/hooks.json` could be cached as empty/invalid content, producing `expected value at line 1 column 1`. | |
| - Once hook loading failed, the `ruflo` MCP server could still be launched, but a 30-second Codex startup limit was too short for a cold `npx` resolution and plugin initialization. |
Ruflo v3.32.1 fixes the Codex integration failures that appeared as hook JSON parse errors, incomplete MCP startup, and 30-second startup timeouts?especially on Windows.
Status: research only; no service, harness, cloud resource, or deployment has been created.
Research date: 2026-07-16
Locally verified: metaharness@0.3.1, @metaharness/harness@0.1.0, @metaharness/host-claude-code@0.1.2, @metaharness/host-codex@0.1.2, and codex-cli 0.142.5.
A small, continuously available coding-agent service is feasible with MetaHarness as the generated harness/control-plane layer, a durable job queue, and replaceable Claude Code and Codex execution adapters. The simplest credible GCP topology is an authenticated Cloud Run API plus Pub/Sub and a Cloud Run worker pool kept at one or more instances; the worker pulls jobs, creates a disposable repository workspace, invokes either claude -p or Codex, publishes artifacts and status, and destroys the workspace.
Issue: ruvnet/ruflo#2661 (P0)
Fix: ruvnet/ruflo#2662, shipped starting in @claude-flow/cli@3.27.0
Every Git worktree of a ruflo project started its own autonomous daemon, each daemon independently scheduled three Claude-powered background workers, and nothing coordinated across worktrees — so the number of autonomous Claude launches per hour scaled linearly with worktree count, with no ceiling.
TL;DR: RuVector — an open-source Rust vector database with HNSW indexing, WASM bindings, and Postgres integration — just shipped local (no-API-key) embedding generation via Lattice on both the Rust crate (ruvector-core@2.3.0) and the npm/WASM package (ruvector-extensions@0.1.2), fixed 3 real RustSec CVEs, and turned cargo audit + cargo deny fully green after they'd been failing on main. Full release notes: ruvector-core-v2.3.0.
Most vector-search tutorials assume you're calling OpenAI or Cohere for embeddings. That's fine for a demo, but it means every insert and every query round-trips to a third party, costs money per call, and leaks your data off-box. RuVector's new Lattice integration gives you a CPU-native, pure-Rust embed
Published on 2026-07-08 from branch fix/main-v3-ci-red-shim-types, targeting source commit e09843303232b0199d5c8629ec3bd5e233adc5a7.
Release tracker: ruvnet/ruflo#2614 PR: ruvnet/ruflo#2604
claude-flow@3.25.5