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

Ouverte
#39,041 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
TypeScript
Étoiles
24.8k
Forks
6.4k
Merge moyen
4 h 29 min
PR mergées (30 j)
488

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de pingdotgg/t3code

Toutes les issues de pingdotgg/t3code

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.