Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt

Use this file to discover all available pages before exploring further.

​
About artifacts

Cosmos saves the pull requests, branches, and Linear tickets a session creates so you can find them later, and lets you attach any external link as well. Cosmos stores each one alongside the session, surfaces them in the session details panel, and matches them in the Cmd+K command palette. Use artifacts to:
  • See the concrete outputs of a finished session.
  • Find the session that opened a specific pull request, branch, or Linear ticket.
  • Attach external context (a Linear ticket, a Notion doc, a dashboard URL) to a session so it stays discoverable.

​
Viewing artifacts in a session

Open any session and look for the Artifacts section in the session details panel. Each artifact shows its type, a label, and a link out to the underlying system. Empty sessions display a placeholder prompting you to attach a PR, Linear ticket, or custom link. Each artifact card has Edit and Delete controls. There is no toggle or enable/disable state — an artifact is either attached or removed.

​
Artifact types

There are four artifact types today. The headings below are the exact labels the UI uses.

​
Pull request

A GitHub pull request linked to the session. PR artifacts are auto-attached in two cases: when the Expert opens a PR through its GitHub tool, and when you send a chat message containing a GitHub PR URL. You can also add one manually from the Add-artifact dialog. The artifact stores the PR URL and renders as a link to GitHub.

​
Git branch

A branch associated with the session. Branch artifacts are recorded automatically from the running VM’s git context — there is no manual option for Git branch in the Add-artifact dialog.

​
Linear issue

A Linear ticket linked to the session. Linear artifacts are auto-attached when you send a chat message containing a Linear URL, and you can add one manually by pasting a Linear URL or a bare issue identifier (for example, AUG-12110).
The Linear artifact type is gated by the poseidon_linear_integration_enabled feature flag. When the flag is off for a tenant, Linear does not appear in the Add-artifact category dropdown and Linear URLs are not auto-attached.
A custom external URL — for example, a Notion page, a runbook, or a dashboard. Use this type for anything that doesn’t fit the categories above. The UI labels custom artifacts as “Link”; the storage-layer name is CUSTOM.

​
Searching sessions by artifact

The Cmd+K command palette matches artifact content alongside session names. Search by:
  • PR number or URL — e.g. 4821 or a full github.com/... URL.
  • Branch name — e.g. fix/auth-token-refresh.
  • Linear identifier or URL — e.g. AUG-12110.
  • Custom link label or URL — whatever you typed when attaching the link.
Results show every session whose artifacts contain the query, scoped to your tenant.

​
Adding artifacts manually

The session details panel has an Add button above the Artifacts list. Use it to attach an artifact that wasn’t auto-detected, or to record an external reference (Linear ticket, Notion doc, etc.) against a session.
1

Open the Add-artifact dialog

In the session details panel, click Add above the Artifacts list.
2

Pick a type

Choose Pull request, Linear issue, or Link. The Linear option is hidden when the Linear integration flag is off. Git branch is not a manual option — branch artifacts are recorded automatically from the VM’s git context.
3

Enter the URL or identifier

Paste a URL for pull-request and link artifacts, or a URL or bare identifier (e.g. AUG-12110) for Linear. URLs must use http:// or https://; Linear URLs must use https://.
4

Edit or remove later

Each artifact card in the list has Edit and Delete controls. Editing lets you change the label or URL; deleting removes the artifact from the session.
Artifacts are per session — each session manages its own list.