How to Use the 1Password Connector in Muse

1. The short answer

As of October 25, 2026, 1Password for Agents is launched but not fully live for everyone. 1Password announced it on October 22, 2026, with Muse rolling out first, and a waitlist applies. Saying it plainly: if you open Muse today and look for the 1Password connection, you may not find it yet, and that is expected. The rollout is happening over the coming days, and the waitlist decides who gets in first. Our Muse connectors list keeps the dated count of every connector, including which ones are announced but not live.

Here is what it does when it reaches you. When Muse hits a login page while doing a task for you, it pauses and asks 1Password for that login. You see which login it wants and why, and you approve or deny the request on your own device. If you approve, 1Password types the login straight into the form itself. Muse never receives the password, the password never lands in the chat, and once the site accepts the login, the credential is removed so Muse cannot read it or replay it later in the task. The rest of your vault stays out of reach.

The September background is short. At Meta Connect on September 23, 2026, 1Password was announced as coming soon, alongside PayPal and Instacart, so Muse could use logins you already have. The October 22 launch made it real, with Muse and the Grok Bot first in line, and Claude Duet, ChatGPT Work, and other agents listed as coming soon. This builds on 1Password for Claude, which launched July 16, 2026, and worked only on the Mac, inside Chrome. The new platform is built for agents that are not tied to one desktop browser session.

Muse is invite only right now. Need an invite code? Click here to grab one free from the community pool. Waiting on a launch in your country? Join the waitlist and we will send you a fresh code on launch day. Muse is available in the United States, Canada, and Japan.

2. What you need

• Muse access. You need an account with access first, in the United States, Canada, or Japan, where Muse has launched.
• A 1Password Individual or Family plan on 1Password.com. The feature is included at no extra cost in those plans. Accounts hosted on 1Password.eu and 1Password.ca are not supported at launch, so check which region your account sits in before you join the waitlist.
• A place on the waitlist. There is a waitlist for 1Password for Agents, and the Muse rollout is happening over the coming days. Join it, and check back: access arrives in waves, not all at once.
• Your logins already in the vault. 1Password for Agents uses the logins you already saved. If the account Muse needs is not in your vault, add it first, the same way you save any login.
• Approvals set to ask me. Before you connect anything that can sign in as you, set approvals so nothing happens without your tap. This is the single most important step on this page, and for this connector it is the whole safety model.
• Two step verification kept on. Keep two step verification switched on for the accounts that matter, and let 1Password fill the code instead of switching it off. A login without its second step is a weaker login, and an agent login is no exception.

3. How to connect it, step by step

The connection itself is short. The habit around it matters more, so run the steps in order and do not skip the approvals step. One honest note first: the rollout is still landing, so the steps below follow the announced flow. If a step looks different when access reaches you, the version Muse and 1Password show you is the version to trust.

1. Join the waitlist. Sign up for 1Password for Agents through 1Password's page. This is the queue for access, and Muse users are first in line, but first in line still means waiting for your wave. Do not look for the connection in Muse before your wave arrives.
2. Check your plan and your region. Confirm you hold an Individual or Family plan on 1Password.com, where the feature is included at no extra cost. If your account sits on 1Password.eu or 1Password.ca, it is not supported at launch, and no setting will change that yet.
3. Connect when your wave arrives. When the rollout reaches you, connect 1Password in Muse's settings. The agent proves who it is to 1Password with its own digital key, which is how 1Password knows the request comes from your Muse and not from something pretending to be it.
4. Set approvals to ask me. Do this before your first agent login. Every login request should pause for your decision. Keep this setting on while you learn what the connector does, and keep it on after. Approving per task, not forever, is the rule that keeps this safe.
5. Ask Muse to do a small task that needs a login. Pick a low stakes account first, one with no saved card and nothing sensitive behind it. When Muse reaches the login page, it will request the credential. Check which login it wants and why, then approve it on your own device.
6. Check the account afterwards. Once the task is done, open the account yourself and look at what happened: orders, sent messages, and connected apps. A quick check after the first few logins tells you whether Muse did what you asked and nothing more.

4. What it actually does

The value of this connector is not that Muse can log in. You can log in yourself. The value is that Muse can finish a task that needs a login without you handing it your password, and without you stopping to log in by hand every time. That is the gap it closes: until now, an agent that needed a login either waited for you or got a password pasted into a chat window, where a copy sat outside your control.

Booking and shopping tasks are the use most people will actually keep. Ask Muse to book a table, reorder groceries, or plan a trip, and when it reaches a login page, 1Password fills the credential itself after your approval. You do not type the password, Muse never sees it, and the task continues. The agent does the job it was asked to do without getting permanent access to everything behind the account, which is how 1Password's chief product officer put the goal.

Scoped access is the mechanism that makes it safe. Each approval covers one login for one task, and the rest of the vault stays out of reach. Muse cannot browse your vault, cannot list your logins, and cannot pull a credential you did not approve. The attack surface shrinks to the single login you approved, for the single task you asked for, instead of the whole vault.

It also pairs well with the connectors that need logins to work. Stripe, Shopify, Gmail, and the travel connectors all sit behind accounts, and Muse reaches them through their own connectors, not through passwords. 1Password for Agents covers the rest: the sites with no Muse connector, where a login is the only way in. That is where it earns its place, as the bridge for everything that has no connector yet.

It is also optional and reversible. Connecting 1Password is a choice, and you can disconnect it whenever you wish. 1Password still works as before without connecting any agent. If you try it and decide the trade is not worth it, disconnecting returns you to exactly where you started, with nothing lost.

5. What it cannot do

It cannot keep Muse from acting inside an account once it is signed in. This is the catch, and 1Password's own FAQ says it plainly: an agent may be able to see information or take actions inside an account once it is signed in. Hiding the password does not limit what the account itself allows. If you approve a login to your airline account, Muse can do whatever that account allows. The password is protected. The account is not, beyond your approvals and your own checks afterwards.

It cannot make banking safe. Banks are uneasy about agents working inside customer accounts, and some have started blocking third party agents or rewriting their terms. Keep email and banking out for now. Email can reset every other password you own, and a bank account is the one place where an agent mistake costs real money. Use the narrowest account you can, one with no saved card, or a low limit card, until the practice is proven.

It cannot see or fill a login that is not in your vault. If the account Muse needs is not saved in 1Password, there is nothing to approve, and the task stops at the login page. That is the system working, not failing. Add the login to your vault first, then ask again.

It cannot work with every agent, or on every account type. Muse and the Grok Bot are rolling out first, over the coming days. Claude Duet, ChatGPT Work, and other agents are listed as coming soon. Accounts on 1Password.eu and 1Password.ca are not supported at launch. If your setup falls outside the rollout, the waitlist is the honest answer, not a workaround.

It cannot replace your judgment. You see which login Muse wants and why, and you approve or deny it on your own device. That decision is yours, every time, and it is the safety model. If a request does not match the task you asked for, deny it. An approval you did not think about is not an approval at all.

6. What to watch for

Never paste a password into a chat. This is the habit the whole product exists to kill. If a task needs a login, let 1Password fill it after your approval, or log in yourself. A password pasted into a chat window sits outside your control, in a place you cannot delete with confidence. The new flow exists so you never have to do that again.

Approve per task, not forever. When Muse asks for a login, check that the request matches the task you asked for, then approve that one login. Deny anything you did not ask for. The moment you start approving without reading is the moment the connector stops being an assistant and starts being a risk.

Use the narrowest account that works. Pick an account with no saved card, or a low limit card, for the first tasks. Keep two step verification on, and let 1Password fill the code instead of switching it off. Keep email and banking out for now. That checklist, narrow account, second step on, email and banking excluded, is the safest way to start.

Check the account afterwards. After the first few agent logins, open each account yourself and look at orders, sent messages, and connected apps. A quick check tells you whether Muse did what you asked and nothing more. If anything looks off, disconnect 1Password from Muse and review what happened before you connect again.

Finally, remember the rollout is still landing. 1Password for Agents launched October 22, 2026, Muse is rolling out first over the coming days, and a waitlist applies. If you cannot find the connection yet, that is the rollout, not a fault in your setup. Check your plan, check your region, and check back. And Muse itself is available in the United States, Canada, and Japan only. Outside those three countries, the waitlist is the way in.

Get started

Frequently asked questions

Is 1Password for Agents live for everyone?

No. It launched October 22, 2026, with Muse rolling out first over the coming days, and a waitlist applies. If you cannot find the connection yet, your wave has not arrived, and that is expected.

Does Muse see my passwords?

No. When Muse needs a login, you approve the request on your own device, and 1Password types the login into the form itself. Muse never receives the password, and the credential is removed once the site accepts the login.

What does 1Password for Agents cost?

It is included at no extra cost in 1Password Individual and Family plans held on 1Password.com. Accounts on 1Password.eu and 1Password.ca are not supported at launch.

Can I use it with an account on 1Password.eu or 1Password.ca?

Not at launch. Only accounts held on 1Password.com are supported, so check which region your account sits in before you join the waitlist.

Can Muse log in to my bank with 1Password?

Technically it could, if you approve the login, because an agent can do what an account allows once it is signed in. Keep email and banking out for now, use the narrowest account you can, and check the account afterwards.

How do I disconnect 1Password from Muse?

Connecting is optional, and you can disconnect whenever you wish. 1Password still works as before without connecting any agent, and disconnecting returns you to exactly where you started.

Built with Muse is an independent community project. Not affiliated with or endorsed by Meta.