Skip to the content.

Set Up a Teammate

A plain-English guide for people who want Codex to keep an eye on the work without babysitting it all day.


The short version

This is about giving Codex a steady view of your work so it can notice what changed.

Think of it like this:

It is useful when the important stuff is scattered across Slack, email, docs, notes, calendars, or trackers.


What this means in real life

Codex can help spot things like:

So instead of you checking five places all day, Codex can bring the useful bits to you.


Who this is for

This is handy if you:

If your work is mostly one file or one task, this is probably overkill. If your work is spread everywhere, it gets useful fast.


What you need to do

  1. Connect the tools where your work happens.
  2. Tell Codex what matters and what is just noise.
  3. Start with one thread or one workstream.
  4. Add automation so it can check back on its own.
  5. Keep using the same thread so it learns what to pay attention to.

A good way to ask

Try something like:

Check the places where my work happens and tell me what needs my attention.
Look for anything important, surprising, or likely to get missed.

If you want it to be more specific:

Check Slack, email, calendar, and notes for this project.
Tell me what changed, what is blocked, and what I need to answer.

What makes it work well


The trap to avoid

The trap is trying to make it monitor everything at once.

That usually turns into noise, not help.

Start with one useful check and make it earn more responsibility.


Plain-English summary

Set up a teammate means turning Codex into a useful extra pair of eyes on your work.

It watches the places you already use, notices changes, and points out the things worth your attention.


Source: OpenAI Codex use cases page, “Set up a teammate”