Deadline TOMORROW | last minute tips - OpenAI Build Week
( http://devpost.com )
Tomorrow's the day!! 🎉 Submissions close Tuesday, July 21st at 5:00 PM PT. This is it, go through this tonight and you're golden.
First, the rules ask you to build your project with both Codex and GPT-5.6. This does not require you to use the API or to have API credits.
A few things to sort out tonight before you dive into the checklist 🤿:
-------------------------------------------------------------------------
*
⬆️ Upload your video early. Getting a demo video ready is really a few steps, not one: upload to YouTube, wait for it to finish rendering, grab the public (unlisted OK) link, then paste that link into your Devpost submission. Each of those can take a few minutes, so don't start this at 4:50 PM.
*
👨💻 Double check your code repo permissions, and if it's private, make sure it's shared with testing@devpost.com and build-week-event@openai.com. If you'd rather do this later tomorrow, that's okay, just set yourself a reminder now so it doesn't slip your mind. An unshared repo at the deadline can get you disqualified, so don't let this be the thing that trips you up.
*
📋 Read your project description out loud. If it sounds like it was written by an AI and not by you, rewrite it. Judges read these.
*
🎥 Watch your own video. Make sure the audio is clear and the voiceover (required!) actually addresses Codex and GPT-5.6, not just "we used AI." Judges may not watch beyond the 3-minute mark. Trim it down if you need to: speed up playback and cut out loading or typing.
*
📝 Save your submission before you close the tab. Obvious, but it happens! Navigate to the My projects ( https://devpost.com/submit-to/30223-openai-build-week/manage/submissions ) page on the navigation bar and you’ll see your submissions tagged Submitted in green.
Submission checklist:
---------------------
* Your project runs and functions as described, test it fresh
* Demo video is uploaded to YouTube as a public (unlisted OK) video and the link is in your submission form
* Voiceover (required) covers what you built, how you used Codex, and how you used GPT-5.6
* /feedback Codex Session ID is retrieved and entered in your submission form (see below if you’re having trouble)
* Code repo (if private, is shared with testing@devpost.com and build-week-event@openai.com)
* README has setup instructions, sample data if needed, and documents how Codex and GPT-5.6 were used throughout
* If you're submitting a plugin or developer tool, installation instructions, supported platforms, and a way to test without rebuilding from scratch (demo instance, sandbox, or test account) are included
* Team members have been added to your submission AND have accepted their invitations
* Submission is marked as submitted (not saved as a draft)
A few more tips:
----------------
Stuck on your /feedback Session ID? Easy fix: run /feedback as a slash command from the "/" menu inside an official Codex interface. If you built your project somewhere else, just open your codebase in Codex Desktop or CLI and run /feedback from there. (Same trick works for /status.) We want the session where most of your work was done.
With this many builders submitting at once, aim to have your submission in around 3 hours before the deadline as a comfortable buffer. You can keep polishing right up until the very last second, so submitting early just means you're covered, not scrambling if something unexpected pops up right when you need it least.
If you're using the Devpost Hackathons Plugin to help with any of this, we love that! It can knock out things like your README, session ID, and repo sharing fast. Just make sure your submission appears on your Devpost My Projects page after you submit through the Plugin. Check yourMy Projects page ( https://devpost.com/submit-to/30223-openai-build-week/manage/submissions ) and confirm your project shows as Submitted, not just saved as a draft, before the deadline.
🔒 One important heads up: once the clock hits 5:00 PM PT Tuesday, that's it, submissions lock in. No late entries, and no changes to your project, video, team, or anything else after the deadline without putting your eligibility at risk. So get everything exactly how you want it before then!
If you're not going to submit, that's okay too, come check out the project gallery, there's going to be some genuinely awesome stuff in there.
Questions? Head to#build-week-chat ( https://discord.gg/openai ) in the OpenAI Discord. And if you're local to aBuild Week event ( https://luma.com/calendar/cal-FhWvOxHV0AGL38z ), tonight is a great night to show up and submit alongside other builders. You've got this, let's go!! 💪
You received this email because you signed up for OpenAI Build Week. If you're no longer participating, you can unregister here ( https://openai.devpost.com/ ).
© 2026 Devpost, Inc. All rights reserved. Unsubscribe from these notifications ( https://devpost.com/notification_subscriptions/T5j5oAnlkUb6ljxdVtOF8g )
action requiredLive GPT-5.6
Analysis complete
Devpost says the OpenAI Build Week submission closes Tuesday, July 21st at 5:00 PM PT and that projects must be built with both Codex and GPT-5.6. The calendar year is not stated in the deadline sentence.