Vercel OAuth
VauCode starts a Vercel OAuth authorization flow and handles the callback through a local loopback HTTP listener.
Deployment integration
▲Available now
Vercel
Connect a Vercel account from VauCode, discover projects across the personal account and teams, and reuse the stored Vercel token for VauCode deployment workflows.
Inside VauCode
This page documents the integration currently present in the VauCode Android/Flutter source, not a generic roadmap description.
Personal projects
The integration loads projects available directly under the connected Vercel account.
Team discovery
VauCode also loads Vercel teams and requests projects for each accessible team scope.
Framework metadata
Project cards can display the framework returned by Vercel together with team context.
Stored deploy token
The resulting access token is saved through the native VauCode bridge for later Vercel operations.
Native deploy path
The Android source includes a Vercel CLI deployment path using npx vercel deploy with the connected token.
Connection flow
How it works in the app
- 1
Open Integrations → Vercel and confirm the connection.
- 2
Authorize the Vercel account through OAuth.
- 3
VauCode receives the callback, loads personal projects and discovers accessible teams.
- 4
Browse Vercel projects together with team/framework information.
- 5
The native VauCode runtime can use the saved token as the foundation for Vercel deployment operations.
Implementation notes
What the source currently does
Project discovery calls the Vercel v9 projects API for both personal and team scopes.
Team discovery calls the Vercel v2 teams API and merges project results by project ID.
The access token is stored through the native saveVercelToken MethodChannel action.
Android deployment plumbing invokes npx --yes vercel deploy --token … --yes in the selected workspace path.
Current source note
The current VauCode home-screen source still marks its Vercel deploy action as temporarily unavailable/gated. OAuth, token storage and project discovery are active; the native deploy plumbing exists, but the website should not present the current UI as a fully exposed one-tap deployment flow yet.
Explore more