Issue Artifacts [Private preview feedback]

Issue artifacts give you and your agents a dedicated place to attach durable work products directly to an issue. Instead of leaving important output buried in comments or scattered across external tools, artifacts keep it visible alongside the issue where the work is planned and discussed.

An artifact can capture context that should remain easy to find and revisit, such as:

• an implementation plan
• research notes or an investigation summary
• a design proposal
• a root cause analysis or postmortem
• a link to a related resource

Three artifact types are available:

Type	Use it for	Body
generic	Research, root cause analyses, summaries, notes, and other Markdown documents	Markdown
plan	Implementation plans and task breakdowns	Markdown
link	References to GitHub resources, documentation, dashboards, or other web pages	A full http:// or https:// URL

How to try

GitHub.com

Open an issue and click Add artifact to get started.

GitHub Copilot App

The GitHub Copilot App has built-in Issue Artifacts support and does not require a local skill:

1. Update to the latest version of the app.
2. Open Quick Open, search for Unlock private preview, and select it.
3. Enter the preview code: issue-artifacts-preview.
4. The app opens Experimental Settings. Confirm that Issue Artifacts is enabled.

Once enabled, open an issue in an enrolled repository and start a Copilot session from the issue. Ask Copilot to create a plan, research note, or other artifact, or type /create-issue-artifact in the prompt box and select the command.

Local agents

The API is not yet exposed as a first-class GitHub MCP or gh issue command (coming soon!). GitHub Copilot CLI, GitHub Copilot in VS Code, Claude Code, and Codex can use the API through GitHub CLI by installing the skill below.

Create an issue-artifacts directory in the location supported by your agent:

Agent	Repository skill path	Personal skill path
GitHub Copilot CLI	.github/skills/issue-artifacts/	~/.copilot/skills/issue-artifacts/
GitHub Copilot in VS Code	.github/skills/issue-artifacts/	~/.copilot/skills/issue-artifacts/
Claude Code	.claude/skills/issue-artifacts/	~/.claude/skills/issue-artifacts/
Codex	.agents/skills/issue-artifacts/	~/.agents/skills/issue-artifacts/

Repository skills can be committed and shared with the team. Personal skills are available across your local projects.

Create SKILL.md in the directory for your agent:

---
name: issue-artifacts
description: Read, create, and update durable artifacts attached to GitHub issues. Use when a user asks to save or retrieve plans, research, root cause analyses, summaries, links, or other agent context on an issue.
---

# Issue Artifacts

Use `gh api` to work with artifacts at:

`repos/{owner}/{repo}/issues/{issue_number}/artifacts`

## Prerequisites

- Run `gh auth status` before the first API request.
- Confirm the target repository, issue number, and requested operation.
- Never print or request the user's GitHub token.

As you work with an issue, try creating or attaching an artifact for a meaningful output that you would otherwise put in a long comment, save in another tool, or lose in a chat transcript. Then return to the issue later and see whether the artifact makes it easier to understand the work and continue from where you left off.

Suggested prompts

• Save this implementation plan as a new artifact named "Implementation plan" on OWNER/REPO#123.
• Attach https://example.com/runbook as a link artifact named "Service runbook" on OWNER/REPO#123.
• Update artifact 2 with the findings in research.md. Preserve any existing details that are still accurate.
• Compare the plan artifact with the current implementation and tell me what remains.

We'd love your feedback!

Please respond in this discussion with any feedback or bug reports. Some questions that might help:

• Are there any other issue artifacts types you'd want to store?
• What did you expect to be able to do with the artifact that you couldn't?

Thank you for helping us shape issue artifacts! Your feedback will directly inform what we improve before a broader release.

[rwoll]

I'm excited to give this a spin as I had previously been dumping these kinds of Artifacts in temp branches or <details> sections. Glad to see it have a more formal place to live! Feature request: a lot of my work involves data analysis. Could Markdown support on GH[.]com expand to support Microsoft's OSS Flint Charts: https://microsoft.github.io/flint-chart/#/.

I'd expect it to work similarly to the GH Mermaid Integration where user can do:

```mermaid
…
```

```flint
…
```

Cheers! ❤️

[evi-liu]

Excited for you to try out issue artifacts! We're looking for any and all feedback :)

Could Markdown support on GH[.]com expand to support Microsoft's OSS Flint Charts

We have a team working on a new and improved Markdown experience for GitHub, so I'll definitely pass along this feedback to them!

[beingminimal]

Hi @evi-liu

Could you please enable/allow Private Preview access for the new Issue Artifacts feature across our GitHub organizations?

Target Organizations:

• https://github.com/Aakaar-ai
• https://github.com/CodecycleLLP
• https://github.com/MahakaalGH
• https://github.com/open-doc-spec
• https://github.com/oss-forks-staytuned
• https://github.com/StaytunedFoundation
• https://github.com/StaytunedLAB
• https://github.com/StaytunedLLP
• https://github.com/Z1-Test
• https://github.com/Z2-Test

Thanks!

[evi-liu]

@beingminimal All of those organization are now flagged into issue artifacts! Let us know if you have any feedback.

[beingminimal]

@evi-liu as we have access now so we will be able to use api through gh cli way for issue artifacts or not?

[gillesdemey]

Love this feature! Is this also coming to Pull Requests? We'd love to attach agent plans to those so too in case we don't have an issue to link it back to.

[evi-liu]

Yes, we do intend to bring artifacts to PRs as well :)