I was in an all-night session when i ran into the lame "we've hit our rate limit with Vertex" message. Not only did it not complete the long running process, but Claude 4 seemed to completely lose track of the process afterwards and start the next thought process with "let me look at the codebase to see where to start". As if it had completely reset the running chat and started over. Any Cursor users here have any advice on how to avoid this? Is this just a Cursor problem being overloaded? Any way to mitigate memory or chat summary failure afterwards? I'm doing my best to always maintain docs, current_state.md, and todo lists etc, but these un-scheduled chat resets are a pain in my butt. Maybe move back to Augment...

I'm excited to kick off this community where we'll learn and grow with AI-assisted coding together. Whether you're writing your first lines of code or building complex applications, you'll find a home here. What to expect: - Weekly live coding sessions and Q&As every Wednesday at 7 PM CST - Hands-on tutorials and projects using the latest AI coding tools - Monthly contests with cool prizes - A supportive space to ask questions and share knowledge 🎯 Ready to dive in? Here's how to get started: 1. Introduce yourself in the #welcome channel 2. Check out our first tutorial on getting started with GitHub Copilot 3. Join us this Wednesday for our kick-off live session: "AI Coding Tools Overview" See you around! Drop any questions below 👇 What tools are you currently using for coding? I'd love to hear about your experience with AI assistants so far!