Agent 3 attempts to test, when it can't login, overrides all authentication

I asked Agent to fix certain APIs because there was an error loading data on the page and make sure tables were properly implemented. App testing was turned on to make sure the form fill was properly saving a record to the database.

Agent ran into issues on the authentication page (it was typing in the wrong password). Agent took it upon itself to “fix” the issue by replacing the user’s password. A forced password reset by Agent seems like something that should be prevented.

1 Like

I experienced this also. It really struggles with auth, especially non-Replit auth (firebase, supabase etc.)

Use full autonomy with caution in these instances right now.

1 Like

Do you think that adding an instruction onto Replit.md to never change the auth system without specific instruction would help? How much does agent pay attention to the Replit.md file?

1 Like

replit.md instructions so far have been ineffective for me.

Yeah. It sounds like a useful thing, but in reality it does not seem to work how it should.

Looks like they fixed overriding authentication, Agent told me it failed logging in because it wasn’t given the right username/password just now.

1 Like