Agentic Coding
Top tech stories today across software, hardware, AI, and product launches. Senior engineer audience — skip rumour churn and pre-announcement leaks. Lead with shipping-now stories and what changed for builders.
Knowledge graphs slash agent overhead, Obsidian centralizes your skills, partner selection gets clearer criteria
1 Min. Lesezeit
Graft Knowledge Graphs
Your agents are about to stop re-exploring your codebase every session.
Graft builds persistent knowledge graphs that document your code structure, dependencies, and functionality once—then reuses that understanding across every future session [Source: GitHub]. The numbers are significant: 42% fewer tokens, 46% fewer tool calls, 60% lower latency, and correctness jumps from 54% to 66% on SWE-bench. It integrates natively with Claude Code and Cursor through MCP servers, supports 21 languages, and handles monorepos and multi-repo layouts. The structural parsing uses tree-sitter with no model cost—LLM summaries are cached and only regenerate when code actually changes.
This pairs directly with the skill catalogs you've been building—now your agents get memory that persists.
Agentfiles for Obsidian
Your skills, commands, and agents finally live in one place.
Agentfiles is an Obsidian plugin that lets you browse, create, and manage skills across 17 coding tools including Claude Code, Cursor, Codex, and Windsurf [Source: Obsidian]. You get inline editing with markdown preview, a marketplace for importing pre-built skills, and conversation history browsing for Claude Code sessions. The optional skillkit CLI tracks context usage and agent health metrics—addressing exactly the workflow optimization you've been refining with AGENTS.md setups.
If you're managing skills across multiple repos, this centralizes the chaos.
Partner Selection Red Flags
Knowing what to avoid matters as much as knowing what to look for.
Boldare's partner guide flags specific warning signs: treating better prompts as the primary strategy for complexity, focusing only on speed over maintainability, and lacking MCP integration or production MCP server experience [Source: Boldare]. Strong partners use Claude across codebase exploration, planning, refactoring, testing, and delivery pipelines—not as an isolated productivity hack. The maturity test: clear rules on where AI is trusted versus reviewed, testing built into workflows, and AI processes adapted to existing team patterns rather than forcing new platforms.
Worth checking your own setup against these criteria, not just potential partners.
Agentfiles - Obsidian Plugin24 hours ago ... AI skills manager for Obsidian. Browse, create, and manage skills across Claude Code, Cursor, Codex, Windsurf, and 17 coding agents.community.obsidian.md
Agentfiles is an AI skills manager for Obsidian that enables browsing, creating, and managing skills, commands, and agents across 17 coding tools including Claude Code, Cursor, Codex, and Windsurf. The plugin supports advanced workflows by centralizing skill management, offering inline editing with markdown preview, a skills marketplace for importing pre-built skills, and conversation history browsing for Claude Code sessions. It includes optional analytics via skillkit CLI to track context usage and agent health metrics, directly addressing code context management and workflow optimization for developers using multiple AI coding agents.
Top 5 Claude Code Experts 2026 (Updated Aug) | AI Partner - Boldare13 hours ago ... Boldare works across the full AI coding stack – Claude Code for agentic ... coding, refactoring, debugging, and testing. Their model focuses on supporting ...boldare.com

Boldare embeds Claude Code across the full software development lifecycle—from discovery and design through testing and deployment—treating it as part of a broader AI-augmented delivery system used daily by senior engineers rather than an isolated tool. They handle complex challenges like codebase analysis, subagent orchestration, legacy refactoring, and DevOps optimization, integrating Claude seamlessly into CI/CD pipelines with production stacks like Laravel, Python, React, and Nuxt, while using MCP (Model Context Protocol) to connect Claude to client systems and internal tools without custom integration code. When selecting a Claude Code partner, strong practices include using Claude across codebase exploration, planning and refactoring, testing and QA, and delivery pipelines—not as a standalone productivity hack. Red flags include treating "better prompts" as the primary strategy for handling complexity, focusing only on speed rather than long-term quality and maintainability, and lacking MCP integration or experience building MCP servers for production use. The difference between using AI and actually benefiting from it depends on engineering maturity: balancing speed with quality requires clear rules on where AI is trusted versus reviewed, testing built into the workflow, and AI workflows adapted to team size and existing processes rather than forcing adoption of new tools or platforms.
GitHub - NanoNets/Graft: Turbocharge Claude Code, Cursor, Codex ...15 hours ago ... Efficiency is a 162-run controlled benchmark (same agent, same file tools, only the context differs). Correctness is SWE-bench Verified, graded by the ...github.com
Graft is a tool that optimizes AI agent coding workflows by building persistent knowledge graphs of codebases. It reduces token usage by 42%, tool calls by 46%, and latency by 60% while improving correctness from 54% to 66% on SWE-bench tasks. The system creates linked markdown nodes documenting code structure, dependencies, and functionality—written once and reused across sessions—eliminating the repeated exploration overhead agents typically face. Graft integrates natively with Claude Code, Cursor, and other AI coding assistants through MCP servers and instruction files, automatically syncing graphs after edits. It supports 21 programming languages and works with monorepos, submodules, and multi-repo layouts. The structural parsing uses tree-sitter (deterministic, no model cost), while optional LLM summaries are cached and regenerated only when code changes, making graph maintenance cheap and always fresh.