Why can't my AI agent log in to websites?
An AI agent usually can't log in because it starts with no session. A cloud browser has no cookies from you, so the site shows its login page, and the agent has no password to enter. Wield avoids the login step. Its recipes run in your own browser, which already holds your session. Wield never reads, copies or sends your cookies or passwords.
Three reasons logins break for agents
- No session. A cloud browser starts empty. In our benchmark, the browser-agent side ran in a fresh headless Chromium with an empty profile, so it had no login.
- A second step the agent cannot finish. A site may ask for a code or another check during login. The agent cannot complete that step for you, and Wield does not handle it either. You complete it yourself in your own browser.
- Missing login values. Some recipes read values the page keeps, such as a token, from the site's tab. If a required value is missing, the run stops with
login_required.
How Wield handles login without touching your password
Wield never reads, copies or sends cookies or passwords. Requests go out with the session you already have, from a tab of the site in your browser. Recipes cannot set Cookie or Host headers. Derived tokens are redacted from results and logs.
A recipe that needs your session is marked requires_login: true. Its login_check step is a cheap request. It passes only when you are logged in. Doctolib's login check, for example, answers 401 User not logged in when you are logged out. Wield then reports login_required instead of trying anything else.
What login_required means and how to fix it
login_required means you are not logged in to the site in this browser. The fix is simple:
- Open the site in your browser and log in yourself.
- Ask your agent again.
Wield never handles passwords, so it cannot log in for you. The troubleshooting page covers the other error codes.
Which recipes need login today
| Site | Recipe | Needs login |
|---|---|---|
| Doctolib | my-appointments, book-slot | Yes |
| Kleinanzeigen | message-seller, my-messages | Yes |
| bahn.de | my-bookings | Yes |
| Lieferando | order-status | Yes |
| Zalando | order-status | Yes |
Most of these recipes are not yet verified with a logged-in browser. The recipes registry marks Doctolib's my-appointments and Zalando's order-status as untested until a logged-in recording is made. Booking and messaging are writes. Each write stops for your Allow before its first request.
FAQ
Can Wield log in for my agent?
No. You log in yourself, in your normal browser. Wield then uses that session for the recipe. Wield does not store or enter your password.
Do I need to give my agent my password?
No. Wield does not ask for a password. Keep your password in your password manager, and log in in your browser as usual.
What happens when my login expires?
The next run that needs your session returns login_required. Log in again in your browser, then ask your agent to retry.
Does Wield complete two-factor steps?
No. Wield does not handle login steps for you. If a site asks for a second factor, you enter it in your own browser.
Which sites can an agent log in to with Wield?
Wield can use your session on any site where you are already logged in, as long as a recipe exists for that site. Recipes that need login are listed above. For a site without a recipe, you can request one.