⌘K
NextBlock™ CMS Just submitted our application for **NextBlock CMS**! 🚀 NextBlock is an open-source, full-stack CMS framework built natively for **Next.js 16 (App Router + RSC)** and **Supabase (PostgreSQL JSONB)**. We’ve focused on: * **Zero-Config 1-Click Deploy:** Automated Supabase database migrations on build. * **100/100 Lighthouse Defaults:** Tiptap visual editor renders PostgreSQL JSONB directly into React Server Components, eliminating client hydration overhead and HTML sanitization taxes. * **Cortex AI & Native MCP:** Model Context Protocol server support (`/api/mcp`) for deterministic, schema-constrained block synthesis. * **GitHub:** https://github.com/nextblock-cms/nextblock * **Live Sandbox:** https://cms.nextblock.dev Looking forward to the review process and collaborating with the Vercel DX team! 🧱
Axyl1410 Hi! I applied for the Summer 2026 Vercel OSS Program, but I’m not sure whether my application was successfully submitted. I also didn’t receive a confirmation email. Is there any way for applicants to verify whether their application was received, or is there normally no confirmation email after submitting the form? I’d like to avoid submitting a duplicate application if my original submission went through. Thanks!
Amy Egan If you reached the final page that says, "Thank you," then your application was received :) You'll get an email about a week after applications close letting your know whether or not your project was accepted
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?
