Intent is reread from the messages
visarga has the agent reread the user messages in the project and check code and tests against that intent. A task list stays in the project and is read twice.
Done with Valgfri agentEasy
What was done
On 16 October 2026 visarga writes that he has worked this way for half a year. He has the agent reread every user message in the project. It takes only a few minutes even on a 10,000 message project. That fresh reading of intent is used to check code and tests. For long work he generates a task list that stays in the project. Each closed gate includes what the agent said happened. The file is reviewed twice, once before implementation and once after. The formula he gives is review agents, tests and the message log. He does not name the product.
How it went
He writes that the reread takes a few minutes even at 10,000 messages. He does not give a count of bugs removed.
Worth knowing
The product is not named. 10,000 is his example, not a count from one named project. The comment shows no specific bug that was caught.
How to do it
- Ask the agent to reread the messages in [project] before it checks the code.
- Have it write what the intent was, and what the tests say.
- Read the task list once before the work and once after.
Try it with Valgfri agent
With [tool], reread the user messages in [project]. Check the code and tests against that intent. Write the gaps here. Do not deploy until I say yes.
Replace text in brackets with your own.
Done when. The gaps have been read, and nothing has been deployed unless you said yes.
Safety rule. The agent does not deploy. You read the intent and the tests before anything proceeds.
Read the original
Read the original · comment by visarga on Hacker News ·