Gaia 3.0 release highlights

Gaia 3.0 spans releases 3.0.0-3.0.47 and is the version where Gaia moved from governed automation inside a project toward a broader operating layer for agentic work across teams, systems, documents, and external channels.

This cycle made the Gaia assistant more useful as an authoring and setup partner, introduced UI layout canvas artifacts, added execution protocols and session tracking, expanded organizations and platform access management, brought collaboration directly into conversations, strengthened document intelligence and grounded citations, and opened more integration paths through MCP tools, service accounts, bridge webhooks, and live chat infrastructure.

Major themes

• The assistant became a stronger authoring partner: entity authoring, bootstrap previews, project-spec patch previews, configuration tools, project setup diagnostics, and project improvement flows make Gaia better at helping teams shape real systems instead of only answering questions about them.
• Governance became more automated and more attributable: governance dashboards, evidence link previews, package import details, operations review posture, governance agent management, operational logs, project-level tool access, and clearer execution principals make oversight easier to operate.
• Organizations and access became first-class platform surfaces: organizations, organization roles, platform users, platform roles, service accounts, multiple API keys, guest login, anonymous sign-in, and stronger permission enforcement give administrators a clearer control plane.
• Conversations became collaborative workspaces: participants, mentions, agent reactions, discussion mentions, assistant reviews, PDF transcript downloads, timestamps, task run approvals, and continuation flows make conversation history easier to share, review, and act on.
• Document intelligence became more grounded and inspectable: document knowledge folder attachments, structure search, richer index inspection, PDF retrieval improvements, advanced folder file settings, and inline citations make source-backed answers easier to trust.
• Integrations moved closer to operations: MCP tool integration, GitHub Copilot and Gaia Automation support, bridge agent webhooks, channel bindings, advanced handoff rules, the Genesys Live Chat Bridge, and signed live chat events extend Gaia beyond its own interface.
• Visual and embedded experiences matured: UI layout intent routing, canvas artifacts, text decoration support, portal frame previews, mobile Messages and Canvas tabs, portal embed setup, custom launcher images, and configurable chat behavior make Gaia easier to embed and tailor.

Notable additions

• Entity authoring skill and project setup previews help teams move from a rough business request to inferred entities, relationships, workflows, folders, and safer setup choices before committing changes.
• UI layout canvas artifacts let agents produce structured visual layouts inside conversations, with persistence, validation, grading support, and a clearer path from discussion to usable interface.
• Execution protocol registry and agent execution sessions give agents lifecycle stages, checkpoints, structured outputs, and real-time session state that operators can inspect during work.
• Organizations, roles, and platform user management create a more complete administration layer for multi-team Gaia usage.
• Service accounts and MCP tool integration give non-human principals and external tool servers a cleaner way to participate in governed automation.
• Collaborative conversations add participants, mentions, and agent reactions so conversation threads can carry shared work rather than remain private transcripts.
• Document knowledge and inline citations make grounded answers easier to follow back to their sources, with better source labels, spreadsheet citations, index previews, and PDF handling.
• Live chat bridges and advanced handoffs make Gaia more practical in support and contact-center workflows where an automated agent, a human operator, and an external channel all need to stay in sync.

What 3.0 changes

The important shift in 3.0 is not a single surface. It is that the platform now carries more of the operating model around agentic work.

Teams can design projects with more help from Gaia, govern the work with clearer evidence and access boundaries, collaborate inside the conversations where decisions happen, connect agents to external tools and live channels, and inspect the documents and citations that shaped an answer.

Gaia 2.12 made governed automation operational. Gaia 3.0 makes that operating model broader, more collaborative, more grounded, and more connected to the systems where work already happens.