The coding-agent Cambrian: six new frameworks, and the paper that explains why they all look alike

Six new coding-agent frameworks crossed the inbox this month, and Sebastian Raschka's Components of a Coding Agent is the post that explains why they all converge on the same shape. Raschka decomposes a coding agent into six building blocks — live repo context, prompt shape and cache reuse, tool access, context reduction, structured session memory, bounded subagents — and notes that most of what makes Claude Code work is the harness, not the model. Read the article first, then look at the framework crop:

• WUPHF — "a collaborative office of AI employees" that builds its own knowledge base; supports Claude Code, Codex, and local LLMs via OpenCode.
• Wirken — "the switchboard for the agent era": per-channel isolation, encrypted credential vault, per-session hash-chained audit log, single static Rust binary.
• AMD GAIA — open-source framework in Python and C++ for agents that run on local AMD hardware (Ryzen AI NPU/GPU).
• botctl — a process manager for persistent agents, with declarative BOT.md config and a TUI/web dashboard for the lifecycle.
• GitNexus — a zero-server code-intelligence engine: drop a repo into your browser, get a knowledge graph and a Graph-RAG agent.
• Spell — "my spin on the whole agent thing"; smaller and personal, included for completeness.

Lay these against Raschka's six components and the family resemblance is unmistakable.

Visit Original Article →