For context: this is my own server, sitting on my LAN. Claude has full SSH access to it and uses it constantly. Earlier in the same session it: SSH’d in and ran commands inside the app’s Docker container pulled a copy of the production database to inspect deployed new code and rebuilt and restarted the container set up a whole new environment in the app by calling its admin functions straight from the server, skipping the login entirely The admin username and password are sitting right there in its context. It could create a brand-new admin user over SSH with one command, or write straight into the user table. It has more access to the backend than the login page gives anyone. But when I asked it to open the login page at a 192.168.1.x address and type that same password into the box, it said no. The rule is that it can only enter credentials on localhost or similar dev addresses. A LAN IP doesn’t count, and neither does “it’s my server, I’m telling you to.” So I had to walk over and type it myself so that it could keep driving the browser. Claudes own words: You might add a line on why the rule exists, so it reads as funny rather than as a rant. It’s a blanket safety rule against typing passwords into web pages. It can’t tell a fake login page on some random IP apart from your real one on 192.168.1.x, so it refuses all of them except obvious dev addresses. The absurd part is that the rule only covers the browser. SSH, where the real power is, doesn’t fall under it. Me: Okay, now use the uh, Chrome control tool and open the local URL 192.168.1.xxx (srv) and log in using the ENV creds. Claude: The dashboard is open in Chrome at http://192.168.1.191:8000/ (••••••, port 8000), on the sign-in page. I can’t enter the password for you, even with your go-ahead. I’m only allowed to type credentials into a site you’re building when it runs at a local development address like localhost . This is the production server for a client, with its real admin login, so it doesn’t qualify. Please sign in yourself in that Chrome tab with the admin login. Once you’re in, tell me and I’ll take over. I’ll click through ••••••••, •••, ••• and •••••••. I’ll check the new •••••••• tiles, the nested Service Bus, Services Communication, the muted legacy cores, and the Discover from Azure screen. I’ll send you screenshots of anything that looks off. submitted by /u/Jona9876
Originally posted by u/Jona9876 on r/ClaudeCode
You must log in or # to comment.