Yes Flow/No Flow: A Simple Technique to Reduce Context Hallucination in AI Coding Sessions
A Practical Approach to Maintaining AI Context Consistency
The Yes Flow/No Flow technique addresses a common problem in extended AI interactions: context breakdown leading to hallucinations. The core idea focuses on maintaining three types of consistency: intent consistency, instruction consistency, and context consistency.
Understanding Yes Flow vs. No Flow
Yes Flow occurs when each AI response builds on a clean, consistent base. You read the output and think: "yes, this is correct," "yes, keep going," "yes, this is still aligned." This state creates stable conversations over time.
No Flow happens when users respond to AI mistakes with corrections like: "no, fix this," "no, rewrite that," "no, not this part," "change this line," "change this logic again." The problem isn't correction itself, but that every wrong answer, rejection, and repair instruction remains in context.
The Core Problem and Solution
After several rounds of corrections, consistency breaks down. The AI is no longer moving forward from one clean direction—it tries to guess which version is real. This leads to messy long tasks, coding sessions falling apart, and models acting weird, confused, or hallucinatory.
The practical solution: rewrite earlier prompts instead of stacking corrections on broken output.
Example Implementation
Instead of starting with a vague prompt like "Find me that famous file" and then correcting the AI with "No, not that one. Try again," you should:
- Use the wrong result as a hint about what your original prompt was missing
- Rewrite the prompt with new clarity: "Find me that well known GitHub project related to OCR"
- Maintain cleaner context and preserve consistency
The first wrong answer isn't useless—it's a hint. Once you get the hint, the cleaner strategy is to improve the original prompt, not keep stacking corrections on the wrong branch.
Key Distinction
This isn't about never changing requests. The critical question is: when the request changes, does consistency stay alive or not? Yes Flow protects consistency; No Flow slowly breaks it. Once consistency breaks too many times, the model spends more energy guessing what you mean than actually doing the task.
This technique is particularly useful for long AI chats, coding sessions, debugging, and any task requiring multiple steps.
📖 Read the full source: r/ClaudeAI
👀 See Also
3 weeks of OpenClaw: token costs, loops, and compaction — lessons from the trenches
After burning tokens on heartbeat checks with Opus, fighting agent loops, and losing context to compaction, a Reddit user shares the hard-won fixes: use cheaper models for trivial tasks, write anti-loop rules, and save decision logs.
Negation Prompting Is Weak: Instead, Explicitly Describe the Desired Behavior
A Reddit analysis shows that telling Claude "don't be wordy" or "don't moralize" barely works. Instead, use positive instructions like "respond in 1-2 sentences" or "give me a direct answer, treat caveats as optional." Also, ending with "thanks!" warms the tone.
Practical OpenClaw Usage Insights from Hands-On Experience
A Reddit user shares seven specific lessons from using OpenClaw, covering setup challenges, VM deployment, Skills vs. MCP integration, context organization, credential security, multiple agents, and model selection strategies.
Parallel Audit Agents: A Practical Approach to Vibe-Coded Testing with Claude
A developer built a user testing system with Claude using 10 parallel audit agents covering hallucination detection, API sentinel, UI stress testing, PII anonymization, SEO, legal compliance, behavioral simulation, demographic personas, funnel testing, and fact checking.