Tagged #coograph
4 {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
Eleven Names, One Namespace: Unifying Coograph Under /coograph-*
Coograph's skills and slash commands used to live under three different prefixes. As of today, every shipped command starts with /coograph-. Here's why, what changed, and how existing projects pick it up automatically.