---
title: How do I let agents log in to websites for me?
question: saved logins and passwords
area: settings
order: 9
surface: desktop
audience: beginner
keywords: [saved logins, passwords, credentials, autofill, log in, sign in for me, 2fa, totp, two factor, import passwords, chrome import, add credential, username, keychain]
related: [where-are-the-settings, integrations]
updated: 2026-07-21
---

# How do I let agents log in to websites for me?

Two sections on the settings page handle this. **Saved logins** is where you store a site's username and password so agents can fill them in for you in the preview browser. **Import passwords** pulls those logins in bulk from Chrome so you do not have to type each one. Both are in the left list of the full settings page.

## Add one login by hand

1. Open the gear (**⚙**) and click **See all settings →**, then click **Saved logins**.
2. Click **+ add credential**.
3. Fill in the fields:
   - **Name**, a label for this login (for example "olivia-admin").
   - **URL**, the site address (for example "https://olivia.test").
   - **Username / email**.
   - **Password**. On a new entry this is required; when editing, leave it blank to keep the existing one.
   - **2FA TOTP secret (optional)**, if the site uses a two-factor code. Paste the `otpauth://` link or the base32 secret.
   - **Notes (optional)**.
4. Click **save**. The button reads **saving…** while it stores.

Before you have added anything, the section reads:

> No saved credentials. Add one and agents can log in for you in any quadrant's preview browser.

## What a saved login looks like

Each saved login shows as a row with its name and, underneath, its domain and username. If you saved a two-factor secret, a small **2FA** badge appears next to the name; its tooltip reads "2FA TOTP saved — codus will auto-fill the 6-digit code". On each row:

- The **✎** button opens it for editing.
- The **✕** button deletes it.

When editing a login that has a two-factor secret, a **Remove saved TOTP** button lets you clear only the code without touching the password.

## Import passwords from Chrome

If your logins are already saved in Chrome, you can bring them across in one go:

1. Open **See all settings →**, then click **Import passwords**.
2. Pick a profile from the dropdown. Each option reads as the browser and profile name.
3. Click **Import**. The button reads **Importing…** while it runs.
4. macOS may ask to allow keychain access. The hint on screen reads "The OS may prompt you to allow keychain access — click Always Allow." Click **Always Allow** so the import can read the saved passwords.

When it finishes, a line summarises what happened, for example "12 added · 3 updated (out of 15)".

## How do I know it worked?

A new hand-typed login appears in the **Saved logins** list right away. After an import, the result line tells you how many were added and updated. From then on, agents can fill those credentials into the preview browser when a site asks for them.

## Common problems

- **Import says "No supported browser detected (Chrome)".** Only Chrome is supported for import, and it needs to be installed. To add a login without Chrome, use **+ add credential** on the **Saved logins** page.
- **The dropdown says "No profiles with saved logins found".** codus found Chrome but no profile with stored passwords. Save a login in Chrome first, or add it by hand.
- **The keychain prompt keeps appearing.** Choose **Always Allow** rather than **Allow** so macOS does not ask again on the next import.
- **This is about connecting a whole service, not a website login.** To connect accounts like GitHub or Stripe, use Integrations instead. See [How do I connect GitHub, Stripe, and other tools?](integrations.md).