Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

Background artifact threads are told not to pick up main-session work

When an artifact thread is handled in the background, the model is now told to leave pending tasks, agents and next steps to the main session

Under the hood Internal Changes
JSON All of v2.1.287
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.287,
Internal ChangesSection of the release
What

Claude Code can handle an artifact thread in the background, as a separate piece of work alongside your main conversation. The instructions given to the model for that background work now include an extra rule. Anything that belongs to the main session stays with the main session, and the background thread must not resume, relaunch or check on it. That covers:

  • Pending tasks
  • Background agents (helper instances of Claude working on their own)
  • Monitors
  • Next steps listed in a summary

The background thread is told that the thread itself is its whole job.

Why

This keeps the background thread focused on its own task, so it does not drift into work that your main session is already handling.

See this entry in the whole of v2.1.287 →

Feedback