[Bug] Excessive token consumption in multi-turn conversations causing premature rate limit exhaustion
Resolved 💬 5 comments Opened Jan 12, 2026 by JonathanMandel Closed Feb 27, 2026
Bug Description
This conversation, starting with "I've fixed the compilation errors. Continue with the implementation." used up 68% of my 5-hr "Pro" usage. This problem has been going on since Dec 30. I do not have time to continue documenting this for you guys. I've gotten one response, 5 days ago, saying "This is a known issue". That's it. At this point, I am looking at other coding tool solutions. Augment looks like a pretty good alternative. Claude is essentially useless if I can only give it 3 prompts in a 12-hour period. Before Dec 30th, a similar conversation would consume 12-15% of my usage.
Environment Info
- Platform: win32
- Terminal: null
- Version: 2.0.76
- Feedback ID: 2ad2e7cd-3d0b-4f84-88b4-cffac0248166
Errors
[{"error":"Error: Plugin hook \"node \"C:\\Users\\jon\\.claude\\plugins\\cache\\thedotmack\\claude-mem\\8.5.4/scripts/user-message-hook.js\"\" failed with exit code 3\nstderr: 📝 Claude-Mem Context Loaded\n ℹ️ Note: This appears as stderr but is informational only\n\n\n\^[[1m\^[[36m[Bakezap] recent context\^[[0m\n\^[[90m────────────────────────────────────────────────────────────\^[[0m\n\n\^[[2mLegend: 🎯 session-request | 🔴 bugfix | 🟣 feature | 🔄 refactor | ✅ change | 🔵 discovery | ⚖️ decision\^[[0m\n\n\^[[1m💡 Column Key\^[[0m\n\^[[2m Read: Tokens to read this observation (cost to learn it now)\^[[0m\n\^[[2m Work: Tokens spent on work that produced this record (🔍 research, 🛠️ building, ⚖️ deciding)\^[[0m\n\n\^[[2m💡 Context Index: This semantic index (titles, types, files, tokens) is usually sufficient to understand past work.\^[[0m\n\n\^[[2mWhen you need implementation details, rationale, or debugging context:\^[[0m\n\^[[2m - Use the mem-search skill to fetch full observations on-demand\^[[0m\n\^[[2m - Critical types (🔴 bugfix, ⚖️ decision) often need detailed fetching\^[[0m\n\^[[2m - Trust this index over re-reading code for past decisions and learnings\^[[0m\n\n\^[[1m\^[[36m📊 Context Economics\^[[0m\n\^[[2m Loading: 5 observations (1,690 tokens to read)\^[[0m\n\^[[2m Work investment: 7,235 tokens spent on research, building, and decisions\^[[0m\n\^[[32m Your savings: 5,545 tokens (77% reduction from reuse)\^[[0m\n\n\^[[1m\^[[36mDec 31, 2025\^[[0m\n\n\^[[2mGeneral\^[[0m\n \^[[2m#351\^[[0m \^[[2m12:37 PM\^[[0m 🔵 \^[[1mBakeZap Project Architecture and Development Guidelines\^[[0m\n \^[[2mBakeZap is a Kotlin Multiplatform application for bakery formula management. The architecture consists of a Kotlin/JS frontend using Fritz2 framework with Tailwind CSS, and a Kotlin/JVM backend using Ktor 3.0.x. The application integrates with Supabase for authentication and PostgreSQL database storage. Development follows strict guidelines including the \"FAIL FAST, FAIL HARD\" principle which mandates throwing exceptions rather than implementing fallback code. Critical restrictions include never using Map<String, Any> type collections in server code due to Ktor serialization limitations, and never modifying configuration files in server/config/ that contain irreversible secret keys. The project supports both development (localhost) and production (Digital Ocean) environments with corresponding Supabase projects. Development tools include MCP claude-context for semantic search and ripgrep for code searching. The app runs in a hot-restart environment managed by the developer.\^[[0m\n \^[[2m(~528t)\^[[0m \^[[2m(🔍 2,496t)\^[[0m\n\n \^[[2m#352\^[[0m 🔵 \^[[1mprocessAndStoreSession() Method Usage Across Codebase\^[[0m\n \^[[2mThe processAndStoreSession() method is defined in the LoginUser.kt file within the commonMain source set, making it available to both JS and JVM platforms. The method signature is \"suspend fun processAndStoreSession(): ServerLoginResponse\" and is part of the SessionManagementService. The function is invoked across multiple parts of the application including routing logic, HTTP session handling, Stripe pricing page interactions, and internal authentication workflows. A key inconsistency exists in how the method is called: HttpSession.kt calls it as a static method (SessionManagementService.processAndStoreSession()) while other files instantiate the service first (SessionManagementService().processAndStoreSession()). This discrepancy at line 177 of HttpSession.kt is likely the source of the \"unresolved\" error mentioned in the user's question.\^[[0m\n \^[[2m(~383t)\^[[0m \^[[2m(🔍 1,27
Note: Error logs were truncated.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗