Vladislav Guzey

Posted on Aug 1

How to Prepare for the Next OpenAI Codex Ambassador Cohort

I am Vladislav Guzey (proflead), an OpenAI Codex Ambassador in Chiang Mai, Thailand.

If you are interested in a future Codex Ambassador cohort, the best preparation is not writing a perfect application. It is doing useful work for developers before the form opens.

This guide explains the role, the current program status, and a practical preparation plan you can start now.

Status checked August 1, 2026: applications are paused while OpenAI supports the current cohort. OpenAI plans to open another cohort, but it has not announced a date. Use the official Codex Ambassadors page as the source of truth.

What is a Codex Ambassador?

The OpenAI Codex Ambassador Program is a global community program. It brings together people who help developers learn and build with Codex.

The program is relevant to:

Developer meetup organizers
Open-source maintainers and contributors
Student community leaders
Workshop teachers
Codex power users who support other builders

You do not need to be a full-time content creator or have a large audience. A useful GitHub project, a clear tutorial, or a small hands-on workshop can show meaningful community impact.

The ambassador role as a simple loop

I think about the work as a four-step loop:

Listen to builders
      ↓
Create an event or resource
      ↓
Help people use it
      ↓
Share lessons and feedback
      ↺

Each part improves the next one.

1. Listen to builders

Find out what people actually need. New developers may need installation help. Experienced engineers may want code review, testing, migration, or automation examples. Open-source maintainers may care about issue triage and contributor workflows.

Do not choose an event topic only because it sounds impressive. Choose it because it removes a real obstacle.

2. Create something practical

Ambassador contributions may include:

Meetups and workshops
Hackathons or build days
Tutorials and videos
Open-source repositories
Codex skills and agents
Prompt and workflow examples
Event notes and learning materials

Reusable resources are especially useful. A workshop helps the people in the room. A public repository or guide can also help the next group.

3. Support people while they build

A good technical event should include time for participants to use the tool. A 60-minute talk with no practice may be interesting, but it does not show whether people can apply the ideas.

For a beginner workshop, I like a structure similar to this:

10 min  — explain the task and expected result
15 min  — demonstrate one complete workflow
30 min  — participants build with support
15 min  — demos, questions, and feedback

The exact timing can change. The important point is to give builders enough time to try, fail safely, ask questions, and continue.

4. Share honest feedback

Ambassadors can report what developers find useful, confusing, or difficult. This feedback gives the Codex team context from different cities, countries, skill levels, and working environments.

Useful feedback is specific. “People liked it” is less helpful than “five beginners could not understand where project instructions should live, so we added a short setup exercise.”

What support is listed?

OpenAI currently describes support including:

Codex and API credits for ambassador activities and events
Adaptable starter kits
Collaboration with ambassadors and the Codex team
Invitations to selected future events
Exclusive swag

Support can change between cohorts. Verify the exact details when a new application round opens.

What is the time commitment?

The current expectation is about two to four hours per week and at least one contribution each month.

Treat this as regular community work, not a single application task. Some weeks may be quiet. Event weeks may require more preparation.

Before applying, ask:

Can I contribute consistently?
Do I have a community or audience I understand?
Can I complete at least one realistic activity each month?
Can I listen to feedback instead of only promoting my own ideas?

A five-part preparation plan

The following is my personal advice, not an official OpenAI checklist.

Step 1: Build with Codex

Use Codex on something real: a personal project, work task, open-source issue, workshop example, or automation.

Keep a small record:

## Project
What did I build or change?

## Workflow
How did I use Codex?

## Result
What worked?

## Lesson
What would I teach another developer?

Three strong examples are enough to begin.

Step 2: Publish one reusable resource

Choose a problem you understand and create one resource that solves it. This could be a short DEV post, GitHub example, video, Codex skill, or workshop worksheet.

Make it easy to verify:

State the goal.
List requirements.
Show the workflow.
Explain common mistakes.
Include the final result.

Step 3: Help a small group

You do not need to begin with a conference. Invite a local developer group, student club, online community, or several colleagues.

Run a small session and collect questions. Those questions often reveal what your next tutorial should explain.

Step 4: Define your local focus

Write one sentence in this format:

I help [specific group] use Codex for [specific need] through [realistic activity].

For example:

I help university students in Chiang Mai learn practical coding-agent workflows through monthly beginner workshops.

This is clearer than “I want to grow AI worldwide.”

Step 5: Propose one first-month contribution

Keep it small enough to complete:

audience: 20 local developers
format: 90-minute hands-on workshop
topic: using Codex to understand and improve an existing repository
result: each participant completes one reviewed change
follow_up: publish notes and example files

Specific plans are easier to understand and deliver.

What I learned from an event in Thailand

On July 18, 2026, I hosted an OpenAI Build Week community meetup in Chiang Mai. Developers, founders, students, and AI-curious creators explored Codex across the app, CLI, IDE, and cloud.

My main lesson was simple: different experience levels can work well in one room when the activity has a clear goal and people are encouraged to help one another.

If you are in Thailand, follow my Codex events and resources page for future meetups, workshops, hackathons, recaps, and tutorials. You can also see my official OpenAI Ambassador profile.

Frequently asked questions

Do I need previous event experience?

Existing community experience is useful, but professional event experience is not required. Builders who are ready to start bringing people together locally may also be a fit.

Can several people apply from one city?

Yes. The program is about supporting a community, not reserving a city for one person.

Do I need to be an expert programmer?

OpenAI does not list a required degree, job title, or fixed number of coding years. Practical Codex experience and the ability to help builders are more relevant.

When will applications reopen?

No reopening date has been announced. Check the official program page instead of relying on an old application link.

Resources

The application form may be paused, but your preparation can start today: build something real, document the workflow, help a small group, and listen carefully to what developers need.

DEV Community