The First Time I Let AI Edit a Site Without Giving It My Password
Last week, at 10 p.m. in Hangzhou, I asked a coding assistant to fix an error on a client’s website. Then I froze: it needed to log in to the dashboard to investigate. The password was already in my browser, and my fingers hovered over the keyboard. I had authorized an assistant too casually before, only to discover later that its temporary files could widen the access boundary. Now, refusing to hand over my password isn’t impossible—I just have to redesign how access works.
Lend Swaps the Long-Term Key for a Disposable Card
Lend is an authorization service. I hand it the website account to manage, and it issues the coding assistant a temporary credential with restricted permissions that I can revoke at any time. The assistant can complete the assigned task without ever seeing my long-term password.
I know an indie developer named Chen Mo who runs a small WordPress site. Last year, in Suzhou, he took on a client job that required an assistant to modify theme files. Instead of letting the assistant enter the client’s hosting account directly, he used Lend to issue temporary access limited to editing the test directory. Once the changes were finished, he revoked access immediately, then had the client confirm the result. This was a very specific setup: not “stop AI from working,” but open only the door required for this particular job.
What It Costs to Replicate Today: ¥0, About 10–30 Minutes
Money: Lend can initially be used free or at a low cost; check its current pricing page for exact charges. Time: Initial setup takes roughly 10–30 minutes. For every project afterward, I repeat the authorization and revocation steps. Technical barrier: I don’t need to write code, but I do need to understand the difference between a long-term account password and temporary authorization, and confirm that the target site supports the relevant login method. First step: Open Lend’s website and click the button to create an authorization or begin setup. If I already have access to the site dashboard, I first prepare a test account with the lowest possible permissions—I wouldn’t experiment with the main administrator account.
This tool isn’t for everyone. If a project involves one or two simple changes I can click through myself in a few minutes, there’s no reason to set this up. It’s also fine not to try it now; tightening up my password-handling habits may matter more.
How I’d Choose Based on Where I’m Now
If I’m just getting started: I’d skip the hosting service for now. I’d use a separate low-privilege account and keep human confirmation in the loop. After every task, I’d check the authorization log.
If I have 1–2 clients: I’d completely separate client sites from my personal accounts, issue temporary permissions by client and task, and set a revocation time. I might first run through the process on my own test site.
If I’m scaling up: I’d turn “receive task—authorize—work—verify—revoke” into a fixed checklist and record who received which permissions and when. If someone on the team isn’t familiar with the process, I’d accompany them through one run before granting access in batches.