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

Aperta
#39,041 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

[!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.

Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
4h 29m
PR unite (30g)
488

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pingdotgg/t3code

Tutte le issue di pingdotgg/t3code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.