Save outputs to the Library

An output is a deliverable a run produced, such as a document, a page, or a file, recorded with the agent and session that made it. Save outputs so your team can find every result in one place and trace each one back to the run behind it.

What an output holds

Part	Meaning
Name and description	The output’s title and what it is.
Content	Either a file uploaded to Atlan (`upload` mode) or a link to something hosted elsewhere (`link` mode). Exactly one per version.
Agent	The agent or coding harness that produced it, when recorded.
Session	The recorded session it came from, when recorded.
Workspace	Where it lives. It follows that workspace’s access.
Versions	Every version stays readable. An uploaded file is pinned to the exact file version it was published with.

Before you begin

You can write to the workspace where the output should live.
For a local file, your agent can reach Atlan through the Atlan MCP endpoint or the Atlan API.
For a link, the URL is an absolute http or https address with no user name, password, or credential in it. A presigned URL is refused; upload the file instead.

Record the output

From a coding agent
With the API

Ask your agent to run the /atlan-record-output command with the file path or URL and a name. In Claude Code, with the Atlan MCP server named atlan:

/mcp__atlan__atlan-record-output ./reports/q3-churn.md q3-churn-report

For a local file, the command uploads it first, then creates the output pinned to that upload. For a URL, it creates a link output. It also attributes the output to the agent and session when it knows them. See Atlan commands and skills for coding agents.

Call POST /agent/v1/outputs. For a link output:

curl -sS --fail-with-body \
  -X POST "${ATLAN_GATEWAY_URL}/agent/v1/outputs" \
  -H "Authorization: Bearer ${ATLAN_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "q3-churn-report",
    "description": "Churn drivers for Q3, by segment.",
    "workspace_id": "workspace_01example",
    "mode": "link",
    "external_url": "https://docs.example.com/q3-churn",
    "subject_kind": "agent",
    "subject_id": "agent_01example",
    "session_id": "session_01example"
  }'

For an uploaded file, upload it as a file record first, then send "mode": "upload" with file_artifact_id and file_version_ordinal instead of external_url. Set subject_kind and subject_id together, or leave both out. The 201 response returns the output with its output_… handle.

Publish a new version when the content changes

An output’s content doesn’t change in place. To publish new content, call POST /agent/v1/outputs/{output_id}/versions with the same fields as a create, without the name, description, or workspace. Each version is complete: agent and session fields you leave out are empty on that version, not copied from the last one. A version can switch between upload and link.To change only the description, use PATCH /agent/v1/outputs/{output_id}.

Verify

Open the Library

Select Library in the left rail. The page reads Library, “Everything your agents have made, in one place.”

Find the output

Use Search the Library, or narrow with All agents, All workspaces, and All types. Switch between List view and Gallery view. Each row shows the output’s type, the agent that made it, its workspace, and when it was made.

Open it and check its versions

Select the output to open it. When it has more than one version, a Versions rail lists them as V1, V2, and so on; select one to view it. The row’s menu can also offer Open the session, Copy link, and Download.

To see one agent’s outputs, open the agent’s profile and select Library. An agent with none shows No outputs yet.

If the output is refused

Message	Fix
`An upload output requires file_artifact_id and file_version_ordinal.`	Upload the file first and send both fields.
`An upload output cannot also carry external_url.` or `A link output cannot also pin a file.`	Send either the file fields or `external_url`, not both.
`A link output requires external_url.`	Add the URL, or switch to `upload`.
`subject_kind and subject_id must be set together.`	Send both or neither.
`external_url must not carry a credential in its query or fragment.`	Upload the file instead of linking to a presigned URL.

Availability and limits

By default, an uploaded file can be up to 100 MiB.
A workspace admin can archive an output with POST /agent/v1/outputs/{output_id}/archive. Archiving leaves the pinned file in place, and there is no permanent delete.
Yours in the Library may be empty for now, because outputs aren’t yet linked to the person who asked for them. Use All.
The Library’s skill filter isn’t available yet.

Agent profile: The agent’s Library tab.
How agent sessions work: The sessions outputs link back to.
Public API: The agent.createOutput, agent.appendOutputVersion, and agent.listOutputs operations.

Skill management

Agent management

AI Gateway

Metrics Studio

Ontology

What an output holds

Before you begin

Verify

If the output is refused

Availability and limits

​What an output holds

​Before you begin

​Verify

​If the output is refused

​Availability and limits

​Related

What an output holds

Before you begin

Verify

If the output is refused

Availability and limits

Related