Skip to content

Release v0.26.1 - #8438

Merged
kovtcharov-amd merged 1 commit into
mainfrom
kalin/v0.26.1-rc1-prep
Nov 17, 2026
Merged

kovtcharov-amd merged 1 commit into
mainfrom
kalin/v0.26.1-rc1-prep

Conversation

@kovtcharov-amd

Copy link
Copy Markdown
Collaborator

GAIA v0.26.1 Release Notes

Summary

  • Changing the model server, connectors or skills in Settings now takes effect in chats that are already open, including the terminal UI.
  • "Am I free?" no longer says yes when an Outlook meeting's time can't be read.
  • A chat on a cloud model is no longer offered a large local download.
  • After an agent crash, the next message gets a fresh answer instead of the old one continued.
  • 11 PRs merged since v0.26.0.

What's New

  • Settings reach open chats — a model server, connector or skill change applies on the chat's next message, in the Agent UI and the terminal UI. The terminal UI and gaia -p now offer only the MCP servers turned on for GAIA. (PRs #8389, #8394, #8399, #8400)

Bug Fixes

  • Outlook availability is no longer guessed — a meeting whose time can't be read is reported instead of skipped, and Outlook times parse on Python 3.10. (PR #8267)
  • No unwanted local download on a cloud model — Settings › Manage downloads leaves the local chat model unticked while chat runs on a cloud model. (PR #8086)
  • A reply cut short by a crash isn't continued — the next message is answered fresh. (PR #8391)
  • A command's timeout never outlasts the turn's time limit. (PR #8424)
  • An MCP connector shows Connected only after a check has started it. (PR #8434)
  • A document overlap of 0 repeats nothing between chunks. (PR #8382)
  • Closing the resource strip says how to bring it back. (PR #8432)
  • A release candidate names its own pre-release as the agent's source. (PR #8433)
  • The "GAIA doesn't run this model server" line is translated in Arabic. (PR #8435)
  • Relay tests run against fake agents that match the real one. (PR #8393)

Full Changelog

11 PRs since v0.26.0. The PR links above are the changelog.

Full Changelog: v0.26.0...v0.26.1

Bumps GAIA to 0.26.1 for its release candidates and adds the v0.26.1 notes covering the 11 fixes merged since v0.26.0.
@kovtcharov-amd
kovtcharov-amd merged commit 6ff026f into main Nov 17, 2026
82 of 85 checks passed
@kovtcharov-amd
kovtcharov-amd deleted the kalin/v0.26.1-rc1-prep branch November 17, 2026 17:34
@github-actions github-actions Bot added the documentation Documentation changes label Nov 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Skill audit

Skill Verdict Claimed tier Cleared tiers Findings Rules
hub/agents/gaia/npm ✅ ALLOW experimental experimental 3 high body.injection.credential_request, body.injection.guardrail_bypass, body.injection.persona_override

✅ All audited skills cleared the tier they claim.

Per-finding detail is withheld here on purpose. Read it in the Security > Code scanning tab, or download the skill-audit-reports artifact from this run. Offending source text is withheld from CI everywhere — reproduce it locally with gaia skill audit <dir> --show-snippets.

@github-actions

Copy link
Copy Markdown
Contributor

Verdict: Approve with suggestions

This bumps GAIA to 0.26.1 and adds its release notes. Every version field agrees, and the CLI and Agent UI backend both report the new number. One small thing: the notes link three PRs that were closed without merging. Their changes did ship, inside #8400, so the text is right but readers who click those links land on "Closed".

Real-world evidence

The evidence stage ran the CLI and the Agent UI backend from this branch on a runner with no model server:

$ gaia --version
0.26.1
$ curl -s http://127.0.0.1:4200/api/system/status      # selected fields
HTTP 200
{
 "version": "0.26.1",
 "lemonade_running": false,
 "initialized": false,
 "model_loaded": null
}
webui package.json: 0.26.1
package-lock: 0.26.1 0.26.1
hub/agents/gaia/python/gaia-agent.yaml version= 0.3.6 min_gaia_version= 0.26.1
hub/components/terminal-hub/gaia-agent.yaml version= 0.26.1 min_gaia_version= 0.26.1
pyproject deps: ['amd-gaia>=0.26.1']

The version-gate tests passed (120 passed), and the health, settings and sessions routes still returned 200. The evidence stage marked the Agent UI screenshot of the version display as pending the strix-halo lane. That screen is static review only here. The evidence supports the verdict.

🔍 Technical details

Issues

🟢 Release notes link three PRs that were closed, not merged (docs/releases/v0.26.1.mdx:19). #8389, #8394 and #8399 were closed unmerged. #8400 was stacked on them and landed their changes in one squash, so the "Settings reach open chats" claim is accurate and the "11 PRs" count matches git log v0.26.0..HEAD. To keep readers from landing on closed PRs, credit only the merged one:

- **Settings reach open chats** — a model server, connector or skill change applies on the chat's next message, in the Agent UI and the terminal UI. The terminal UI and `gaia -p` now offer only the MCP servers turned on for GAIA. (PR [#8400](https://github.com/amd/gaia/pull/8400))

Checks done

  • Docs drift: the minimum core version moved from 0.26.0 to 0.26.1 in the flagship's gaia-agent.yaml, pyproject.toml, npm README, SKILL.md and CHANGELOG. They all agree now. The remaining 0.26.0 hits in docs/ are history (the shim removal in docs/spec/chat-agent.mdx and the plans in docs/plans/release-train.mdx), so they are not stale.
  • The flagship package stays at 0.3.6, and the new requirement sits under [Unreleased] in the CHANGELOG. Published 0.3.6 is not rewritten.
  • docs/docs.json adds the new page to the nav and updates the navbar label.

Strengths

  • Every version field across core, the webui, the terminal-hub component and the flagship manifest moves together, and the evidence confirms it.
  • The release notes lead with what users will notice, not with how it was built.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Documentation changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant