Reader · no content
No body text on file.
Open the original to read the full piece.
8 out of 10 agent frameworks launched in 2026 will be dead by Q4 2026; the two…
Brief
Agent frameworks: @code_rams warns that 8 of 10 frameworks launched in 2026 will be defunct by Q4 and recommends filtering launches with five practical tests (longevity, production postmortems, non-disruptive adoption, cost of skipping, measurable evals). He urges investing in five compounding primitives — context engineering, tool design, orchestrator-subagent, evals/golden datasets, and file-system-as-state — and flags AutoGen and CrewAI as poor production bets.
Why it matters
8 out of 10 agent frameworks launched in 2026 will be dead by Q4 2026; the two survivors won’t be the frameworks trending at the time (post by @code_rams on 2026-04-30).
Key details
- Run five tests on any new launch: (1) Will it matter in 2 years (wrappers around frontier models have ~6-month half-lives; primitives like protocols/memory/sandboxing last years)? (2) Has a respected team shipped production and published a postmortem? (3) Does adoption force replacing tracing/retries/auth/config? (4) What’s the cost of skipping 6 months (usually zero)? (5) Can you measure real benefit with evals?
- Prioritize five primitives: context engineering (manage state to avoid token bloat), tool design (5–10 well-named tools beats 20 mediocre — one team cut retry loops 40% by rewriting error messages), orchestrator-subagent pattern (default to single-agent), evals + golden datasets (50 hand-labeled examples is a good start), and file-system-as-state with think-act-observe (seen in Claude Code, Cursor, Devin, Aider). Skip AutoGen and CrewAI for production, naive parallel multi-agents, autonomous-agent pitches, and per-seat pricing; single-model-only agents are a smell.