opencode-vercel

Browse Vercel deployments without leaving the OpenCode v2 TUI.

opencode-vercel adds a /deployments command that discovers locally linked Vercel projects and Vercel projects connected to the current GitHub repository, lets you select an app in a monorepo, and opens a searchable deployment list. Deployment data, details, and build logs come from the authenticated Vercel CLI.

Projects and deployments are refreshed in the background every minute. While a deployment list is open, it refreshes every five seconds and inserts new deployments without replacing the dialog. Build logs for each project's newest three deployments are also prefetched, so the deployments people inspect most often open immediately.

OpenCode v2 and its TUI plugin API are beta. This release targets OpenCode 0.0.0-next-16741 exactly.

Requirements

• OpenCode 0.0.0-next-16741, available as opencode2
• Node.js 22.12 or newer
• Vercel CLI authenticated with access to the linked projects
• A GitHub origin remote or at least one local .vercel/project.json created by vercel link

Verify Vercel CLI access with:

vercel whoami

For a single app, link its directory with:

vercel link

For a repository containing multiple Vercel projects, run this from the repository root:

vercel link --repo

Install

Add the package to ~/.config/opencode/cli.json:

{
  "plugins": [
    {
      "package": "opencode-vercel"
    }
  ]
}

Restart OpenCode after adding or updating a package plugin.

Use

Start OpenCode in a repository containing one or more linked Vercel projects and run:

/deployments

If the repository contains multiple linked projects, select one first. The plugin then loads the latest 100 deployments for that project.

Press Enter to inspect a deployment, l to view its build logs, or o to open its deployment page in the Vercel dashboard. Press / from a searchable list to return focus to its search field. Escape and Backspace return to the previous view.

The plugin combines local Vercel links with projects from your accessible Vercel teams whose Git integration exactly matches the current GitHub origin repository. Project names are never used to guess repository membership.

Develop

Install dependencies and create the initial build:

npm install
npm run build

Run the compiler in watch mode:

npm run dev

Register the absolute local build path in ~/.config/opencode/cli.json:

{
  "plugins": [
    {
      "package": "/absolute/path/to/opencode-vercel/dist/tui.js"
    }
  ]
}

Restart OpenCode after adding the plugin. Local source rebuilds are hot-reloaded, but dependency and package configuration changes require a restart.

To test interactively, open a linked Vercel repository and run /deployments. Verify project selection in a monorepo, deployment searching, Up/Down navigation, Enter for details, l for logs, o for browser opening, / to return to search, and Escape/back behavior in every view.

Verify

npm run check
npm pack --dry-run

For OpenCode diagnostics:

OPENCODE_LOG_LEVEL=DEBUG opencode2

Installed OpenCode logs are written to ~/.local/share/opencode/log/opencode.log.

Releases

Every non-bot push to main creates the next patch release, publishes it to npm, tags the release, and creates a GitHub Release. Publishing uses npm trusted publishing with GitHub Actions OIDC, so no npm token is stored in GitHub.

Include [skip release] in a commit message when a push should not create a release.

Configure the opencode-vercel package's trusted publisher in npm before relying on the workflow: select GitHub Actions, enter organization vestia-dev, repository opencode-vercel, workflow filename release.yml, and allow npm publish.

The workflow updates both package.json and package-lock.json in its release commit. Its bot-authored push is excluded from triggering another release.

License

MIT