Issue artifacts attach agent-generated outputs and other important context directly to an issue. By keeping plans, research, links, and visualizations alongside the work, they give coding agents richer context and teams a durable record as the work evolves.
With issue artifacts, you can attach:
- Markdown files for plans, research, root cause analyses, and other documents.
- Links to Slack or Microsoft Teams threads, prototypes, and other external resources.
- HTML files for interactive visualizations, flowcharts, and diagrams, with the ability to toggle between a rendered preview and the source.
Get started with the GitHub App #
When you use the GitHub App to work on an issue, artifacts created during the session are automatically attached to that issue. You can also prompt the session to create a specific artifact, such as an implementation plan, root cause analysis, or summary of historical context. Support for creating and viewing HTML artifacts in the GitHub App is coming soon.
Get started with gh issue artifact #
gh issue artifact
The new gh issue artifact command brings issue artifact support to GitHub CLI. You can use the create, edit, list, view, download, and delete commands to manage issue artifacts. Coding agents and developer tools that use gh can also invoke them as part of their workflows.
Artifacts can also be addressed by their GitHub URLs, and Markdown documents support image and video attachments with --attach. For usage details, see the gh issue artifact documentation.
Manage and view artifacts on github.com #
Create, edit, and delete artifacts directly from an issue on github.com. You can update an artifact as plans and decisions change while retaining its version history, giving teammates and agents a current source of truth without losing how it evolved.
Each artifact can be linked, making it easy to open, reference, and share.
Share your feedback #
Join the GitHub Community to tell us what you think and help shape the public preview.