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

Abierto
#39,041 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
4 h 29 min
PR fusionados (30 d)
488

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.