{"version":"2.1.293","anchor":"skills-sync-resync-gains-an-idle-interval-mode-with-activity","canonical_anchor":"skills-sync-resync-gains-an-idle-interval-mode-with-activity","heading":"Skills sync checks less often while you are idle","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/skills-sync-resync-gains-an-idle-interval-mode-with-activity","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Skills sync checks less often while you are idle\n\nThe claude.ai skills sync now waits longer between checks when you are idle, and wakes up again when you return\n\n**What**\n\nClaude Code regularly checks claude.ai for changes to your skills and copies them down. A skill is a packaged set of instructions Claude can use. This repeated check now has an idle mode.\n\n- While the client is idle, the time between checks is multiplied. The multiplier comes from remote configuration and has a maximum.\n\n- Claude Code listens for user activity and schedules the next check sooner once you are active again.\n\n- A check counts as idle when it is a routine recheck, nothing woke it, and no recent check failed, among other conditions. Idle checks may do less work.\n\n- Check reports now include `idle` and `woken`, downloads note a skill's state on disk before and after, and the completion stats gain `mount_wait_ms`.\n\nThe gate `tengu_claudeai_skills_sync_idle_intervals` has not been read, so its state is unknown.\n\n**Why**\n\nAn idle Claude Code does less background syncing. A skill changed on claude.ai while you were away may take a little longer to show up until you become active again.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}