Fetching from the wire…
Public story · 2026-08-03 · high
Incremental rebuilds could silently drop whole file layers, so an agent's graph query would say code doesn't exist.
Why now: Released August 1, two days ahead of this August 3 briefing.
Graphify Labs shipped version 0.9.32 on August 1, fixing a merge bug that silently dropped file layers from incremental code-graph rebuilds, per the release notes.
A dropped layer doesn't throw an error, so an agent querying the graph would just report the code doesn't exist. Anyone running Graphify for agent navigation instead of grep has been exposed since before this release.
The fix uses tier-aware merging so file layers survive graphify update. It also keeps the graph's directed flag intact through updates and corrects edge rendering in query results. Symbol resolution improves too, for C# members, Kotlin anonymous objects, and Ruby mixins.
If you run a local Graphify graph for agent navigation, upgrade to 0.9.32 and rebuild from scratch once. An incremental update on top of a graph that may have already dropped layers won't necessarily self-heal.
The prior release, 0.9.31 on July 30, supports both MCP SDK 1.x and 2.x instead of picking one, unusual for a widely installed server.
Each link below shares sources, entities, or timing with this story.
Kits like TanStack/ai (type-safe, provider-agnostic streaming, tools, and agents across OpenAI/Anthropic/Gemini) and manifest let you swap providers, and increasingly the harness itself, without rewriting (TanStack). With the model market churning weekly and June releases slip...
If you wrote an MCP server before July, it's on a protocol shape the maintainers have already removed. Not deprecated-with-a-migration-window. Removed from the spec. MCP lead maintainers David Soria Parra and Den Delimarsky published an updated roadmap on August 22, and the re...
Anthropic invented a file convention. It's now shipping GA inside a competitor's product. Nobody wrote a spec, nobody held a standards meeting, it just happened. On July 29, GitHub made agent skills and MCP server support generally available in Copilot code review for all Pro,...
Everyone writing SKILL.md files has absorbed the same folklore. Keep the top file thin. Push detail into reference files. Let the agent walk the tree as needed. More layers, more context efficiency. A controlled study submitted July 20 tested that across InfiniteBench, three a...
Graphify-Labs/graphify ships as a /graphify skill for Claude Code, Cursor, Codex and Gemini CLI using local deterministic AST parsing with no API cost. The scope claim is what separates it: non-code artifacts land in the same graph, so "which endpoint reads this table" resolve...
If you've written Claude Code skills with context: fork in the frontmatter, go check them right now. As of the July 22 release, /code-review runs as a background subagent, and any skill declaring context: fork runs in the background by default (release notes). The opt-out is b...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.