---
title: "Comment by Kartik N V J K on \"When your coding agent repeats a mistake, move the lesson out of chat.\" | Hashnode"
description: "Judging the setup by what happens when a mistake recurs, not by one good session, is a sharp way to think about agent reliability. The six-place breakdown is us"
url: "https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7/comment/6a723eff95c5452a78aa6d1e"
---

[Discussion](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7)

Comment [When your coding agent repeats a mistake, move the lesson out of chat.](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 4](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7/comment/6a723eff95c5452a78aa6d1e)

Judging the setup by what happens when a mistake recurs, not by one good session, is a sharp way to think about agent reliability. The six-place breakdown is useful precisely because it forces the question of where a correction belongs, since piling every rule into agent config is what makes the important instructions get lost. For the mistake-log-plus-regression-test path, how do you keep that suite from growing into something the agent spends more time satisfying than the task itself?

[Bryce Darling](https://hashnode.com/@mindrealm)

[Aug 4](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7/comment/6a723eff95c5452a78aa6d1e#reply-6a727692c0efcb54d46b680f)

I don't optimize for keeping the suite small. I'm biased because I've been doing TDD for two decades, but I think automated testing matters more when agents can produce more code than a person can realistically inspect line by line. I treat test code as production code. Mindrealm reviews the tests too: weak assertions, mock abuse, flaky tests, state leaks, and public functions or methods with no corresponding test. If an agent spends time satisfying a valid test, that's part of the task. If a test no longer protects behavior we care about, I decide whether it gets fixed or deleted.

For a prototype or proof of concept, who cares. Ship it without tests. If a team has to maintain it, the test suite is part of the product.
