Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Upload announcement recovers after a create conflict

An upload announcement that hits a create conflict now checks its own journal and continues if it wrote it

Under the hood Bug Fixes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Directory SyncArea: what it touches
Bug FixesKind: in v2.1.281,
Bug FixesSection of the release
What

Before uploading, the client announces the upload. That announcement can clash with a record that already exists, because the step is only allowed to create a new record and never to overwrite one. When this clash happens, the client now reads its own journal (readOwnJournal). If that journal was written using the same announcement token, the client takes the journal's etag and carries on. An etag is a label that identifies one version of a stored file. Before this change, the client gave up.

Why

An upload whose earlier attempt already got through no longer fails just because that first attempt's record is still there.

See this entry in the whole of v2.1.281 →

Feedback