[Bug]: Claude threads cannot approve reading an artifact made by someone else: the consent prompt never shows
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 48/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- typescript
- Bereich
- backend
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
[!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.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 24.8k
- Forks
- 6.4k
- Ø Merge
- 4 Std. 29 Min.
- Gemergte PRs (30 T.)
- 488
Entwicklungsumgebung
Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus pingdotgg/t3code
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
needs more info
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
pingdotgg/t3code#39400 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelEvtl. vergeben @iamdatvt94 hat das vor 1 Tag übernommen. Offenbug needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in pingdotgg/t3code
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
twilio/twilio-node#1241 ·
Maintainer antworten meist innerhalb von 1 Tag
-
documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 85/100
hugomrdias/playwright-test#786 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:stdlib effort:S impact:med platform:linux type:bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
WenyuChiou/agent-board#1745 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 88/100
Maintainer antworten meist innerhalb von 1 Tag