Overwhelming consensus: AI coding workflows, especially with Claude Code, suffer massively from context loss and switching—users waste time re-explaining projects across sessions or juggling multiple tools/projects. No contrarian takes; everyone agrees 200K tokens isn't enough for large projects, leading to "amnesia" that kills productivity. Surprise: Devs aren't waiting for fixes—they're hacking persistent memory, session forking, search tools, and time-blocking to 10x workflows.

Multi-project context switching ranks as the #2 pain after code review in teams, with solo builders splitting time across apps/tools. YouTube echoes this, promising to eliminate the "first 10 minutes of re-explaining." Strong push for continuity via auto-save/recall, dedicated sessions, and custom monitors.

Most Mentioned

• Context Switching — 9 mentions
  Brutal for multi-project work, tools like Claude/Cursor/Codex, and team features; causes confusion, lost focus; mitigated by time blocks, project monitors, dedicated sessions.
  Sources: X (1,3,8,9,10,12,13), Reddit (5,6)
• Claude Code Context/Memory — 8 mentions
  Default setup forgets sessions/projects; 200K tokens insufficient for large codebases; hacks like persistent auto-save/recall, session search/forking essential for continuity.
  Sources: X (2,9,10), Reddit (4,5,6,7,11)
• Persistent Memory Solutions — 4 mentions
  Custom tools auto-save conversations, recall context, enable instant search across sessions; directly tackles amnesia in agentic/long-term coding.
  Sources: X (2), Reddit (7,11), YouTube (15)

Key Patterns

1. Amnesia Across Sessions — AI tools like Claude Code default to stateless convos, forcing constant re-contextualization; users build persistent memory, forking, and search as workarounds.
2. Multi-Project/Tool Juggling — Devs bounce between projects (e.g., iOS app + B2B) and apps (Claude, Cursor); time-blocking and monitors emerge as top mitigations.
3. DIY Fixes Dominate — No reliance on vendor updates; community ships free tools for session search, auto-recall, and workflow monitors to enforce continuity.
4. Large Project Focus — Issues amplify on big codebases/architecture; emphasis on structure, transcripts, and avoiding "context pollution" via task-specific forks.