◉CLAUDE LABJP
●VERSION — v2.1.227 landed on August 10 with no new features, just fixes around plan detection and CI behavior●AUTO — Two days remain until August 14, when auto mode becomes the default in Claude Code for Pro, Max, and Team●CI — Bash commands no longer fail across the board under claude-code-action with allowed_non_write_users on GitHub-hosted runners●BILLING — Sessions started with an expired token could misread your plan and nudge Max users toward usage credits; that is now fixed●SUNSET — The legacy Workbench and the experimental prompt tool APIs retire on August 17, five days out●PRICE — Sonnet 5 promo pricing at $2/$10 per Mtok runs through August 31, moving to $3/$15 on September 1●VERSION — v2.1.227 landed on August 10 with no new features, just fixes around plan detection and CI behavior●AUTO — Two days remain until August 14, when auto mode becomes the default in Claude Code for Pro, Max, and Team●CI — Bash commands no longer fail across the board under claude-code-action with allowed_non_write_users on GitHub-hosted runners●BILLING — Sessions started with an expired token could misread your plan and nudge Max users toward usage credits; that is now fixed●SUNSET — The legacy Workbench and the experimental prompt tool APIs retire on August 17, five days out●PRICE — Sonnet 5 promo pricing at $2/$10 per Mtok runs through August 31, moving to $3/$15 on September 1
TAG

Distributed locks

1 articles
← Back to all tags
Related:
Claude Agent SDK1Scheduled jobs1Production1Design1
⬡ API & SDK/2026-06-25Advanced

When the Previous Run Hasn't Finished and the Next One Starts: Leases and Fencing Tokens for Scheduled Agents

A scheduled agent that runs on a fixed clock can overtake itself and start twice. From the moment a naive lock breaks to leases, fencing tokens, and bounded catch-up — worked through with the implementation I actually run.