Cursor Auto Mode is acting up – anyone else?

Just saw a status update from Cursor indicating they are investigating a service degradation specifically affecting "Auto mode." For those of us who rely heavily on the agentic capabilities of Cursor to handle complex refactoring or multi-file edits, this is a bit of a headache.

When these automated modes go down, it’s not just a minor lag; it completely breaks the developer flow. If you're in the middle of a deep coding session, having your primary AI agent stall out feels like losing your co-pilot mid-flight.

In my experience, these "degradations" often stem from high latency in the underlying LLM calls or issues with the way the IDE manages the context window during autonomous tasks. It’s worth noting that while the status says they are "investigating," these types of incidents can sometimes take a few hours to fully resolve, especially if there's a backend bottleneck.

Has anyone noticed if it's a total failure or just sluggishness? If you're seeing weird hallucinations or timeouts, it's definitely the service issue and not your local setup. I'll be keeping an eye on the status page, but I'd suggest switching back to manual chat mode for any mission-critical logic until they get this sorted.

What are you guys using as a fallback when your primary AI tool hits a snag?