[Bug]: Artifact watches are refused in every Claude thread: "Watch <url>" is treated as a print session
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend-api-design
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- 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." - In the same thread, send
Watch <the link of that artifact>. - Read the result of the
ArtifactCommentscall (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.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 4h 16m
- Merged PRs (30d)
- 352
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Autocomplete still accepts an option after becoming disabledPossibly taken @Xapollon430 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
reduxjs/react-redux#2416 · 1 comment ·