Skip to main content
Airia releases periodic updates to Airia Agent that add new capabilities, improve reliability, and update the underlying models and pipeline logic. As an administrator, you control when your tenant applies these updates.

​
Check for available upgrades

When a new version of Airia Agent is available, a notification banner appears at the top of Settings → Airia Agent. The banner shows:
  • The current version your tenant is running
  • The version available to upgrade to
  • A cumulative changelog listing everything that has changed since your current version
You can also navigate to the Version section of the settings page at any time to see the current version and check for updates.

​
Before you upgrade

Run through this checklist before applying an upgrade, especially for production tenants:
  • Read the full changelog — note any breaking changes or behavioral shifts
  • Test the current version with your key workflows so you have a baseline to compare against
  • If you have a staging tenant, apply the upgrade there first and verify before promoting to production
  • Identify which tools, sub-agents, and system prompt behaviors are most critical to your users — these are the first things to test post-upgrade
  • Check whether the upgrade introduces MCP placeholder bindings that need to be resolved (see Tools & MCP)

​
Apply an upgrade

1

Review the changelog

Read the cumulative changelog in the banner or in the Version section. Pay attention to:
  • New tools or capabilities being added to Airia Agent’s default behavior
  • Changes to how existing tools or sub-agent invocation work
  • Any breaking changes or behavioral shifts that may affect your users
2

Apply the upgrade

Click Upgrade. The platform applies the update in place. Airia Agent remains available to users throughout the upgrade — there is no downtime.
3

Verify behavior

After the upgrade, test Airia Agent with the key workflows from your pre-upgrade baseline. Pay particular attention to tools and capabilities mentioned in the changelog.
Upgrades cannot be rolled back through the admin interface. There is no self-service way to revert to a previous version after an upgrade is applied. If a breaking change is discovered post-upgrade, contact Airia support — they can assess options on a case-by-case basis.

​
What is preserved across upgrades

ConfigurationPreserved?
Custom system promptYes — automatically retained
Tool configuration (which tools are connected)Yes
Per-tool enable/disable stateYes
MCP server connectionsYes
Sub-agent configurationYes
Access mode and user/group assignmentsYes
Fallback agent selectionYes
Compute sandbox user assignmentsYes
Skills RepositoriesYes — repositories are project-scoped and unaffected
The only things that change during an upgrade are the base pipeline logic, built-in capabilities, and the underlying model configuration that Airia manages.

​
What changes during an upgrade

Upgrades may include:
  • New built-in capabilities — for example, a new reasoning mode or improved context handling
  • Model updates — the underlying AI model may be updated to a newer version
  • Pipeline logic changes — how tool calls are sequenced or how responses are synthesized may change
  • Bug fixes — behavioral fixes that change how Airia Agent handles edge cases
All of these are detailed in the changelog before you apply the upgrade. Check for upgrades once a month. Apply them promptly — updates often include security improvements and capability enhancements that benefit users immediately. If your organization has compliance or change-management requirements that govern when software updates can be applied, plan upgrade windows accordingly. Airia does not force upgrades; your tenant stays on its current version until you apply an update.