User discovers AI chat logs bloated by single-line rule causing instruction failure
A Reddit user reports that their AI chat agents stopped following instructions because a rule to trim notes to 120 lines was misinterpreted: each line was excessively long, causing context bloat. The user had instructed chats to keep session notes and trim them at 120 lines, but the agents complied literally, resulting in lines that were too long and degraded performance.
Entities
Related
Developer open-sources agent-instructions repo to curb AI coding agent degradation
A developer frustrated by AI coding agents losing context and hallucinating after about 10 minutes created a set of rules to keep them on track. The rules, shared as an open-source GitHub repo, aim to reduce the need for constant reminders and prevent infinite loops. The project has gained attention from other developers facing similar issues.
Developer discovers chatbot quality degrades after 5 turns
A developer reports that their chatbot, which passes quality evals on short interactions, gradually loses context after about 5 turns, forgetting user constraints and contradicting itself. This highlights a common limitation in current conversational AI systems.
Users report Claude Code consuming excessive usage due to large context bug
Multiple users report that Claude Code consumes 20-40% of their usage allowance per session due to a bug that sends 300k+ message contexts even on fresh sessions. One user lost significant paid usage before realizing the issue. Another user describes a layered configuration setup with CLAUDE.md and AGENTS.md files, and a cleanup that removed ~700MB of empty content but still faced model selection inefficiencies.
Developer reports Claude performance degrades beyond 500K tokens, uses handover files to reset context
A developer working on a large C# plugin reports that Claude becomes increasingly unreliable after 500K tokens of context, with performance degrading significantly by 800-900K tokens. To work around this, they manually create a handover.md file summarizing the project state and start a new session, asking Claude to re-read key files. The post questions whether this is common practice and whether tools exist to automate the process.
User discovers that describing desired output quality outperforms step-by-step instructions in prompts
A Reddit user reports that shifting from detailed step-by-step instructions to describing the desired outcome (e.g., 'a great version would make a busy person understand the tradeoff in ten seconds') dramatically improves LLM output quality. The post highlights that models are better at navigating to a well-defined finish line than following clumsy instructions.