Issue Artifacts [Public Preview Feedback] #210917
Replies: 21 comments 18 replies
|
Thanks for introducing Issue Artifacts! I tried using Issue Artifacts to share an AI-generated swimlane diagram with my team to help them understand a complex workflow. However, the diagram was too wide to view comfortably because the artifact panel is limited to a maximum width of 768px. I experimented with overriding the panel's CSS variables in DevTools and found that:
Of course, part of the issue could be how the AI-generated HTML handles responsive layouts. Rather than simply increasing the fixed maximum width, it would be great if users could freely resize the panel, ideally up to around 80–100% of the viewport width, or switch to a full-screen view. This would make Issue Artifacts much more useful for sharing wide diagrams and other complex content with teams across different screen sizes. |
|
Seems like a super useful feature, but it seems like it isn't available to GitHub app tokens yet? |
|
Very useful feature. I suggest adding link previews and titles using |
|
Great! |
|
Thanks for this great feature! |
|
What are the storage constraints around these artifacts? |
|
Can we expect privacy controls for artifacts, like restricting access to organization members? |
|
I like this feature a lot! Thank you so much. I'm planing a new AI-based workflow where I'm trying to translate a bunch of |
|
Looks super promising for enhancing project tracking and planning using GitHub issues. |
|
Can we get artifacts on discussions too please? Some repos are starting to do the discussions = feature request, issues = bugs type flow. So an html mockup of a new feature request naturally fits as something I'd want in a discussion, not just an issue. Note: I've unsubscribed from this discussion as I only want replies to this comment, not the entire discussion and discussions don't support that yet. @ me in responses if you need more info. |
|
Love the HTML preview, thanks! Two requests:
|
|
Exploring the feature, and would love it if checkboxes were clickable in the artifacts like they are in issue bodies. I wanted to store a separate checklist as an artifact instead of polluting the GitHub Issue body, but I can’t interactively click on the checkbox in the artifact to select it/mark it as complete. Would enjoy that feature |
|
Great feature! Regarding the artifact view panel on a github issue page, the max width is quite narrow. Not great if the artifact is a bit long (which is likely the intent). Particularly acute on half screen windows.
|
|
The "Add artifact" button is displayed in arbitrary issues in public repositories in EMUs, who should not be able to create replies on or edit public issues. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
TitleIssue artifact (embedded_html) can no longer be opened after ~34 updates: viewer request returns 503/504 BodySummaryAn issue artifact of type What I observed
Steps to reproduce (not yet verified on a clean repository)
ExpectedThe latest version of the artifact renders, regardless of how many versions exist. ActualThe artifact panel does not render. The viewer request returns 503/504. My guess (not confirmed)The web endpoint seems to load the full Questions
Environment
|
|
Issue artifacts are a great fit for a plan → human review → implementation workflow, but I’m encountering a gap in the handoff to Copilot. I have an agentic workflow that generates an implementation plan and attaches it to the issue as a native Plan artifact. After reviewing it, I assign the issue to Copilot for implementation. However, that session cannot read the artifact. Copilot confirmed:
I can retrieve the artifact through the REST API using my own authenticated GitHub CLI. The assigned Copilot session’s attempt via My workaround is to paste the plan into the implementation PR’s comments, which duplicates the artifact and undermines having one authoritative plan. Could issue artifacts be made available as context when an issue is assigned to Copilot—or could the built-in GitHub MCP server expose artifact-reading tools in those sessions? If there’s an existing supported configuration for this, I’d appreciate guidance. |





Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Leave your feedback below on issue artifacts!
https://github.blog/changelog/2026-10-28-issue-artifacts-are-now-in-public-preview/
All reactions