Five Go HTTP stacks, one benchmark rig, real numbers.
Go ships a production-capable HTTP server in its standard library, and since Go 1.22 the built-in router handles method matching and path parameters on its own. The framework question has narrowed, not disappeared.
A software factory built from agent skills
AI coding agents can already write functions, modify repositories, run tests, and open pull requests. The harder problem is getting an agent to follow a repeatable engineering process before, during, and after the code is written.
No reject state. Here's the workaround.
An agent that proposed “move persistence into a shared library” six months ago will happily propose it again unless something durable says it was already rejected – and OpenSpec has no built-in state for that today.
Specs as deltas, not a 40-page PRD.
OpenSpec is a free, open-source CLI from Fission AI that gets you and your coding agent to agree on a change in plain Markdown before any code gets written, without the phase-gated ceremony of heavier spec-driven frameworks.
OpenCode from the command line, in practice
OpenCode’s command-line interface is built for scripting, CI pipelines, and unattended agent runs. This article is a practical guide to using it in daily work.
Enforced SDD skills, installed in one command.
Superpowers packages a full spec-driven methodology into installable Claude Skills, enforcing brainstorming, planning, subagent-driven implementation, and strict TDD instead of leaving that structure up to you.
A small coding agent that expects you to shape it.
Pi Coding Agent is a minimal, open-source terminal coding harness that ships with four default tools and leaves most of the behaviour to extensions, skills and your own workflow.
Delegate the noisy work, keep your context clean.
Most Claude Code sessions get slow and cluttered for the same reason: every exploratory grep, every log dump, and every “let me check one more file” stays in the main conversation forever.
Stop poison messages from blocking queues
A dead-letter queue is the safety net that catches messages your consumers cannot process, so one broken payload does not block or silently drop everything behind it in the queue.
Stop cascading failures in Go microservices.
A circuit breaker stops your Go service from hammering a failing dependency, preventing cascading failures that consume goroutines, sockets, and memory until the entire system collapses.
Protocol security is who may act, not the model.
Prompt injection gets most of the security attention in LLM systems, and it deserves attention, but it is not the whole problem once agents start calling tools and delegating work to other agents.
Long-running A2A tasks outlive chat sessions.
Most AI agent demos still behave like chat completions with extra steps: you send a prompt, wait a few seconds, and get an answer back in one response.
40% of multi-agent pilots fail. Here's how to pick the right orchestration pattern - and avoid the ones that break.
Single-agent AI systems peaked in 2025 — you gave one LLM a prompt, some tools, and a goal, and it did reasonably well on bounded tasks.
Write the event with the data. Never split them.
Two writes that should succeed together will eventually fail separately.
Your order service saves the order to the database, then publishes an order.created event to a message broker.
Go context is control flow, not storage.
Go’s context.Context is simple enough to use badly — and that is the problem.
Handle errors at the right boundary.
Go error handling is easy to complain about. Every Go developer has written this code hundreds of times:
