Can I participate solo or on a team?

Yes. You can enter as an individual, a team, or an organization.

How many members are allowed per team?

There is no limit on team size but note some prizes have their own team-size restrictions, so check individual prize details.

Can I work on a project I already started?

Yes. If your project existed before the hackathon, you'll need to clearly document what's new, including evidence that Codex and/or GPT-5.6 was used during the Submission Period (timestamped session logs, commit history, etc.).

What categories can I enter?

There are four categories:

• Apps for Your Life

• Work and Productivity

• Developer Tools

• Education

Pick the track that fits your project best. If your project could fit more than one, choose the closest match — each project can only be entered into one track.

Do judges test my project?

They may, but they're not required to. If they do, they'll use the demo link, sandbox, or test account you provide. Make sure your README and instructions are clear.

Can I update my submission after the deadline?

No changes can be made to your submission after the Submission Period ends on July 21 at 5:00 PM PT. 

I've never used Codex before. Can I still compete?

Absolutely. Sign up for an OpenAI account, download Codex, request your free Codex credits, and dive in. The plugin has resources and commands to help you get oriented. Build Week is as much about exploring as it is competing.

Do I need a paid plan to participate?

No. You can participate with a Free plan. Free users have access to GPT‑5.6 Terra in Codex, and any Codex credits provided for the competition can be applied to extend usage for models available to your plan.

Do I need to use 5.6 for my whole project?

No. You can use any model you want for your project as long as you've used 5.6 for a part of it

Do I need to be a professional developer to enter?

No. The Education track in particular welcomes projects from students, educators, and learners. All tracks are open to anyone who meets the eligibility requirements.

Can my team be in different countries?

Yes, as long as each team member meets the individual eligibility requirements for their country of residence.

Can I use open source libraries or existing frameworks?

Yes. Standard development tools, libraries, and frameworks are allowed. You must comply with any applicable open source licenses, and you need to disclose any pre-existing code or third-party work in your submission.

What if I want to build a plugin or developer tool as my project?

That's a great fit for the Developer Tools track. Just make sure to include installation instructions, supported platforms, and a testing path for judges who won't rebuild it from scratch.

Do I have to use Codex?

Yes. Codex usage is required and must be demonstrated in your submission including your text description, demo video and highlight where Codex accelerated your workflow, where you made key product, engineering, or design decisions in your README. You'll need to provide a /feedback Codex Session ID from the primary thread where you built your project, and specifically, your demo video must include audio explaining how you used Codex.

Do I have to use GPT-5.6?

Yes. Your project must use GPT-5.6. Judges will look for evidence of this in your demo video and code repository; make sure it's clearly referenced in your README.

Can I use other models or tools alongside GPT-5.6 and Codex?

You can use standard libraries, frameworks, and third-party SDKs as long as you're authorized to use them. But your project must meaningfully use both Codex and GPT-5.6 — they can't be incidental or decorative.

What counts as "using Codex"?

Building your project with Codex — whether through the ChatGPT app, the Codex CLI, the IDE extension, or the SDK. You'll verify this by submitting the /feedback Session ID from the main thread where you did the majority of your core development.

How do I get the /feedback Session ID?

In Codex, type "/status" in the thread where you did the majority of your core work. This will not consume any credits, and will display your Session ID (a unique identifier for that thread). Copy it and paste it into the submission form. You should use the thread where most of your core functionality was built — not a side conversation or a test thread.

What if I worked across multiple Codex threads?

Submit the Session ID from the thread where the majority of your core functionality was built. If you had multiple significant threads, pick the most representative one. Your README should document how Codex contributed across your workflow.

How do I get Codex credits to build?

Registered participants can request $100 in free Codex credits to use for this hackathon. Complete the request form at https://forms.gle/Ncu6iGkaHq1SwUmEA before it closes on Friday, July 17th at 12:00 PM PT. Request early — the form will not reopen and Codex credits will not be distributed after that date. The last batch of Codex credits will be delivered shortly after the form closes. One code per Entrant. 

What if I use up all my Codex credits before the deadline?

As stated in the Official Rules: "Any additional charges incurred by the Entrant for the use of OpenAI products or services beyond the provided Codex credits or credits are the responsibility of the Entrant. Entrants are encouraged to monitor their usage so as not to incur additional charges." Watch your usage meter and plan accordingly.

How do I check how many Codex credits I have left?
Log into chatgpt.com with the account you used to request credits, go to Settings → Usage, and you'll see your credit balance and recent usage.

Will I get charged if I run out of credits?
No — Codex credits are prepaid. Once they're used up, Codex usage just stops. You won't be charged automatically unless you've turned on Auto top-up in Settings → Usage, so leave that off if you want to be sure you never go over.

I want to build with the OpenAI API — can I use my Codex credits for that?

You can build with any OpenAI tools, models, or APIs, but per the official rules, your project must be built with Codex and/or GPT‑5.6 to be eligible — quoting the rules directly: "Build any project with Codex and GPT 5.6 that fits into one of the following tracks" and, for projects that existed before the hackathon, they "must have been meaningfully extended using Codex and/or GPT-5.6 after the Submission Period start date." We are only distributing Codex credits for this event — we are not providing separate OpenAI API credits or tokens. Good luck building!

What do I need to submit?

• A working project built with Codex and GPT-5.6

• Your chosen track

• A text description explaining what you built and how it works

• A public YouTube demo video (see video requirements above)

• Provide a URL to your code repository for judging and testing. The repository must be either public (with relevant licensing) or private and shared with [email protected] and [email protected].

• Include a README with setup instructions, sample data (if needed), and clear guidance for running your project

• Make sure to highlight where Codex accelerated your workflow, where key decisions were made and how GPT-5.6 and Codex were used. This is an important part of how judges evaluate technical implementation and quality of the idea.

• Your /feedback Codex Session ID from your primary build thread

If you're submitting a Plugin or Developer Tool, also include: installation instructions, supported platforms, and a way for judges to test it without rebuilding from scratch (demo instance, sandbox, or test account).

What should be in my README?

At minimum: setup instructions, any sample data needed to run the project, and clear guidance on how to test it. Also document how Codex accelerated your workflow, where you made key decisions, and how GPT-5.6 is integrated. This directly feeds into how judges evaluate Technical Implementation and Quality of the Idea.

Can judges build my project from scratch to test it?

They are not required to. Make it easy — provide a working demo link, test account, or sandbox wherever possible. The easier you make it for judges to see your project working, the better.

My project covers multiple tracks. Which do I pick?

Pick the one that best fits. If you're genuinely torn, think about the primary audience and use case for your project. You can only enter one track, so choose the closest match.

I have a question the FAQ didn't answer. Where do I go?

Join the #build-week-chat in the OpenAI Discord or post on the Discussion Board.

Demo Video

What are the video requirements?

Your demo video must:

• Be 3 minutes or under (judges are not required to watch beyond 3 minutes)

• Be uploaded to YouTube as a public video

• Include a clear demo of your working project

• Include a voiceover (you can use AI to help record or narrate)

• Cover what you built AND how you used Codex AND how you used GPT-5.6

Wait — does my video really need a voiceover?

Yes. This is a stricter requirement than some hackathons. A screencast with background music won't cut it. Judges need to hear, in your own words (or AI-assisted narration), what you built and how you built it. Think of it as a short product demo where you're both the developer and the narrator.

What do I need to say about Codex and GPT-5.6?

Your voiceover should explain:

• What your project does

• How you used Codex to build it (not just that you used it — show the workflow, the key moments, the decisions it helped you make)

• How GPT-5.6 is integrated into the project and what it's doing

You don't have to show the Codex interface on screen, but your narration needs to be specific. "We used Codex to generate the backend" is less compelling than "We used Codex to scaffold the data pipeline and iterate on the API integration — here's what that looked like."

Can I use AI to help with my voiceover?

Yes. If recording your own voice isn't practical or you just don’t want to, you can use a text-to-speech or AI voice tool to narrate your video. Just make sure the narration is accurate and covers the required points above.

Does my video need to show the Codex interface?

It is not explicitly required, but showing Codex in action — even briefly — is a strong signal to judges that you actually used it. It also makes a more compelling case for the Technological Implementation criterion.

Can my video be in a language other than English?

Your video must be in English, or you must provide an English translation as part of your submission materials.

What makes a great demo video?

Record as you go, not the night before. The best videos show a real, working product with a clear problem statement, a crisp demo, and an honest explanation of how the tools were used. Three minutes is enough time to tell a good story — don't rush it, but don't pad it either.

What is the Devpost Hackathons Plugin?

The Devpost Hackathons Plugin is an optional tool you can install in Codex inside ChatGPT. It loads full context about OpenAI Build Week — including the challenge requirements, rules, tracks, submission form, and resources — so you can access everything you need without leaving your editor. It's also a capable AI assistant that can help you ideate, plan, and prepare your submission.

Do I need a Devpost account to use it?

Yes.

Is the plugin free?

Yes.

Do I have to use it?

No. The plugin is completely optional. You can register, build, and submit entirely through the hackathon website at openai.devpost.com. Using the plugin doesn't give you any advantage in judging and won't affect your eligibility.

How do I use it once it's installed?

Once the plugin is installed, you can start a conversation in Codex and interact with it directly. It has full context about this hackathon. Just ask it what you need or use one of the commands below.

What commands can I use?

• $find-hackathons — Show Devpost’s currently available hackathons and recommend some to you

• $start-hackathon — Trigger a workflow that will register, review the rules, and help you submit your project to Devpost

• $resources — Learn how to make your project succeed, and launch an optional guided build assistant that can help you get a best-practices proof of concept off the ground

• $prepare-submission — When your project is ready to share, do a full security and eligibility audit, making sure you submit with your best foot forward

• $submit — Complete your submission form and enter your project into a Devpost hackathon

Can the plugin help me build my project?

Yes. Beyond hackathon-specific commands, it runs inside Codex — so it can help you generate code, plan architecture, write specs, debug, and iterate just like you'd expect from Codex. Think of it as Codex with extra context loaded about this specific challenge.

What can the plugin NOT do?

A few important things to know:

• It is not the official source of truth. The Official Rules and the hackathon website always take precedence. If there's ever a conflict between what the plugin says and what the rules say, the rules win.

• It can make mistakes. Like any AI tool, it may occasionally produce information that's incomplete, outdated, or inaccurate — including about rules, deadlines, and prizes. Always verify against the Official Rules before acting on it.

• It cannot guarantee token access or prizes. Those are governed by OpenAI and the Official Rules, not the plugin.

• It cannot access your private code or files unless you share them in the conversation.

Does using the plugin count as using Codex for the purposes of proof of usage?

The plugin runs inside Codex, so your sessions within it are Codex sessions. However, judges are evaluating your project — make sure the work you're doing in Codex (with or without the plugin) is building something real. Running /checklist or chatting about your idea is not a substitute for actually building with Codex.

Can I use the plugin for other hackathons on Devpost?

During OpenAI Build Week, you can only register for the Build Week hackathon through the plugin. After that, you'll be able to find, register, and submit to other hackathons on Devpost using the plugin!

Which version of Codex should I use for this hackathon?

We recommend using Codex inside the ChatGPT desktop app (macOS or Windows) for the best experience. You can also monitor and steer your sessions from the ChatGPT mobile app, though mobile currently only connects to Codex sessions running on macOS.

Can I add teammates through the plugin?

Yes. During submission, the plugin gives you an invite link which you can share with your teammates so they can join. If you’re working solo, skip this step.

Can I edit my submission after I submit it?

Yes.