Jason Meller

@jmeller.bsky.social

Founder of Kolide.com VP, Product at 1Password Author of honest.security CT, USA I write about entrepreneurship, Ruby, IT, and cyber security.

We sweat the details on this, and I couldn’t be prouder. Yesterday I asked Claude Cowork to: 1. Book my annual physical 2. Suggest audiobooks from my kids’ Yoto history 3. Add games to my @playdate wishlist 4. Submit my recent trip expenses Happy to do Q&A! 1password.com/blog/1passwo...

1Password for Claude: Give Claude access without giving up your credentials | 1Password

Give Claude access, without giving up control of your secrets. 1Password now enables AI agents to complete tasks requiring credentialed access, while keeping your credentials encrypted, secure, and in...

1password.com

I was inspired by @s.ly 's recent piece on Latent Space Engineering. I wanted to see if his observations also applied to the security domain. What started as small experiment turned into a full blown agentic AI benchmark that I'm releasing as OSS at 1Password. 1password.github.io/SCAM/

SCAM — How safe is your AI agent?

An open-source benchmark by 1Password that tests whether AI agents can handle real security threats during everyday tasks. View the leaderboard, watch replays, and try the security skill.

1password.github.io

Arko in this post says he’s in control of a second 1Password account. One thing he should do is check if he’s the only owner. If he is, no one can evict him and regain the account. IMO he should have disclosed this access to them in his original email, esp if it’s how he got AWS root access.

André Arko@indirect.io · last yr.

Ruby Central said some really concerning things today. I don’t think they’re representing the situation accurately. andre.arko.net/2025/10/09/t...

3 things I found are always true when making SaaS. 1. To know what you need to build, you must first build it. 2. A fast and cost-effective way to find and fix bad bugs is to ship them to production. 3. If you're nervous about deploying to production, the solution is to deploy more frequently.

We’ve got more “small teams” than ever before. They’re all mostly B2B SaaS. I think B2C is the big upset. How do we explain to people that they should “shop local” when it comes to software. And pay for it!

Third task for the day. Lot's of stuff shipped over the weekend. What I like to do is let individual customers to know via our shared Slack channels when something they cared about ships. This is one of those things that won't scale for long, but we do it anyway because it's the right thing to do.

Second Problem. Customer bug report. Kolide offers Slack based support (which btw is the best decision we've ever made) & while normally it's quiet, we have a customer who is hitting a problem with mobile registration. This is bad because I _just_ changed this code last night. What did I break?

Bild