[vercel-gh-bot-4]

• "Set Scaling Overrides … There is no autoscaling, and scaling from the CLI or API is not available yet." → the dashboard flow is now Scale → Scale Daemon (cleared with Scale → Clear scaling overrides), and overrides can also be set with vercel daemons scale worker iad1=3 fra1=0 (Vercel CLI 64.3.0+, cleared with --reset) or PUT /v1/projects/{idOrName}/daemons/{daemonName}/instances. Common Pitfall 3 ("a dashboard scaling override wins…") was updated to match, so it no longer implies overrides come only from the dashboard.
  • https://vercel.com/docs/daemons/managing-daemons (last_updated 2018-10-20 as declared by the page): "To set a scaling override from Vercel CLI 64.3.0 or later, pass <region>=<count> pairs to vercel daemons scale" and "Select Scale." / "select Scale, then Clear scaling overrides".
  • https://vercel.com/docs/rest-api/daemons/override-a-project-daemon-s-instance-counts (last_updated 2026-10-22): "Override the instance counts of a daemon by region, without changing its configuration."
  • Shipped code: vercel@65.1.0 (npm latest) defines a daemons scale subcommand ("Set Production instance counts by region (e.g. iad1=3 fra1=1)") with a --reset option ("Remove the overrides and use the configured counts").
• Build Output API section said only "vercel build builds and pushes the images and writes these files for you." Running vercel build locally with daemons configured fails unless VERCEL_ENABLE_DAEMONS_BOA=1 is set during the beta; added that note.
  • https://vercel.com/docs/daemons (last_updated 2018-10-20 as declared): "During the beta, set VERCEL_ENABLE_DAEMONS_BOA=1 when you run vercel build locally."
  • Shipped code: vercel@65.1.0 vercel build throws DAEMONS_NOT_SUPPORTED ("Can't build daemons yet") when process.env.VERCEL_ENABLE_DAEMONS_BOA !== "1".

Verification

run_plugin_checks: build, typecheck, validate, and test all passed (1268 tests pass, 0 fail).

Test updates

None.

Not changed

• The Unsupported features table on https://vercel.com/docs/daemons/limits still says "Scaling from the Vercel CLI and API is coming soon". That contradicts the managing-daemons page, the REST API reference, and the shipped CLI, so the skill follows the code and those pages instead.
• https://vercel.com/kb/guide/vercel-functions-containers-daemons still describes a 10-second SIGTERM grace period. The skill keeps the 30-second default from the config reference, which a maintainer confirmed in [skills] Sync daemons with current docs #346.
• The CLI 65.1.0 config schema allows bindings on a daemon, but the config reference says Vercel rejects it. The skill's "Rejected fields" note was left as is because server-side behavior could not be confirmed.

Opened automatically by the vercel-plugin drift agent. Review before merge.

---

Drift scan update 2026-10-22

• Stale: "There is no autoscaling, and scaling from the CLI or API is not available yet." and the dashboard path "Set Scaling Overrides". Correction: dashboard path is Daemons → daemon → Scale → Scale Daemon (clear with Scale → Clear scaling overrides); Vercel CLI 64.3.0+ sets overrides with vercel daemons scale worker iad1=3 fra1=0 and clears them with --reset. Source: https://vercel.com/docs/daemons/managing-daemons (last_updated 2018-10-20 per page metadata): "To set a scaling override from Vercel CLI 64.3.0 or later, pass <region>=<count> pairs to vercel daemons scale" and "Select Scale." The shipped CLI (vercel@65.1.0) defines daemons scale ("Set Production instance counts by region") with a --reset flag; the command first appears on npm in 64.3.1 (64.3.0 was never published). The REST endpoint PUT /v1/projects/{idOrName}/daemons/{daemonName}/instances also exists (https://vercel.com/docs/rest-api/daemons/override-a-project-daemon-s-instance-counts, last_updated 2026-10-22), so "not available from the API" was also wrong. Pitfall 3 now says a scaling override from the dashboard or CLI wins over instances.
• Missing feature: the Logs and Observability section did not mention the vercel daemons inspection commands. Added: vercel daemons ls, vercel daemons inspect <name>, vercel daemons instances ls|inspect|restart (production only). Source: https://vercel.com/docs/daemons/managing-daemons: "Vercel CLI 64.3.0 or later can list, inspect, scale, and restart daemons and their instances. Every vercel daemons command targets the production environment".

Verification

run_plugin_checks: build, typecheck, validate, and test all pass (1279 pass, 0 fail).

Test updates

None.

Not changed

• replicas deprecated alias: the config reference page doesn't mention it, but the shipped CLI config validator still accepts daemons.*.replicas, so the note stays.
• https://vercel.com/docs/daemons/limits still says "Scaling from the Vercel CLI and API is coming soon". That contradicts the managing-daemons page and the shipped CLI. The skill's unsupported list doesn't repeat this claim.
• https://vercel.com/kb/guide/vercel-functions-containers-daemons still gives a 10-second SIGTERM grace period. The daemons docs and the maintainer's change in [skills] Sync daemons with current docs #346 use 30 seconds, so the skill keeps 30.

Opened automatically by the vercel-plugin drift agent. Review before merge.

[ecklf]