https://gethydrate.dev/blog/ Writing from the Hydrate team on shared memory, multi-agent orchestration, and the economics of coding agents. en-GB https://gethydrate.dev/blog/slept-through-beta-launch/ https://gethydrate.dev/blog/slept-through-beta-launch/ Tue, 12 May 2026 09:00:00 GMT Two days before the Hydrate beta, the checklist was still a week of serial work and I was the lead developer with no team to ask. So I dogfooded the product. Three hours with Claude Code and ChatGPT produced the plan; an orchestrator Claude Code session ran it for the next fifty hours. Forty-eight commits, mostly while I was asleep. https://gethydrate.dev/blog/ingest-decisions-areas-verified/ https://gethydrate.dev/blog/ingest-decisions-areas-verified/ Thu, 07 May 2026 09:00:00 GMT The obvious way to test an LLM feature is to call the model and check what it said. Slow, expensive, and when the test fails you cannot tell if the model is confused or the code is broken. Hydrate has a clean seam in its pipeline so half the testing can happen without a model call. Free stage caught five real bugs. Paid stage cost three cents. https://gethydrate.dev/blog/model-routing-single-developer/ https://gethydrate.dev/blog/model-routing-single-developer/ Sat, 02 May 2026 09:00:00 GMT Sonnet for new decisions. Haiku for established implementation. Hydrate is the bridge. The benchmark data behind the 97% cache hit rate that lets Haiku execute against warm context, and why the realistic solo split is 80% Haiku after your first sprint. https://gethydrate.dev/blog/100-developers-claude-code-cost/ https://gethydrate.dev/blog/100-developers-claude-code-cost/ Fri, 01 May 2026 09:00:00 GMT Anthropic quietly revised their Claude Code cost estimates upward. Average developer: $13/day. 90th percentile: $30/day. For a 100-person team that's $343,200 a year before onboarding, churn, or model choice. Here's the full breakdown with our benchmarked savings numbers. https://gethydrate.dev/blog/what-hydrate-does-between-sessions/ https://gethydrate.dev/blog/what-hydrate-does-between-sessions/ Thu, 30 Apr 2026 09:00:00 GMT Two features, one loop. The dream system runs offline consolidation between sessions: scanning your fact store, detecting contradictions across the full corpus, producing a clarity report. The inner monologue runs during sessions, tracking goals and uncertainty. Here is what the test results show, and how to use both. https://gethydrate.dev/blog/vibe-cross-platform-memory/ https://gethydrate.dev/blog/vibe-cross-platform-memory/ Tue, 28 Apr 2026 09:00:00 GMT Alice and Bob built a Go API in Claude Code. Carol joined on Mistral Vibe and started with their full project memory on her first tool call. Then she added a logging convention. Then Alice picked it up and extended it. Full round trip: Claude Code to Vibe to Claude Code, different vendors, one shared fact store. https://gethydrate.dev/blog/tier-migration-verified/ https://gethydrate.dev/blog/tier-migration-verified/ Mon, 27 Apr 2026 09:00:00 GMT We ran real Claude Code sessions inside Docker containers (hooks firing, agents receiving injected context) and asked each agent to work from that context alone. Alice built an entire Go REST API from 13 facts and an empty directory. Bob joined cold, listed every convention without reading a file, and closed with: "this is all from injected hook context." https://gethydrate.dev/blog/team-bench-39-percent-cheaper/ https://gethydrate.dev/blog/team-bench-39-percent-cheaper/ Wed, 22 Apr 2026 09:00:00 GMT Canon propagation is the mechanism. Round 2 sessions - where teammates build on each other's work - showed 51% cost reduction and 44% fewer turns. Carol's lint task went from 12 turns to 3. Here's the full methodology. https://gethydrate.dev/blog/memory-not-smarter-cheaper-models/ https://gethydrate.dev/blog/memory-not-smarter-cheaper-models/ Tue, 21 Apr 2026 09:00:00 GMT 12 benchmarks, 5 scenarios, one finding: memory doesn't improve quality - it shifts which model you need. A 2am P0 incident, 1.84x cheaper, identical result. The 96% cache hit rate is the whole ROI story. https://gethydrate.dev/blog/tokenmaxxing-and-the-empirical-answer/ https://gethydrate.dev/blog/tokenmaxxing-and-the-empirical-answer/ Mon, 20 Apr 2026 09:00:00 GMT TechCrunch reported developers with the largest token budgets ship 2x at 10x cost; AI users see 9.4x more code churn. We measured the same gap and shipped a fix. The Hybrid cell ships 7/7 at $0.20/session - 12% of raw-Opus cost. https://gethydrate.dev/blog/hydrate-is-not-just-a-hook/ https://gethydrate.dev/blog/hydrate-is-not-just-a-hook/ Sun, 19 Apr 2026 09:00:00 GMT Hooks are the fastest-to-ship integration, but they're one of two paths. The other - MCP - works with every agent that speaks the protocol, and that's the path that actually makes Hydrate portable. https://gethydrate.dev/blog/hydrate-on-gemini-cli/ https://gethydrate.dev/blog/hydrate-on-gemini-cli/ Sat, 18 Apr 2026 09:00:00 GMT We shipped hydrate-mcp today. One Go binary, MCP over stdio, every MCP-capable agent gets Hydrate memory. Proven end-to-end on Gemini CLI. https://gethydrate.dev/blog/how-to-use-hydrate/ https://gethydrate.dev/blog/how-to-use-hydrate/ Sat, 18 Apr 2026 09:00:00 GMT The practical guide - what installing Hydrate actually does, the five patterns that make it pay off, and the one case where you should turn it off. https://gethydrate.dev/blog/how-and-when-to-dehydrate/ https://gethydrate.dev/blog/how-and-when-to-dehydrate/ Sat, 18 Apr 2026 09:00:00 GMT Dehydrate is a hygiene tool for CLAUDE.md, not a cost amplifier. When to reach for it, when to leave it alone, and the honest benchmark number from civichub.