
Official updates for developers building with @1Password. Securely manage API keys, credentials, and agent access without exposing your secrets.
Joined April 2026
- Tweets630
- Following218
- Followers1.1K
- Likes597
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.
1Password Developers retweeted
Every day now seemingly brings another breach, and the postmortem almost always ends the same way. A credential was compromised, and it could reach far more than it should have.
We spend enormous energy trying to prevent the breach. Prevention matters, but I think we ask the wrong question afterward. The question is not only how did they get in. It is why did one stolen credential open so much.
Breaches are inevitable. Blast radius is a choice.
Every standing credential in your environment is pre-authorized damage. The API key on a hard drive that never expires. The token sitting in a config file. The agent running with persistent access to systems it touches once a month. When one of them leaks, and one of them will, the damage was decided by choices made months earlier.
So what can we do? Secure exposed credentials. Give every identity, human or agent, only the access it needs, only for as long as it needs it. Know where every credential lives, who owns it, and how to revoke it.
Agents make this urgent. Handing an agent your credentials is not automation. It is delegation without accountability.
You cannot shrink a blast radius you cannot see. Start by looking. How much standing access do you have? Most teams I speak with cannot answer that today. That gap is the risk.
Breaches are inevitable. What happens next is up to us.
1Password Developers retweeted
What can October’s security incidents teach us about securing AI agents?
Leaked credentials, exposed API keys, and compromised infrastructure highlight risks developers need to account for.
Five lessons to apply to your own workflows and discuss with your team. 🧵
RT @LTM_yvr: Engineers should not be handing their over-privileged (standing) access to their agents. Allowing engineers to work with agent…
This quoted post is unavailable.
1Password Developers retweeted
Agents need access, not secrets 🤝
Builders came from across the Universe to Barrio in Ghirardelli Square for @1Password Agents After Dark with @databricks .
📷 Great views, great people and great conversations!
#GitHubUniverse #AgentsAfterDark















