Skip to main content

AxonFlow v7.6.1 Release Notes

Platform patch release. Two user-visible bug fixes around the read-side governance surface; no new endpoints, no schema-breaking changes on existing responses.

This release is the platform companion to a coordinated plugin release shipping the same day:

PluginNew version
Claude Code (axonflow-claude-plugin)v1.1.0
Cursor (axonflow-cursor-plugin)v1.1.0
Codex (axonflow-codex-plugin)v1.1.0
OpenClaw (axonflow-openclaw-plugin)v2.1.0

The plugins expose the platform's read-side governance surface — search_audit_events, explain_decision, list_overrides, create_override, revoke_override — as agent-callable tools and skills, so a Claude Code / Cursor / Codex / OpenClaw agent can use them autonomously during a conversation. See each plugin's integration page for details.

Platform fixes​

POST /api/v1/audit/search returned entries: null on empty result sets​

Empty result sets on /api/v1/audit/search previously serialized as {"entries": null, "count": 0}, which broke any caller that iterated for entry of entries or read entries.length without a null guard. The response now consistently returns entries: [] so naive iteration works. Pre-existing callers that already handled the null case remain compatible — the change is widening (null → empty array), not narrowing.

POST /api/v1/overrides now rejects severity=critical system policies with HTTP 403​

Authentication-bypass, time-based blind SQL injection, stacked DROP/DELETE/UPDATE/INSERT/EXEC, national-ID PII (US SSN, India Aadhaar/PAN, Singapore NRIC/FIN), and financial-PII patterns (credit cards, EU IBANs, US bank account numbers) are no longer overridable. Attempting to create a session override against any of them returns:

HTTP/1.1 403 Forbidden
{"success":false,"error":"Critical-risk policies cannot be overridden"}

Pre-existing active overrides on these policies are revoked at upgrade time as part of the migration that ships with this release.

The handler-side enforcement was already in place but unreachable on shipped systems — every system policy carried allow_override=true regardless of severity, so the 403 path never fired. This patch promotes severity='critical' system policies to risk_level='critical', which engages the existing database trigger and forces allow_override=false. After upgrade, attempts to override a critical-risk policy return 403 instead of silently succeeding.

Plugin compatibility​

The platform's plugin_compatibility payload (returned by GET /health) advances recommended_plugin_version to the new tags shipped alongside this release:

Plugin idMinRecommended
openclawv2.0.0v2.1.0
claude-codev1.0.0v1.1.0
cursorv1.0.0v1.1.0
codexv1.0.0v1.1.0

The min_plugin_version floor is unchanged — pre-W2 plugins (1.0.0 / 2.0.0) continue to work against this platform and emit only an upgrade hint via /health.

Note on internal scaffolding​

The binary additionally contains internal scaffolding for upcoming work — free-tier email recovery and a paid plugin-claim tier. These are not yet wired to any user-facing surface in this release. No new public endpoints, no behaviour change. They activate in a later release when the plugin and operator-facing pieces ship together.

Upgrade​

# Self-hosted Docker users
docker compose pull && docker compose up -d

# AWS Marketplace users
# Update the AXONFLOW_VERSION parameter to 7.6.1 on the running stack

No migration steps required beyond a normal upgrade — migrations 075-078 included in this release run automatically on agent startup. The cascade-revoke of pre-existing overrides on critical-risk policies happens once during migration 076; the operation is idempotent on subsequent runs.

Last updated on