Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

Skills sync telemetry gains a suspended outcome and unified payload builder

Skills-sync telemetry gains a 'suspended' outcome for rounds delayed by the process being asleep

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaSkillswhat it touches
KindInternal Changesin v2.1.269,
Under the hood

Skills-sync telemetry gains a 'suspended' outcome for rounds delayed by the process being asleep

What

The skills-sync process, which keeps the list of available skills up to date, now builds its telemetry through a single shared function that always includes account_opt_in, trigger, and duration_ms, plus two new fields: suspended_ms (time the process spent suspended or asleep during the round) and tick_late_ms when applicable.

  • If a skills-list fetch fails with a timeout, network, or HTTP error, and suspended_ms exceeds 45 seconds, the round now reports its outcome as suspended instead of list_failed.
Why

This distinguishes sync failures caused by the process being suspended, for example a laptop going to sleep, from genuine network or server failures, giving clearer telemetry about why a sync round didn't complete.

See this entry in the whole of v2.1.269 →