Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.309 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

Unattended routines refuse artifact writes from linked or unusual files

Scheduled runs with nobody present now refuse artifact writes and uploads from linked, oddly named or uploads-folder files instead of asking

You'll notice Improvements
JSON All of v2.1.310
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release

Unclear One further check runs before the refusal, and it is not clear whether it is a feature switch that could be off for some accounts.

What

A routine is a scheduled run of Claude Code with no person watching. When a routine tries to write data into an artifact's database, or upload a file to an artifact, from one of these kinds of file, Claude Code now refuses outright:

  • A file reached through a link (a shortcut that points at another file)
  • A hard-linked file (one file stored under more than one name)
  • A file whose name is spelled in an unusual way
  • A file in the uploads folder

Before, these cases raised a permission prompt asking for approval. This happens when no hook (a script you set up to run automatically) or permission rule settles the question first. The refusal explains that only a person can approve this and nobody is present in the run. It tells Claude not to retry with that file. Claude should either send the documents inline in the data or say in its report what was not written or uploaded.

Why

An unattended run no longer gets stuck on a permission prompt that nobody can answer. It fails safely with a clear refusal, so check routine reports for anything listed as not written or not uploaded.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtOne further check runs before the refusal, and it is not clear whether it is a feature switch that could be off for some accounts.

See this entry in the whole of v2.1.310 →

Feedback