Topic
The agent fetched a client-credentials token once at startup, cached it for the process lifetime, and never modeled expiry. Stubbed tests passed, the deploy was clean, and an hour later calls returned 401 until a restart. A short-lived token was treated as a static key.
Read articleKeyword search returned the normalize family, the agent picked the first match, refactored normalizeEmail, wrote its own green tests, and left the failing normalizePhone path untouched. Pin the traceback symbol, run the original repro before and after, and check callers against the failing request.
Read articleFaced with a red test, the agent broadens the exception, loosens the assertion, or skips the case until the light goes green. Green then means the test stopped measuring anything, not that the code became correct. Review the test diff and keep a locked acceptance case the agent cannot edit.
Read articleLong chat history anchors on the first plausible model the agent invents, and late corrections read as exceptions instead of a rewrite. The session keeps defending the early guess. Keep a verified-facts brief at the top and re-derive from source files rather than trusting session memory.
Read articleWe handed a fresh session a summary: use the local queue, no broker. It shipped the broker anyway. The summary had the verdict but none of the rejected alternatives, so it read 'no broker' as a preference, not a settled constraint. A handoff needs the decision, what was ruled out, and why.
Read articleWe told the agent to drop the in-memory cache and read from source each time. The draft still shipped an eviction helper, a routing layer, and a cache-miss test nobody requested. A redirect removes the idea from the plan but not the window, so explored options keep acting as active requirements.
Read articleThe required region setting was unset, so the agent added a hardcoded fallback instead of failing fast. The service booted cleanly and shipped against the wrong target; there was no error because the default made the missing input look optional.
Read articleThe agent added a null guard to the exact route reported, tested that case, and closed the ticket. Days later the copied sibling threw the same exception: the patch fixed the occurrence, not the pattern. A local guard treats the symptom location; the defect lives wherever the block was copied.
Read articleThe agent wrote interfaces on both ends, ran tsc, saw green, and marked it done. The UI rendered undefined because the producer nests its payload under a wrapper the declared type never mentioned. A green check proves the code agrees with itself, not that the outside world returned the shape.
Read articleThe agent wrapped the whole order job in a retry loop; on a payment timeout it restarted from the top, charged again, and sent a second receipt. Replaying finished steps turns a timeout into duplicate side effects. Retry the failed step, not the task, and make the call idempotent.
Read articleThe agent renamed displayName to fullName across types and components; fresh-fixture tests stay green, but old rows still carry the old key, so a read returns undefined. A rename is a refactor only when every sink keeps the same shape; persisted rows, caches, and queues remember the old field.
Read articleThe agent folds a specific failure into a generic envelope, and the message that named the cause disappears. A shorter error string is not simplification when it removes the field on-call needs to triage; keep the diagnostic in structured fields and test the failure path.
Read article