Non-project chats: when I open an artifact or any file I should be able to render it, especially HTML
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- desktop
调研方向
The issue does not name files, tests, or implementation entry points. Start by locating how non-project chat artifacts are displayed and compare their available actions with the project chat Files pop out shown in the issue. Done means artifacts can be rendered when supported and opened in the system file explorer, with the path action giving users a usable location.
由索引模型根据 Issue 内容生成。
描述
Feature summary
Open and render files easier especially for artifacts in chats that dont belong to projects.
What problem are you trying to solve?
The agent created an html document and stored it as an artifact.
I can see the raw html.... but there is not option to actually render it.
when I have a repo I can do this by right clicking the file >"Open in browser"
Proposed solution
When I have an artifact especially an html or markdown file I should be able to easily render those. I should also be able to quickly open the file in the system file explorer so if it is a different a file type I can open it. The "copy path" option in artifacts doesnt really do anything it just copies the filename.
These artifacts are not stored in an easy well known spot so it isnt easy to find.
The non-project chats have a pretty terrible artifact experience. It should
Workflow impact
see my chat dialog to see how bewildered I was about this experience.
Installation context
v1.1.29 github copilot desktop app.
Additional context
This is a bad experience that shows artifacts in a non-project chat.
This is a screenshot from a project chat and the Files pop out.
These are the same options I want to see when I open an artifact in a non-project chat
- 主要语言
- 没有语言数据
- 星标
- 2.2k
- 派生
- 183
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/app 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
-
triage
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 70/100
相似的 Issue
-
needs-triage
难度 1/5 1 小时以内 新手友好度 88/100
junruxiong/IncarnaMind#1405 ·
-
area:holodeck review-finding
难度 2/5 1-3 小时 新手友好度 72/100
hyperdrive-technology/holodeck#201 ·
维护者通常 1 天内回复
-
Desktop App QA
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
bug priority: high
难度 2/5 1-3 小时 新手友好度 78/100
cofade/open-garden-planner#542 ·
维护者通常 1 天内回复
-
area:io needs-info needs-triage
难度 2/5 1-3 小时 新手友好度 63/100
bherbruck/solvecraft#3216 · 1 条评论 ·