[Bug]: Artifact watches are refused in every Claude thread: "Watch <url>" is treated as a print session

未关闭
  • 哪里不对？
#35,127 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
64/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
backend-api-design

调研方向

Start in the apps/server area, then trace how Claude session entrypoints are identified and how ArtifactComments decides whether a session can hold an artifact watch. Compare the current "t3-code" entrypoint with the reported working "sdk-ts" behavior and inspect the change from commit ddfc4a92ed. Done when a T3 Code Claude thread can arm the watch and comments sent to Claude reach that thread.

由索引模型根据 Issue 内容生成。

描述

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, and "env": {"CLAUDE_CODE_ARTIFACT": "1"} in Claude's settings.json so the Artifact tools load.

  1. In a T3 Code Claude thread, send: Use your Artifact tool to publish a private page titled "Sample page" with the two lines "Sample page" and "Line two."
  2. In the same thread, send Watch <the link of that artifact>.
  3. Read the result of the ArtifactComments call (expand the tool row), or ask Claude whether comments sent to it on that page will reach the thread.
Expected behavior

The watch connects, as in a terminal claude session. In T3 Code builds from before the entrypoint identifier changed, Claude Code accepts the watch. One such build that also marks composer messages as typed by a person (commit 6a275fb45a) gives, with the same Claude Code version:

Watching <artifact-url> — the watch is armed (`status` shows whether it has connected yet); this session keeps track of new versions published elsewhere; a new version starts no turn and sends no notification

followed by "A comment on it sent to Claude reaches this session (its status row says auto-replies armed)". A comment with "Send to Claude" on that page then wakes the thread, and Claude handles and resolves it.

Actual behavior

On current main the watch is refused. The ArtifactComments result is:

Not watching <artifact-url> — only a main-loop session (interactive, SDK, or background) holds the watch, not a subagent, teammate, or print session.

The publish result in step 1 already says:

Live subscription: none — this is a print (-p), cloud, subagent, or teammate session, which does not keep track of new versions of this artifact published elsewhere (only the main conversation of a local interactive, background, or TypeScript/Python Agent SDK session does). Expected; not an error.

So no artifact watch can connect in any T3 Code Claude thread, and "Send to Claude" on a comment never reaches the thread. Claude Code's session transcript records the thread's prompts with "entrypoint": "t3-code". The build from before the change records "entrypoint": "sdk-ts" for the same steps.

This started when the entrypoint identifier changed (commit ddfc4a92ed, 2026-11-01).

Impact

Major degradation or frequent failure

Version or commit

main b68aedfdb7 (2026-11-12); the build where the watch arms is 6a275fb45a. Claude Code 2.1.322.

Environment

Linux (Ubuntu 26.04), T3 Code desktop app and web client built from source, Claude Code 2.1.322 signed in with a claude.ai subscription, Claude Haiku 5.5.

Logs or stack traces
main b68aedfdb7:   entrypoint "t3-code"  ->  ArtifactComments watch: "Not watching <artifact-url> — only a main-loop session (interactive, SDK, or background) holds the watch, not a subagent, teammate, or print session."
6a275fb45a:        entrypoint "sdk-ts"   ->  ArtifactComments watch: "Watching <artifact-url> — the watch is armed ..."
Workaround

None found. Watching the artifact from a terminal claude session works.

主要语言
TypeScript
星标
24.8k
派生
6.4k
平均合并
4 小时 16 分钟
30 天内合并 PR
352

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。