General Discussions

Category: Assistant / Agents · Type: Feature Request

When users build agents that generate reports or documents, the agent can't hand the user an actual downloadable file. Today it falls back to pasting the content inline as a code block and telling the user to copy/paste it and save it themselves ("I can't create the downloadable .txt file directly here…"). That defeats the purpose of a report-generating agent and reads as a broken experience.

This is happening because downloadable output goes through the Artifacts system, which is gated off for the agent surfaces:

- Agent Builder / live preview — artifacts are disabled (co.aac.enable_artifacts defaults false; the AGENT_LIVE_PREVIEW surface is excluded), so authors can't even test

- Deployed agents — governed by co.aao.* (SearchConfig) plus per-agent/type allow-lists, so it isn't available by default and there's no clear admin/author-facing way to turn it on.

A user built an inbox-triage agent that produces an HTML report. When testing it in the Agent Builder, the agent couldn't generate a downloadable file and instead pasted raw HTML for the user to save manually. Filed as EN-1961706. Artifacts are otherwise fully enabled for their workspace — the gap is specifically agent output.

1. Agents can emit downloadable file artifacts (at minimum HTML, PDF, CSV/spreadsheet, TXT) as first-class outputs to end users when run.

2. Authors can test/preview that file output while building the agent (Agent Builder), not just after deploy.

3. A clear, admin- or author-facing control to enable/scope file output per agent — not a hidden SearchConfig param that requires an internal ticket.

4. Works consistently across surfaces where agents run (web today; desktop app should advertise the capability too).

- Report/document generation is one of the most common and highest-value agent use cases (triage summaries, exports, formatted deliverables). Inline code blocks make these agents feel unfinished.

- Customers perceive it as a bug ("Glean can't create a file"), generating thumbs-downs and support tickets.

- The capability largely exists (Artifacts works in regular chat) — this is about extending/exposing it to the agent path, not building from scratch.

Feature Request -  Allow agents to produce downloadable file outputs (HTML / PDF / CSV / TXT) for end users

Home

Forum

Events

Content

Courses

Collections

People

Contributors

Albums

Groups

Chat

Channels

Tools

Help

Welcome to the Gleaniverse. Empowering work with AI. Connected by knowledge. Growing together. Search Where would you like to start? Join the discussions.

Glean Community

Gleaniverse Community

Copyright

Terms of Service

Privacy Policy

Code of Conduct

Your Privacy Choices

It looks like there is no account associated with the email you provided. The event is for members only. Please complete the application to join our community first.

Thank you for your interest in joining us

Thanks for your interest in joining the event. However, your account is still pending. Once it's approved, you'll be able to register for the event. Please contact us via community@glean.com if you need support.

Pending Approval

Login to the Glean Community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community and get the best experience, complete your profile.

Hey, complete your profile

It looks like there is no account associated with the email you provided. Please complete the application to join our community.

Thank you for your interest in joining Glean Community.

Thanks for your interest in joining Glean Community. We will review your request shortly and email you once it's approved. Meanwhile, please feel free to contact us via community@glean.com for any questions.