Gaia 2.11 — Artifacts, Document Folders, and Working Outputs

Conversations are useful only up to the point where teams need durable outputs. After that, the real question is whether the system can produce working artifacts instead of just text.

With Gaia 2.11, Gaia moved much closer to that goal.

The Problem: Too Much Work Escaped the Conversation

Teams often needed to take useful AI output and move it elsewhere before it became operational.

That showed up as:

• manual copying into docs or spreadsheets,
• disconnected file collections,
• and weak continuity between source material and generated output.

Gaia 2.11 improved that chain directly.

Artifacts Became a Real Output Layer

What shipped

Gaia 2.11 introduced end-to-end artifacts, expanded canvas support, enabled conversation storage attachments, and added PDF attachments with extracted text for previews and follow-on work.

Why this matters

Teams can keep more of the working loop inside Gaia. That reduces friction between generation, inspection, and reuse.

Document Folders Added Shared Project Context

What shipped

Gaia 2.11 added document folders with uploads, OneDrive import, search across indexed contents, sharing with users or agents, and conversations scoped to a folder.

Why this matters

Context is more useful when it is organized. Document folders give teams a clearer unit for managing source material and grounding agent work.

Spreadsheet Artifacts Made Structured Outputs Practical

What shipped

Gaia 2.11 added spreadsheet creation, CSV/XLSX import, interactive editing, formula support, and CSV/XLSX export directly inside conversation artifacts.

Why this matters

Many operational outputs are tabular. Spreadsheet artifacts let teams stay inside Gaia longer before they need an external office workflow.

Seen from 2.12

That next step is now visible in Gaia 2.12.

Artifacts and document folders are no longer only better places to hold working material. They can now sit inside more explicit, graph-based, policy-aware processes where outputs, source context, approvals, and auditability stay connected.

Gaia 2.11 made AI outputs more workable. Gaia 2.12 makes them part of governed automation.