Gemini quality complaints raise workflow risk for solo makers
and 3.5 Flash have drawn a wave of complaints about worse answers over the past few days or week. Pro was described as handling instructions too rigidly, missing nuance, and forcing extra cleanup on complex work.
Flash was expected to be weaker, but Pro becoming hard to use for serious tasks changed the calculation. Other reports described Gemini giving generic research plans instead of doing the deeper work requested, or asking users to paste material again after failing to handle the current context.
Developer complaints also touched Gemini CLI, where an open-source TypeScript tool was said to have been replaced by a closed Go binary, with users moved into one shared quota pool and some Pro subscribers hitting 403 errors during sessions. A reported delay of to July added to the concern, especially for people with long AI Studio histories, including about 1.5 million tokens of past chats that may need to be moved elsewhere.
Key points
- Gemini Pro is being criticized for rigid answers and weaker handling of complex requests.
- Long AI Studio histories can become a migration problem when users lose trust in the model.
- Gemini CLI complaints add a separate concern about developer workflow stability.
- A reported delay makes some users less confident in a quick fix.
- Solo makers should keep backup model workflows for important coding and research tasks.
Sources covering this story (7)
- r/BardGemini quality complaints raise workflow risk for solo makers ↗
- r/GeminiAIInteresting Answer When I Asked Gemini Why It's So Much Worse Than It Was ↗
- r/GeminiAIGoogle training the new model and our patience ↗
- r/GeminiAISome gemini problems ↗
- r/botmonsterGemini CLI is dead ↗
- r/GeminiAIGemini admitted its own issue? ↗
- r/GeminiAIIs it just me or has Gemini gotten wor- ↗