Otpilot

When I first shipped OTPilot, the setup required you to paste in your base32 TOTP secret manually. That’s fine if you’re a developer, but it’s a dealbreaker for everyone else. So I went back and rethought the onboarding from scratch — and the result changes what OTPilot actually is. The big new thing: automatic account detection When you enable 2FA on any site, that site generates a secret and usually shows you a QR code. Hidden in that QR code is a standard URI that looks like otpauth://totp/GitHub?secret=.... OTPilot now scans the page for that URI automatically — no QR scanning, no copy-pasting — and shows a floating card: “Save GitHub to OTPilot?” One click, done. ...

If you work in dev or QA, you probably know the pain: you’re in the middle of a flow, you hit a 2FA screen, you grab your phone, open the authenticator app, squint at the 6-digit code that’s about to expire, type it in, and then repeat the whole thing 10 times a day. I got tired of it, so I built OTPilot. What it does OTPilot is a Chrome extension that auto-fills TOTP codes (the kind Google Authenticator generates) directly into the login page, eliminating the need for a phone. You configure which URLs it should watch, and it handles the rest: detects the field, fills the code, submits the form. ...