For those of you using Vercel hosting and have bots validate their SE work in a branch (using Vercel preview link), how are you handling authentication?
There is a bug with 1Password currently where the preview link is not recognized by 1P, therefore even if you have the credentials saved, it won’t autofill or recognize the credentials being associated with the app.
Therefore, even when using the 1P plugin with Grok Bot (in shared with Grok Bot vault), the bot can’t use the shared credentials.
I would think this is a very common issue for others given:
Many are using GB for software engineering E2E
Vercel hosting is common
Vercel preview links are used by branches which bots use during development and self validation
Many devs already use 1P
Having to manually auth the bot for every task is slowing me down tremendously and kind of defeats the point of agentic development.
How is everyone else solving for credential sharing for SE workflows?
What you’re seeing is expected right now, and it isn’t only on the 1Password side. Grok Bot only fills a 1Password login on a site that matches the item’s saved website, and it follows the same rule 1Password does: every *.vercel.app address counts as its own separate site. So a login saved for your production domain (or for myapp.vercel.app) won’t be offered on myapp-git-my-branch-team.vercel.app, even when the item is in the Shared with Grok Bot vault.
Two setups that work today:
Serve previews from a domain you own. Vercel’s Preview Deployment Suffix setting (Pro and Enterprise plans) makes preview URLs end in your own domain, for example *.preview.yourdomain.com. Add https://yourdomain.com as a website on the 1Password item and keep its autofill setting on “Fill anywhere on this website” (not “Only fill on this exact host”). Every preview then matches that one login, so the bot can sign in on its own.
Give the bot a test account as secrets. Ask your bot to “save my staging test login as secrets”. It shows a masked form, the values are stored on its computer as environment variables (the bot never sees them), they persist across tasks, and it can sign in from a Playwright (or similar) script that reads them. Best with a dedicated non-production user.
Thanks @Colin , your second suggestion has worked great!
The 1Password issue with Vercel preview URLs was killing me. I am aware of Vercel’s Preview Deployment Suffix and it would be great to have, but $100/mo is just too steep.
I hope this thread helps others resolve this issue for themselves. I appreciate your reply!