{
  "schema_version": "1.1",
  "id": "s4:https://vercel.com/changelog/project-scoped-tokens",
  "slug": "project-scoped-tokens-1emgc6h",
  "url": "https://feed7.dev/p/project-scoped-tokens-1emgc6h",
  "title": "Project-scoped Tokens",
  "why_included": "Vercel tokens can now be restricted to one project, giving agent jobs and automation read/write access without exposing unrelated project, team, or user resources.",
  "summary": "Vercel now supports **project-scoped access tokens** for its API. A token can read and write resources only within its selected project; requests targeting other projects or user- and team-level resources are denied.",
  "practical_implication": "Use these tokens for coding agents, CI jobs, and deployment tools that operate on a single project. This narrows the impact of a leaked or misused credential compared with broader account credentials.",
  "agent_context": "Vercel now supports **project-scoped access tokens** for its API. A token can read and write resources only within its selected project; requests targeting other projects or user- and team-level resources are denied.\n\nUse these tokens for coding agents, CI jobs, and deployment tools that operate on a single project. This narrows the impact of a leaked or misused credential compared with broader account credentials.\n\nYou must choose the owning team, project, and **expiration** when creating the token. The resulting secret **is shown only once**, so its storage and rotation still need deliberate handling.",
  "source": {
    "name": "Vercel",
    "url": "https://vercel.com/changelog/project-scoped-tokens",
    "published_at": "2026-07-30T00:00:00.000Z"
  },
  "source_class": "blog_post",
  "content_type": "Engineering Post",
  "layer": "infra",
  "domains": [
    "coding",
    "security"
  ],
  "topics": [
    "sandboxing",
    "tool-use"
  ],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "You must choose the owning team, project, and **expiration** when creating the token. The resulting secret **is shown only once**, so its storage and rotation still need deliberate handling."
  ],
  "connected_context": {
    "meaning": "This adds a credential boundary alongside the prior runtime and sandbox boundaries: single-project agents, CI, and deployers no longer need team-wide authority. It reduces cross-project exposure but does not solve secret lifecycle management, because ownership, expiry, one-time capture, storage, and rotation remain explicit operational responsibilities.",
    "corpus_size": 297,
    "generated_at": "2026-07-31T10:06:09.027Z",
    "connections": [
      {
        "title": "Vercel MCP can now deploy code",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/vercel-mcp-can-now-deploy-code",
        "feed7_url": "https://feed7.dev/p/vercel-mcp-can-now-deploy-code-1292qsq",
        "reason": "Project-scoped tokens directly limit the authority of MCP deployment workflows to the project they are meant to mutate."
      },
      {
        "title": "Run multiple isolated agents in a single Sandbox",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/run-multiple-isolated-agents-in-a-single-sandbox",
        "feed7_url": "https://feed7.dev/p/run-multiple-isolated-agents-in-a-single-sandbox-03i3r7u",
        "reason": "Linux-user isolation separates agents inside a sandbox, while project-scoped tokens independently restrict what each workload can reach through Vercel’s API."
      },
      {
        "title": "Gemini API Managed Agents: 3.6 Flash, hooks, and more",
        "source_name": "Google",
        "source_url": "https://blog.google/innovation-and-ai/technology/developers-tools/expanding-managed-agents-gemini-api-3-6-flash-hooks/",
        "feed7_url": "https://feed7.dev/p/expanding-managed-agents-gemini-api-3-6-flash-hooks-0xce1pm",
        "reason": "Hooks and token caps govern unattended execution, whereas scoped credentials bound the external resources such execution can access; both controls are needed at different boundaries."
      },
      {
        "title": "Vercel Sandbox now supports FUSE-based filesystems",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/vercel-sandbox-now-supports-fuse-based-filesystems",
        "feed7_url": "https://feed7.dev/p/vercel-sandbox-now-supports-fuse-based-filesystems-1be2jtc",
        "reason": "Mounting remote data expands a sandbox’s reachable resources, reinforcing the need to keep API credentials narrowly scoped even when filesystem access is separately controlled."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-07-30T00:00:00.000Z",
  "modified_at": "2026-07-30T00:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/project-scoped-tokens-1emgc6h",
    "json": "https://feed7.dev/p/project-scoped-tokens-1emgc6h.json",
    "markdown": "https://feed7.dev/p/project-scoped-tokens-1emgc6h.md"
  }
}