
Official updates for developers building with @1Password. Securely manage API keys, credentials, and agent access without exposing your secrets.
Joined April 2026
- Tweets653
- Following220
- Followers1.2K
- Likes632
1Password Developers retweeted
We’re starting to test 1password in dots!
Our goal is to make it easy for your dot to do tasks that require a login, while keeping your credentials secure. Excited to roll this out more broadly soon.
Let us know what you think.
Replying to @FredrikAurdal @marckohlbrugge
1Password Environments + their MCP server is the strongest practical option right now.
Create a project-scoped Environment, connect the agent via MCP. The agent can list names, create mounts, and manage config, but the server never returns secret values. Secrets inject only into the runtime process (in-memory mount or op run).
Pair it with the agent’s deny rules so it cannot Read(.env*). Prefer short-lived tokens. This keeps the vault out of the agent’s context entirely.
1Password Developers retweeted
Replying to @marckohlbrugge
new 1pass vault where i duplicate only credentials i want the agent to have access to
that is what works for me 🤷♂️
1Password Developers retweeted
Replying to @marckohlbrugge
1password and create an exclusive vault for the agent
1Password Developers retweeted
Classic attacks now have AI-agent versions:
Phishing → goal hijacking
Supply chain → tool poisoning
Credential theft → secrets in context
Persistence → memory poisoning
Attackers want the same things. The route is new.
Here are 7 to know & how to build your defense:
🧵(1/10)
1Password Developers retweeted
Five places to start:
1. Treat external content as untrusted
2. Give agents the minimum permissions they need
3. Keep credentials out of model context
4. Audit agent tools and dependencies
5. Monitor actions, not only prompts
🧵(9/10)
1Password Developers retweeted
We'll all have to disconnect from the Internet, thanks to AI. Great job, AI developers. 😡
1Password Developers retweeted
The FBI just issued a warning about AI agents being used to hack companies.
Some attacks reached privileged access in under 3 HOURS.
67,000 people's data exposed. 2,250+ downstream tenants affected in a separate campaign.
The tool behind it? ARTEX.
Here's how the attacks work. 🧵
1Password Developers retweeted
Introducing: @browser_use x @1Password
Your agent can log in anywhere without ever seeing your password.
> connect 1Password once
> agent hits a login page
> you approve it in 1Password
> 1Password fills it in, agent keeps going
Try it 🔗⬇️
1Password Developers retweeted
Allie and KC with some great stuff here
New episode of Random but Memorable is live 🎙️
KC Li, senior director of product management, joins to talk about 1Password for Agents: how agents sign in for you without ever seeing your passwords.
Watch now:
youtube.com/watch?v=o9UDSh4t…
1Password Developers retweeted
Loved hosting a developer happy hour with @1PasswordDev on the last day of web summit!
1Password Developers retweeted
The internet has a second audience: AI agents. 🤖
@Cloudflare just shared some fascinating data about how the web is changing.
Here are 3 things that caught our attention 🧵👇
1Password Developers retweeted
Most security incidents don’t start with sophisticated hacks. They start with credentials that have too much access.
Here are 5 practical steps every developer can take to secure their apps, tools, and AI agents. �
1Password Developers retweeted
Your AI co-pilot runs with your credentials: same prod access, same push rights, and no separate identity.
Here’s why that’s a real risk, and how to scope agent access without slowing your team down. 🧵 1/5
1Password Developers retweeted
Grateful for the opportunity to speak with our friends at @lightspeedvp about our journey at @1Password .
1Password’s push into AI met resistance inside the company.
David Faugno (@1PasswordCEO), CEO of @1Password, joined Lightspeed Partner @guruchahal on Cyber60 to discuss the company’s AI strategy.
He said some employees were skeptical when leadership committed to AI two years ago.
David helped connect the strategy to their existing mission: helping customers use emerging technologies safely.
That early work mattered when personal agents began gaining traction. Customers were reluctant to hand over their credentials.
1Password had already been building infrastructure to help agents access accounts while protecting those credentials.
As David puts it, “People want a trust layer” before letting agents act on their behalf.
Check out the full interview down below!
0:00 Welcome to Cyber60
1:29 Why 1Password Shifted to Enterprise
4:22 Scaling From Individual Users to Enterprise
7:37 How AI Is Transforming 1Password
11:28 Balancing Growth and Profitability
15:20 The Funnel Metrics in Cybersecurity
17:41 Building an Executive Team
20:39 Rapid-Fire Questions
1Password Developers retweeted
So proud of the @1Password team. Congrats on the shoutout from @benthompson on Sharp Tech! It’s incredible to see a vision we believed in come to life: AI agents can do useful work without being handed the keys to everything.
1Password Developers retweeted
More than 40% of pull requests on @github now start with an AI agent. 🤯
Just six months ago, it was 17%.
We’re watching software development change in real time.
But the interesting part isn’t just who’s writing the code. 🧵👇
1Password Developers retweeted
Replying to @DawsonBotsford
Hey Dawson! @1PasswordDev is our official developer account. Thanks for checking with us! 💙
1Password Developers retweeted
At Web Summit Lisbon? Your agents keep working while you network.
See how 1Password for Agents keeps your credentials secure.
1Password Developers retweeted
Replying to @jasonlk
This is becoming clear. Reduce blast radius. Harden credential security. Find standing access and exposed credentials. Treat agents as privileged actors with scoped, traceable access. Do it now.



















