Meta Proxy v0.4.0 — signed routing sidecar for MetaHarness and Ruflo

META_PROXY_V0_4.md

Meta Proxy v0.4.0 is available

Meta Proxy v0.4.0 is a signed, local Claude-compatible routing sidecar for Cognitum workflows. It now ships through both MetaHarness and Ruflo.

Quick start

# MetaHarness: install the optional signed sidecar
npx metaharness@latest proxy install --yes

# Ruflo: install the signed v0.4.0 proxy by default
npx ruflo@latest proxy install --yes

# Authenticate with Cognitum OAuth when cloud routing is needed
npx ruflo@latest proxy login

Per-worktree routing policy

MetaHarness can launch a Claude-compatible client through Meta Proxy with an explicit policy. This is useful for separate Ruflo worktrees, temporary agent worktrees, and agent herds with different task importance.

npx metaharness@latest proxy run --policy critical -- claude
npx metaharness@latest proxy run --policy standard -- codex
npx metaharness@latest proxy run --policy economy -- claude

Policies are scoped to the invoked workspace and are forwarded as authenticated routing capability metadata. There is no routing banner.

What is verified

• The signed Meta Proxy v0.4.0 Windows binary release is public.
• ruflo@3.32.4 defaults proxy install --yes to Meta Proxy v0.4.0.
• A fresh public-package acceptance run downloaded and SHA-verified the v0.4.0 binary in an isolated Windows profile.
• metaharness@0.4.0 includes the optional signed sidecar installer, Cognitum login/logout, and critical/standard/economy launch policies.
• @claude-flow/cli@3.32.4 now builds its compiled distribution before publishing, preventing missing-entrypoint releases.

Releases

• Meta Proxy source: https://github.com/cognitum-one/meta-proxy/releases/tag/v0.4.0
• Signed distribution: https://github.com/cognitum-one/meta-proxy-dist/releases/tag/v0.4.0
• Ruflo: https://github.com/ruvnet/ruflo/releases/tag/v3.32.4
• MetaHarness integration: ruvnet/metaharness#144

Security

Installers obtain a release-specific checksum and verify the signed distribution before accepting the binary. Cloud routing remains opt-in and Cognitum OAuth tokens stay in the operating-system keychain.