Support for Vercel preview links

Hi there, just wanted to check in and see if there is any update on the feature request.

Hello @cjkochis, I don't have any news to share about the feature request. I appreciate that this feature is useful for this case, and I'll be happy to advocate on your behalf to the team.

Let me know if you have any further questions.

-Evon

@1P_Evon - I'd like to +1 on this feature request.

Although nzCharlie's solution would work, its additional cost for us that isn't acceptable right now.

We've also recently moved over from LastPass which had the wildcard feature that helped with this, so the dev team is busting my chops a bit on the change.

Any advice or alternate solutions would be amazing, we're in the exact same postion as @cjkochis (and many others historically looking through previous posts).

@HulerDan, thank you for your reply. I've shared your feedback with our product team.

I'm sorry, I don't have an alternate solution other than to save the "example.vercel.app" website URL to the Vercel Login item. I realize this may not be ideal, and I apologize for any interruption in your workflow caused by this issue.

I hope that helps.

-Evon

ref: PB-38963154

This has become a HUGE problem and need fixed. Now that Agents are logging into sites for us, especially in engineering workflows, this becomes a blocker to a primary use case. 1Password even built plugins to allow AI agents to use 1Password credentials, however, with this bug, that plugin is useless.

Scenario: I use Grok Bot as an agent in my software engineering, with Vercel as the host. Bots validate their own work using the Vercel preview links. Even though I’ve shared the login with Grok Bot, via the 1Password plugin, they are unable to utilize that shared credential. This 1Password + Vercel preview link bug, prevents the use of the shared credential on a preview URL. Therefore, the bot is not able to use the shared credential.

Impact: Without this, I have authenticate manually for the bot, every time. With the shift towards agentic coding, this becomes a massive blocker in the workflow.