blog
rssROI takes, build-vs-buy framings, and honest reads on AI coding tooling. Written for founders and engineering leaders, not implementers.
More posts
- · build-vs-buycode-intelligenceai-spenddeveloper-velocity
Build vs. Buy Code Intelligence: The Real ROI
Building in-house code graphs costs $250k+ and 6 months. Adopting Coograph cuts AI spend 80% while freeing engineers to ship product.
- · ai-costscontext-windowcode-graphdeveloper-tools
You're Not Over Budget. You're Over Quota.
Claude Code's weekly cap and Copilot's new per-credit meter punish the same thing: agents that read 20 files when 4 would do. The fix isn't a bigger plan—it's a smaller context.
- · securitysupply-chainai-coding-agentsnpmconfig
Your AI Coding Agent's Config Is the New Attack Surface
In early June 2026, the Miasma worm stopped bothering with npm install. It started committing poisoned .claude/settings.json, .cursor, and .vscode files straight into GitHub repos — including 73 Microsoft repos. Open the repo in Claude Code or Cursor and the malware runs before you type anything. Here's why agent config is now code, and how to treat it that way.
- · mcp-serverai-codingbuild-vs-buyengineering-infrastructure
MCP Server: Scaling AI Coding Agents Without The Waste
An MCP server standardizes how AI agents read your codebase. On a representative task, graph-based context cut tokens ~80% and tool calls ~4x — here's why that matters and how to think about build vs. buy.
- · ai-coding-agentscli-tipsdeveloper-workflow
5 Claude Code Commands That Cut My Context-Switching in Half
The hidden Claude Code slash commands experienced terminal devs actually use daily — /statusline, !, @, /add-dir, /btw, /branch — what each saves, where /add-dir breaks at scale, and the Codex CLI gotcha that ruins muscle memory.
- · ai-costsgithub-copilotcontext-optimizationllm-efficiencypricing
Copilot Goes Pay-Per-Token on June 1. Your Context Bloat Is Now a Line Item.
GitHub Copilot switches every paid plan to usage-based AI Credits on 1 June 2026. Token waste that was hidden inside a flat $10/month bill now eats your credit balance in real time. Here's the math, and how a code-graph cuts it by ~80%.
- · coographnamingslash-commandsuxmigration
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.
- · securityaudit-logai-coding-agentsincident-responseobservability
Per-Session Audit Logs: Scoping the Blast Radius of an AI Coding Agent
A single rolling audit log of every shell command your AI coding agent ran is good. A per-session log is better. Here's why scope matters, what changed in Coograph this week, and how to roll the same pattern into your own setup.
- · securitysupply-chainai-coding-agentsnpmaudit-log
The TanStack npm Compromise: Why Every AI Coding Agent Needs an Audit Log
On 11 May 2026, 84 malicious versions of 42 @tanstack/* packages hit npm and started stealing AWS, GCP, Kubernetes, Vault, GitHub, and SSH credentials. If your AI coding agent ran npm install during that window, you may never know. Here's why agent command logging is now non-negotiable.
- · ai-costscontext-optimizationllm-efficiency
Context Bloat Is Draining Your AI Tool Budget
Most AI coding agents pull too much code into their context window, inflating token costs by 5x. Here's what that costs and how to fix it.
No posts match your search.