Vercel Deploy Status Claude Code mod: the build queue above the prompt

Vercel Deploy Status is a community mod by Ray Amjad (ray-amjad), published in his claude-code-mods repository. It pins the Vercel deploy queue of the linked project in the band above the Claude Code prompt. Every deploy that is queued, building or just finished gets one line with its phase, target (Production or Preview), branch, elapsed time and commit subject.

The header shows the project name and the counts that are not zero, for example ▲ my-site · 1 building · 1 queued. In-flight deploys are yellow, Ready is green, Error and Canceled are red. A toast appears when a deploy starts and when it finishes. A finished deploy stays on the board for 5 minutes. When the queue is empty and nothing is waiting, nothing is drawn.

The mod never starts a turn and never writes to the transcript. It only draws what the vercel CLI reports.

The install block above adds the author's marketplace and installs the plugin from it. You also need the vercel CLI on your PATH, logged in, and a repo linked with vercel link, which writes .vercel/project.json. After installing from the shell into an open session, run /reload-plugins.

The plugin is one function-hooks module, hooks/deploy-status.tsx, plus hooks/queue.ts, which holds the pure logic (types, the push-detection regex, formatters and the merge of one poll into the next queue). session.start finds the link file, reads the project name and starts a poll loop that runs vercel ls in the linked directory. A tool.call hook on Bash wakes the loop after a push or deploy command finishes. This is from deploy-status.tsx:

on('tool.call', { tool: 'Bash' }, async ($, e, next) => {
  const command = typeof e.command === 'string' ? e.command : ''
  if (!isDeployCommand(command)) return next(e)

  // Let the push finish first: Vercel has nothing to report until it lands.
  const result = await next(e)
  await wake?.()
  return result
})

The poll command itself is [vercelBin, 'ls', '--format', 'json', '--non-interactive'] with a 25 second timeout. A deploy that was in flight and then falls off the newest-deploys list is shown as Ready; the README lists this as a known limit.

The plugin declares six user options: vercelBin (default vercel), activePollSeconds (15), idlePollSeconds (60), holdFinishedMinutes (5), watchAfterPushMinutes (6) and maxRows (8). The README says options are read from your user settings only, under pluginConfigs with the key vercel-deploy-status@claude-code-mods. A pluginConfigs block in a project's .claude/settings.json is not read. Set vercelBin to a full path if Claude Code's PATH differs from your shell's.

We read every file the plugin loads: plugin.json, hooks/hooks.json, hooks/deploy-status.tsx, hooks/queue.ts, the README and the test files. queue.ts imports nothing. There is no package.json, no binary, no minified code and no bundled dependencies. Findings:

• Runs commands ($.process.run): only the configured Vercel executable, as an argv array with no shell: vercel ls --format json --non-interactive, run from the linked directory. Because vercelBin is a setting, whatever you put there is what runs.
• Network: none in the plugin code. The vercel CLI contacts Vercel using your login.
• Reads files: .vercel/project.json (for the project name) and directory listings to find it, at most a few levels below the repo root, skipping node_modules and dot folders. Nothing is read from outside the repo.
• Writes files: none. It does not touch ~/.claude, settings, shell files or LaunchAgents, and starts no daemon; the timers end with the session.
• Watches Bash calls: the tool.call hook reads the command string to match git push, gh pr merge or vercel deploy. It never edits or blocks the call, and it waits for the command to finish before polling. claude plugin validate notes that this hook has no .catch.
• Secrets, environment, telemetry: no environment variables are read and nothing is sent anywhere by the plugin. No injected prompt text or hidden Unicode was found.
• Licence: MIT, with a LICENSE file in the repo (copyright Ray Amjad).

claude plugin validate reported no errors and no warnings on the manifest or hooks. Its directory check flagged one non-blocking item: the plugin has no icon. claude plugin test passed 3 of 3 tests on Claude Code 2.1.307 (the band draws other mods' bands under it, a headless session starts no poll loop, an interactive one does). We did not run a real Vercel deployment, so the live queue output is as described by the author and the code, not recorded by us.

Tested with Claude Code 2.1.307 on macOS. The mod needs function hooks and does nothing in -p or SDK sessions. If nothing shows up:

• Check that the repo has .vercel/project.json. Without it the mod logs no .vercel/project.json in this repo, staying quiet.
• Run vercel whoami in the same shell to confirm the CLI is logged in, and set vercelBin if Claude Code cannot find it.
• Start Claude Code with --debug-file load.log and look for hooks module vercel-deploy-status loaded.
• A push made in another terminal is only picked up by the next idle poll, up to 60 seconds later.
• To try it without installing, run claude --plugin-dir /path/to/plugins/vercel-deploy-status from a linked repo.