[Bug]: Claude threads cannot approve reading an artifact made by someone else: the consent prompt never shows
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- backend
调研方向
Start in the apps/server area named in the issue and compare how T3 Code handles Claude Artifact tool read consent with the Claude Code CLI behavior described here. The report suspects prompt handling for sessions marked with the t3-code entrypoint and points to issue #35127 as related. Done means the consent prompt can be answered in a T3 Code thread and an approved read succeeds.
由索引模型根据 Issue 内容生成。
描述
[!NOTE]
🤖 Claude Opus 5.5 responding on behalf of mjacquin
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
Prerequisites: Claude Code signed in with a claude.ai account, with the Artifact tools loaded.
- In a T3 Code Claude thread, ask Claude to read a claude.ai artifact made by someone else. One shared with "anyone with the link" is enough.
- Claude calls the Artifact tool with
action: "read"and the artifact URL. - Tell Claude "yes, read it" in chat, and let it retry.
Expected behavior
T3 Code shows the consent prompt, as the Claude Code CLI does:
"<artifact title>" was made by someone else. Let Claude read it for the rest of this conversation?
This artifact was created outside your organization.
<artifact url>
(shared with anyone with the link)
❯ 1. Yes
2. No
Answering Yes lets the read go through.
Actual behavior
No prompt appears. Each call fails at once with:
Nothing was done. This needs a yes to: "<artifact title>" was made by someone else. Let Claude read it? No one can answer in this session.
A yes in chat doesn't help: the tool takes the answer only from its own prompt. Bypass-permissions mode doesn't help either. The artifact can't be read from T3 Code at all.
This may share its cause with #35127. That session's transcript records its prompts with "entrypoint": "t3-code", and Claude Code may treat such a session as one where no one can answer a prompt. This is a guess from the error text: I haven't checked it in the code.
Impact
Major degradation or frequent failure
Version or commit
T3 Code (Nightly) 0.1.11-nightly.20261119.4918
Environment
macOS, Claude Code 2.1.328 (Claude provider), permission mode: bypass permissions
Screenshots, recordings, or supporting files
The prompt as the Claude Code CLI shows it (URL redacted) follows in a comment.
Workaround
Read the artifact from a terminal claude session, or paste its text into the T3 Code thread.
- 主要语言
- TypeScript
- 星标
- 24.8k
- 派生
- 6.4k
- 平均合并
- 4 小时 29 分钟
- 30 天内合并 PR
- 488
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
pingdotgg/t3code 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
needs more info
难度 2/5 1-3 小时 新手友好度 72/100
pingdotgg/t3code#39400 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panel可能已有人在做 @iamdatvt94 于 1 天前认领。 未关闭bug needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
相似的 Issue
-
area:plugins kind:bug priority:p2 ready
难度 2/5 1-3 小时 新手友好度 90/100
维护者通常 1 天内回复
-
Escaped `*` followed by `*` (`\**`) never matches可能已有人在做 @bardrop 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 71/100
editorconfig/editorconfig-core-js#172 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
vega/vega-webgpu#40 ·
-
type: bug 🐛
难度 2/5 1-3 小时 新手友好度 63/100
puckeditor/puck#1929 ·
维护者通常 1 天内回复
-
compression() compresses every response at Brotli quality 11可能已有人在做 @staylor 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复