PR Custody

docs: mark connected_account_id as required for proxy execute

@decimal-pr-bot[bot]checks n/achecks…decimal/docs-mark-connected-account-id-as-required-for-proxy-execute-668b → next1 files · +1 −1review: @Sushmithamalleshupdated 1mo ago

GitHub

▸Description· 1 comment · 1 noise

Summary of Changes

Updated docs/content/docs/proxy-execute.mdx Parameters table: changed connected_account_id from "No" (optional) to "Yes" (required) and removed the incorrect "Defaults to the most recent active account for the project" description

Reasoning

Users calling the proxy execute endpoint without connected_account_id receive a 400 error (code 2811, ExternalProxy_MissingAuthContext) but the docs say the parameter is optional with a default fallback
The parameter requirement changed as part of intentional security hardening; docs need to reflect the current behavior

@claude[bot]agent1mo ago

Claude finished @decimal-pr-bot[bot]'s task in 50s —— View job

Review Progress

Read docs-reviewer guidelines
Run git diff to see changes
Apply review checklist to changed files
Post review feedback

Review

Looks good. This is a one-line factual correction in docs/content/docs/proxy-execute.mdx:168 — flipping connected_account_id / connectedAccountId from optional to required and dropping the inaccurate "defaults to the most recent active account" sentence.

The change matches the actual API behavior described in the PR (missing param returns 400 / ExternalProxy_MissingAuthContext) and is consistent with the rest of the page — every code example on this page already passes the parameter, so marking it required aligns the table with the examples developers will copy. No missing-step, outdated-pattern, or CI-gap issues. Nothing else needs updating. | Branch

▸ 1 bot/status comment hidden

@vercel[bot]1mo ago

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	May 8, 2026 7:27pm

loading diff…