CLAUDE LABJP
SAFE — A broad stability and safety update landed in Claude Code: tighter permission checks, safer Bash and PowerShell handling, and better background session cleanupEND — The new EndConversation tool lets sessions end explicitly, and progress heartbeats now show that long-running tasks are still alivePERM — Fixed single-segment dir/** allow rules auto-approving writes to nested directories. If you rely on broad allow rules, it's worth re-reading your permission settingsLIMIT — The 50% higher weekly limits promotion for Pro, Max, and Team ended on July 19, so plan automated workloads around standard limits againFASTEND — Fast mode for Claude Opus 4.7 is removed on July 24 — four days left. speed: 'fast' will return an error, so migrate to fast mode on Opus 4.8PRICE — Claude Sonnet 5 launch pricing ($2 in / $10 out per million tokens) runs through August 31, then returns to $3 / $15SAFE — A broad stability and safety update landed in Claude Code: tighter permission checks, safer Bash and PowerShell handling, and better background session cleanupEND — The new EndConversation tool lets sessions end explicitly, and progress heartbeats now show that long-running tasks are still alivePERM — Fixed single-segment dir/** allow rules auto-approving writes to nested directories. If you rely on broad allow rules, it's worth re-reading your permission settingsLIMIT — The 50% higher weekly limits promotion for Pro, Max, and Team ended on July 19, so plan automated workloads around standard limits againFASTEND — Fast mode for Claude Opus 4.7 is removed on July 24 — four days left. speed: 'fast' will return an error, so migrate to fast mode on Opus 4.8PRICE — Claude Sonnet 5 launch pricing ($2 in / $10 out per million tokens) runs through August 31, then returns to $3 / $15
TAG

Claude Code

201 articles
Back to all tags
Related:
Automation28automation25MCP23iOS19CI/CD15troubleshooting14Indie Dev13GitHub Actions9workflow9Workflow8operations7headless7
Claude Code/2026-06-17Advanced

When an Announced Billing Change Gets Paused at the Last Minute: Designing Automation That Doesn't Rush the Cutover

A billing change that was supposed to take effect on June 15 was paused that same day. If your pipeline trusts the announced date, a retraction breaks it twice. Here is a design that decides the cutover from a runtime signal, with implementation code.

Claude Code/2026-06-17Advanced

When an Announced Billing Change Is Withdrawn at the Last Minute, Change No Code

A billing change that was supposed to take effect was withdrawn on the day. To survive announce, apply, and revert without touching code, I keep platform behavior behind a single flag and project the monthly delta from real logs.

Claude Code/2026-06-16Advanced

Keeping Large Claude Code Refactors Revertible One Commit at a Time — Field Notes on Checkpoints and Rollback Detection

Hand a big refactor to Claude Code and the speed hides a real cost: review-proof, oversized diffs. Here are the field notes I actually run — declaring checkpoints in a manifest, enforcing commit granularity with a pre-push hook, and tying rollback calls to observability.

Claude Code/2026-06-16Intermediate

Two Days Into the Billing Change: How Far My Headless Costs Drifted From the Estimate

On June 15 the billing change moved headless execution onto separate monthly credits. Two days in, I broke down cost per pipeline stage and found one stage running at roughly double my estimate. Here is how I measured it, and why I moved one stage back to my subscription.

Claude Code/2026-06-14Advanced

Before Per-PR CI Burns Through Your Monthly Credits: A Three-Layer Guard for Claude Code GitHub Actions

From June 15, Claude Code GitHub Actions bills against non-rolling monthly credits. Run a review on every PR and you can drain the month in the first week. Here is a three-layer guard — when to run, how heavy one run can get, and making spend visible — with working workflows.

Claude Code/2026-06-14Intermediate

Finding and Installing Claude Code Plugins from a Marketplace — Read What's Inside Before You Trust It

A practical walkthrough for discovering and installing Claude Code plugins from a marketplace. Beyond the /plugin commands, it covers how to read the bundled contents before you install, and how to choose between User and Project scope.

Claude Code/2026-06-14Advanced

A SubagentStop Hook That Grades Subagent Output and Sends It Back to Be Redone

When a Claude Code subagent occasionally returns rule-breaking work, a SubagentStop hook can grade it automatically and ask for a redo. Here is a working setup with code and field notes.

Claude Code/2026-06-14Advanced

Pacing Non-Rollover Monthly Credits: A Burn-Rate Scheduler That Avoids Both Early Exhaustion and Wasted Balance

Non-rollover monthly credits punish you for spending too fast and for spending too slow. Here is the design of a scheduler that derives a daily burn rate from remaining balance and days left, throttles headless runs automatically, and the real numbers from running it on a personal automation setup.

Claude Code/2026-06-14Intermediate

Measuring a Week of Headless Usage the Night Before the Billing Change

With headless Claude Code moving to monthly credits on June 15, I spent a week logging how many tokens my unattended runs actually consume, so I could pick a plan based on numbers instead of a guess.

Claude Code/2026-06-13Intermediate

What the June 15 Claude Code Billing Change Means for Headless Runs

From June 15, 2026, the Agent SDK, headless claude -p, GitHub Actions, and third-party agents move to monthly credits. Here's how a solo developer running automation decided what to keep and what to cut.

Claude Code/2026-06-13Advanced

Pin Your Execution Model with enforceAvailableModels — Don't Let Auto-Upgrades Burn Through Your Credits

From June 15, monthly credits become non-rolling. This is a setup-layer approach to keep subagents and fallbacks from silently upgrading to pricier models, using enforceAvailableModels to pin the model set from the managed-settings layer, with a verification step you can run in CI.

Claude Code/2026-06-13Advanced

Context Budgets for Nested Subagents: Designing Contracts So 5-Level Delegation Doesn't Lose Quality

Once subagents could nest, deeper delegation made summaries thinner and reruns more frequent. Here is how I rebuilt quality by adding four contracts between layers: token budgets, a handoff schema, failure isolation, and an independent grader.