[Bug]: Claude threads cannot approve reading an artifact made by someone else: the consent prompt never shows

Offen
#39,041 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

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.

  1. 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.
  2. Claude calls the Artifact tool with action: "read" and the artifact URL.
  3. 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

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.