Triggercmd
Use Triggercmd with AI apps and agents through Vercel Connect. Follow a complete setup guide for secure runtime access.
Install the skill
$ npx skills add vercel/vercel-plugin --skill vercel-connectConnect to
Use its data in agents(opens in new tab) and apps(opens in new tab)
import { getToken } from '@vercel/connect';const userId = 'user_123';const token = await getToken('triggercmd/acme-triggercmd', {subject: { type: 'user', id: userId },});
Use Triggercmd in apps and agents
Run commands remotely on your computers.
Why use Vercel Connect with Triggercmd?
Credentials on demand
Request Triggercmd credentials only when your application or agent needs them instead of copying secrets into application code.
Access for the right subject
Support both user-authorized and app-scoped Triggercmd access from the same connection layer.
Centralized credential management
Manage Triggercmd credentials in one place and retrieve them through a consistent runtime API.
Vercel-native controls
Bind connections to the projects and environments that need them while Vercel OIDC authenticates each runtime request.
Use Triggercmd with your stack
Follow a complete setup for the Connect SDK or a supported agent framework.
Add Triggercmd to an existing Vercel application with the Connect SDK.
Install the Connect SDK
npm install @vercel/connectCreate the Triggercmd connector
Run these commands from the project that will use the connection.
vercel linkvercel connect create triggercmd --name acme-triggercmdvercel env pullRequest Triggercmd credentials
app/api/route.tsimport { getToken } from '@vercel/connect';const userId = 'user_123';const token = await getToken('triggercmd/acme-triggercmd', {subject: { type: 'user', id: userId },});
