{"version":"2.1.248","anchor":"scheduled-tasks-and-other-runtime-files-no-longer-clutter-gi","canonical_anchor":"scheduled-tasks-and-other-runtime-files-no-longer-clutter-gi","heading":"Scheduled tasks and other runtime files no longer clutter git status","tier":"notice","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/scheduled-tasks-and-other-runtime-files-no-longer-clutter-gi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Scheduled tasks and other runtime files no longer clutter git status\n\nClaude Code's runtime files stop showing up as untracked in git status.\n\n**What**\n\nClaude Code writes its own runtime paths into the repository's local git exclude list, so scheduled tasks, routines state, worktrees, checkpoints, mailbox and the agent registry stop appearing as untracked files. Scheduled tasks also take a lock file at `.claude\/scheduled_tasks.lock` so two runs cannot process the same schedule at once.\n\n**Details**\n\n- The lock records the session id, process id, process start time and acquisition time, so a stale lock from a dead process can be told apart from a live one.\n- Writing the exclude entries is wrapped in error handling and only logged on failure, so a read-only or unusual repo does not break startup.\n\n**Evidence**\n\n`**\/.claude\/scheduled_tasks.lock`\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}