Skip to content

claude-flow

v3.10.45 Bugfix

This release fixes issues for SREs watching stability and regressions.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agentic-ai agentic-framework agentic-workflow agents ai-agents ai-assistant
+14 more
ai-coding ai-skills autonomous-agents claude-code codex harness mcp-server multi-agent multi-agent-systems npm skills swarm swarm-intelligence typescript

Affected surfaces

rbac

Summary

AI summary

Fixed hive-mind permission flags to correctly honor both --dangerously-skip-permissions and --no-auto-permissions.

Changes in this release

Bugfix Medium

`hive-mind --dangerously-skip-permissions` now correctly honors `--no-auto-permissions`.

`hive-mind --dangerously-skip-permissions` now correctly honors `--no-auto-permissions`.

Source: llm_adapter@2026-06-12

Confidence: low

Other Low

Added three regression tests for permissions flag interaction.

Added three regression tests for permissions flag interaction.

Source: granite4.1:30b@2026-06-12-audit

Confidence: low

Full changelog

Patch release shipping the completion of the hive-mind permissions fix from v3.10.44's held PR.

Fix

#2301 — hive-mind --dangerously-skip-permissions now also honors --no-auto-permissions

Background: the arg parser converts kebab-case CLI flags to camelCase and stores only the normalized key. The original predicate in hive-mind.ts read only the kebab form for both the activation and deny halves, so:

  • --dangerously-skip-permissions silently no-op'd (closed #2269 originally)
  • --no-auto-permissions silently no-op'd (uncovered when validating the v3.10.44 batch)

The earlier patch (PR #2301 in JOhnsonKC201's branch) correctly fixed the activation half by accepting both kebab + camelCase keys, but the deny half still missed: the parser does NOT produce noAutoPermissions: true for --no-auto-permissions — it uses yargs-style negation and stores autoPermissions: false.

Net effect of the partial fix: after activation worked, --dangerously-skip-permissions --no-auto-permissions would have skipped permissions anyway — strictly more permissive than the pre-fix state where activation never even fired.

This release adds the third deny clause:

const skipPermissions =
  (flags['dangerously-skip-permissions'] === true || flags.dangerouslySkipPermissions === true) &&
  !(flags['no-auto-permissions'] || flags.noAutoPermissions || flags.autoPermissions === false);

Three new regression tests pin the contract:

  • parser produces autoPermissions: false for --no-auto-permissions
  • predicate denies on the parser-produced shape { dangerouslySkipPermissions: true, autoPermissions: false }
  • autoPermissions: true is NOT a deny signal (only === false is)

Test suite: 9/9 pass. Closes #2269.

Co-authored: @JOhnsonKC201 (original PR), @rvrheenen (reporter who supplied the patch).

Install / upgrade

npx ruflo@latest init        # 3.10.45
npx @claude-flow/cli@latest  # 3.10.45

All three packages (@claude-flow/cli, claude-flow, ruflo) and all three dist-tags (latest, alpha, v3alpha) verified at 3.10.45.

Diff

main…v3.10.44 — PR #2301 plus the release bump.

🤖 Generated with RuFlo

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track claude-flow

Get notified when new releases ship.

Sign up free

About claude-flow

Deploy multi-agent swarms with coordinated workflows.

All releases →

Related context

Beta — feedback welcome: [email protected]