Release Notes: AiAxis v3.1.5 Hotfix

TL;DR

A targeted hotfix deployed on April 7, 2026 resolves an issue where some users could not see, edit, or interact with their AI agents after an identity migration. All affected users regain immediate access with no data migration or downtime required.

Bug Fixes

Agent Visibility for Users with Duplicate Identity Records

A subset of users were unable to see, edit, or interact with their AI Agents after a platform identity migration created multiple login records for the same person. Because agent sharing was previously tied to a specific login identifier, users authenticating under a newer identity could no longer find agents linked to their earlier account.

What changed: All agent permission lookups now resolve identity at the user level rather than the login level. The system looks up every identifier belonging to the same person and treats them all as equivalent, so your agents are always visible regardless of which login you use. A fallback ensures users on legacy account configurations are completely unaffected.

The fix applies across all agent-related operations, including:

  • Agent list and single agent fetch
  • Ownership verification and creator agents
  • Workspace agents and public agents
  • Permission reads, bulk permission checks, and relation checks
  • Permission removal

What This Means for You

For All Users: If you experienced missing agents after a recent login change or account update, your full agent library is now restored and accessible. No action is required on your end — the fix is live in production and takes effect immediately.

For Teams & Admins: Agent sharing and permissions are fully intact. Shared agents are visible to all intended recipients, and no access grants need to be re-applied. Your Advanced AI Agents workspace is operating as expected.

Related Resources

More Like This...