⌘K
Ashokcchander 8888 Additional read-only diagnostics — October 10, 2026, approximately 4:50 PM Pacific / 23:50 UTC. We reproduced a difference based solely on whether an explicit team selector is supplied. Project: quintascent-picio-pilot-v1 Project ID: prj_HkwvurhrAMytl7Xb74iiDmCLAM4q Team slug: quitascent Team ID: team_IKgnMSNmT2TNQeoQoCmPyZ5b Results: 1. get_project({idOrName: "prj_HkwvurhrAMytl7Xb74iiDmCLAM4q"}) succeeds. Its response contains accountId: "team_IKgnMSNmT2TNQeoQoCmPyZ5b". 2. The identical lookup with teamId: "team_IKgnMSNmT2TNQeoQoCmPyZ5b" returns 403 Forbidden. 3. The identical lookup with slug: "quitascent" also returns 403 Forbidden. 4. list_deployments with the project ID and no explicit team selector succeeds; the latest two deployments report READY. 5. Earlier list_teams returned an empty list, and direct get_team returned 403. Both failed project lookups identify operation GET /v9/projects/{idOrName} and report: “Not authorized: Trying to access resource under scope "quitascent". You must re-authenticate to this scope or use a token with access to this scope.” Request IDs: - Explicit team ID: sfo1:sfo1::kzw9q-1791676217409-b1ae2808143c - Explicit slug: sfo1:sfo1::ltb42-1791676217674-f6e77d7f6a14 Error metadata: saml=false; ssoEnforced=false. The connector additionally labels the failure INVALID_ARGUMENT, while the underlying API error is 403 forbidden. The Vercel account UI shows quitascent as the default team. The ChatGPT application, owned by Vercel MCP, displays permission to read Vercel team data and read/change authorized projects. Could you trace these request IDs and check why implicit/default-team project access succeeds while explicitly selecting the same owning team fails? Is this expected authorization behavior, a missing team-specific grant, or a connector scope-resolution issue? These tests were read-only. No credentials, deployment protections, or project settings were changed.
Ashokcchander 8888 Additional comparison using Vercel Agent’s separate credentials: • Project lookup succeeds with both the owning team ID and slug “quitascent.” • Team listing includes quitascent, and direct team lookup succeeds. • The project’s accountId matches the supplied team ID. • Deployment listing succeeds. ChatGPT MCP still shows the contrasting behavior documented above: project access without an explicit team selector succeeds, but explicit team ID/slug access returns 403, and team listing is empty. Vercel Agent could not inspect ChatGPT’s effective OAuth grant or token context. Please check whether the ChatGPT connection has an effective grant for this specific team and whether explicit team selectors are resolved correctly. The displayed “read team data” permission alone does not settle that question. No settings or resources were changed in either diagnostic.
Amy Egan I took a look in the logs and see some unusual things. Did you downgrade the same day you upgraded to Pro? In that case I believe the system would automatically issue a prorated refund. Asking the support team for help investigating this as I can't see the full details
Amy Egan The team let me know they corrected the issue with your team, but please let me know if you still have any trouble with it
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0
Amy Egan Vercel has not stopped accepting new accounts. However, sometimes a new account will be flagged if there is a policy violation or suspicious activity that requires manual review. Do you have a support case number I can check?
Ikarov Hey @amyegan, just bringing this back to your attention in case you missed it. Thanks!
Amy Egan Appreciate you reaching out. I'd love to see it stay in the hands of the community rather than have Vercel take over. Feel free to ask around here and in Next.js Discussions to find your successor!
Ikarov Thanks, @amyegan ! Just to clarify, I'm also open to discussing a potential acquisition of the @nextjs username itself, alongside the community. Given the long-standing association with Next.js, I thought it might be particularly valuable in the hands of Vercel or the official team. Would this be something worth discussing with the right person?
Amy Egan First, I want to make sure you're getting the help you need. Do you have a support ticket yet? If not, you can open one at vercel.com/help Appreciate you sharing feedback about your experience. It sounds like there's still some room for improvement here, but I just want to clarify a couple of things to help it make more sense > These emails were receipts issued after the charges had already been incurred. They were not advance spending alerts that gave me an opportunity to prevent the charges. Receiving a partial invoice earlier than your normal billing cycle is actually part of the early warning system to help you avoid runaway usage. There's not really a way to predict the future and warn _before_ usage is incurred, so the next best thing is to let people know when a usage pattern has gotten unusual before a metric gets wildly high. The system recognizes the unusual usage pattern and sends a notification with an invoice for only the amount that's already been used. At that point, you can change build machine settings, manually pause projects, or do whatever is needed to keep usage in budget. > I did not receive an advance Spend, Usage, Budget, Threshold, or unusual-usage email alert before the charges accumulated. In particular, I did not receive an advance email warning between the first receipt and the additional USD 300.83 charge five days later. You should definitely have received an alert 50%, 75%, and 100% of your set budget ($200 by default) unless you've disabled notifications, so I'm going to flag this with the team to figure out what went wrong. A bug in the alert system would be a high priority issue. If you let me know your case number, I can make sure the engineering team knows about it.
airstairjp Hi Amy, Thanks for the quick and helpful reply. I've opened a support case: CSE_019cTeCgidqFnPaM I haven't knowingly turned off any notifications, so I'd really appreciate it if you could flag it to the engineering team to check why no budget alerts were sent. I also asked in the case for the refund request to go to a Billing specialist for manual review. Thanks again!
