I know it has to do with the massive f… up that anthropic has done to … basically the whole planet with their degraded opus 4.7 and obviously as such, replit no different in the ecosystem, but… lately the Replit agent has been hitting me hard on my nerves with this recently introduced bug .
“Agent declined to respond to this request due to a violation of our content policy.”
And it goes on and on, spams of this line, countless…
Worst part ? This 4.7 is acting like a terminator rather than a builder, destroyer on steroids.
Anything that has to do with my cloudflare configs / databases and oauth specific stuff 4/5 prompts are being refused to proceed from the begining, or even worse, the agent starts working on changes and suddenly decides to refuse , when prompted again it acts confused not knowing exactly what was stopped or refused, and starts degrading the plans afterwards…
Instead, whenever i see the refusal message in the middle of the prompt i prefer to just stop it completely and redo the prompt from the start, sometimes it works, sometimes it doesnt, this brought all sorts of problems on my projects where its making your life not just a pain… but something that hurts even more and i cant say it here for obvious reasons, really thick.
So my basic question to every kind builder who is reading this… What do you do when you hit these model blockers knowing that the model is refusing to work for false reasons.
I tried other methods of switching the prompts a little bit, using kimi 2.6 or even just ChatGPT and they seemed to work around… sometimes!
Do we have any update on Replit’s end about this situation ? I havent seen discussions talking about it, anywhere yet
Issue with one of my projects while updating a change to stripe. I changed the request to the agent and it worked. You can change your approach to making changes or updating a project. It depends on what changes were made in Replt during updates that have been implemented during updates to the agent. Cloudflare being a good example.
I figured out that if you click on NEW CHAT which is on top of the chat window , then the issue goes away. This solution was given by replit support team
Continue your dialogue or command under new chat option.
Its not enough though… this problem is mainstream and discourse gets checked only by a handful of people
Since today is the last day (Also birthday lol) of the discounted token charges Replit should find work arounds that inform everyone on this in the agent interface, somehow… its just burning tokens and its going to get people pissed
Happened 10 minutes ago, going new chat solves it most of the times, but not always, you have to repeat and repeat a few times even on the new session, burning 50 cents on the discount each time, now it will start to feel way worse
The real Solution is for Replit to not charge users for fixes on apps we build that are due to agent error. If for example you are building deep into a project and you have issues unrelated to your app that are caused by the agents. Fixing bugs should be free. So as you mentioned burning tokens to fix bugs can be expensive. However, I don’t know if that will happen at scale. The company might see it as loss revenue. I have used platforms that don’t charge tokens for fixing certain bugs.
