Tagged #claude-code
5 {count, plural, one {post} other {posts}}.
-
· Paul Lukic
The Warning Your Agent Never Saw: Instruction Budgets, Invisible Hooks, and a Sync That Ate Its Own Output
One day of running Coograph on real projects: 120,000 tokens of instructions before a single line of code, guardrail warnings the model was never shown, and a sync that overwrote the fixes its own retro had proposed. What we found, how we proved it, and what ships in 1.8.5.
-
· Paul Lukic
The Review That Found What Review Missed: An Optional Deep Review for Big Changes
One reviewer over a diff approves things that several hostile reviewers with refuters do not. Here is what a multi-agent review found on a 176-commit stack after ordinary reviews had passed it, what it costs, why it is optional, and the loop shape that keeps it from eating your budget.
-
· Paul Lukic
One Model for Six Jobs: Why We Made Per-Task Model Selection Opt-In
Coding agents delegate to sub-agents with wildly different demands, and almost everyone runs all of them on one model. Here is the cost of that, why a shipped default would be worse, and how we built model selection that asks once and always reports what it did.
-
· Paul Lukic
Recursive Self-Improvement for Artificial Intelligence Coding Agents: What Is Real, What Is Theory, and What We Shipped
Recursive self-improvement is the idea that an artificial intelligence system improves its own ability to improve. Here is what the theory actually says, why the model-level loop is still theory, and how we built the instruction-level version for coding agents with a human at the gate.
-
· Paul Lukic
Your Claude Code Week Is About to Get a Third Shorter
The +50% weekly limit boost is scheduled to lapse August 19. Limits are weather—capacity-driven, changed five times in a year. Tokens-per-task is the only forecast you control.