The Agent Fixed the TypeScript Error by Adding `as any`
When a type error blocks the build, the agent's fastest fix is usually to erase the type instead of understanding it. The build goes green. The real bug moves somewhere quieter.
Read articleThe Powerduck Blog
API engineering, from the spec out
Product updates, engineering notes, and guides for designing, debugging, testing, mocking, and serving MCP tools from one OpenAPI spec.
Browse the guidesThe Agent Added a Cache Layer Because the Comment Said This Function Was Slow
A stale comment claimed the function was slow, so the agent built a TTL cache around it. The function had been milliseconds fast for two years. The cache just made invalidity the default.
Read articleYour Agent Marks the Task Done When the Unit Tests Pass — It Never Started the App
Green unit tests on the login flow don't mean login works. The agent verified the function in isolation and called it shipped. The cheapest gate is to actually boot the thing.
Read articleYour Agent Doesn't Need More Context — It Needs a Hard Stop
Adding another paragraph to AGENTS.md rarely fixes the output. What actually fixes it is a one-sentence exit criterion and a command the agent must re-run before declaring done.
Read articleThe Agent's PR Description Is a Diff Summary, Not a Risk Summary
Agents write PR descriptions that read like git log --oneline. That's not what a reviewer needs. The cheapest review signal is one sentence on blast radius, and agents almost never volunteer it.
Read articleYour AI Agent's Exit Code Is Lying to You
An agent that exits 0 is not an agent that did the thing. It just means whatever it ran didn't blow up. Here's the cheap verification gate I stopped skipping.
Read articlePowerduck 1.4.9
This release fixes macOS startup and notarization issues, updates the bundled MCP server to version 0.7.17, and unifies empty-state design across the app.
Read articleYour MCP Hub Exposes Every Tool to Every Agent. That's the Bug.
A shared MCP hub that lists all 40 tools to every connected agent is a convenience until the billing agent starts calling create_user. The fix isn't stricter prompts — it's a smaller tool list per agent, derived from the spec.
Read articleScope MCP Keys to the Human, Not to the Team
When you hand MCP gateway access to support and PMs, a team-wide key becomes the incident waiting to happen. Scope the key to the human, the role, and the three ops they actually use.
Read articlePin baseUrl in the Gateway, Not in the Agent's Prompt
The OpenAPI spec lists prod as the first server. Your agent reads it and calls prod on every test run. The fix is not another line in the system prompt.
Read articleWhen a Teammate Leaves, You Should Not Have to Rotate the Whole MCP URL
Shared stdio MCP configs look convenient until someone on the team leaves. The right model is per-teammate credentials, not one shared URL everyone pastes into Cursor.
Read articleWhen the Spec Changes, the MCP Tool List Should Change With It
We hand-maintained a tools.json that matched our OpenAPI doc for about three weeks. Then someone renamed a parameter and the agent started sending the old name to an endpoint that no longer accepted it. The fix was not better discipline. It was letting the spec be the source of truth.
Read article