Lesson 477 of 2116
Codex Tasks: Long-Running Asynchronous Work
The unlock of Codex Cloud is fire-and-forget tasks — work you delegate now and check on later. Treat tasks like Jira tickets, not chat messages.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1From chat turn to task
- 2async tasks
- 3task brief
- 4definition of done
Concept cluster
Terms to connect while reading
Section 1
From chat turn to task
A chat session is interactive — you watch the model think and steer in real time. A Codex task is asynchronous — you write a brief, hit submit, and walk away. The shift is psychological more than technical: you have to write the brief well enough that the agent can finish without you.
The task brief checklist
- 1Goal: the user-visible outcome in one sentence
- 2Scope: which files, modules, or routes are in play and which are off-limits
- 3Constraints: style rules, performance targets, things that must not change
- 4Acceptance checks: the exact commands or screenshots that prove done
- 5Output format: a PR, a patch file, a markdown report, or all three
How long should a task run?
Compare the options
| Task length | When to use | Risk |
|---|---|---|
| Under 5 minutes | Tight fixes, single-file edits | Could have been a CLI prompt |
| 5 to 30 minutes | Multi-file features with tests | Sweet spot — most async tasks |
| 30 to 120 minutes | Cross-cutting refactors | Watch for scope creep |
| Over 2 hours | Migrations, exhaustive audits | Break into sub-tasks |
Applied exercise
- 1Take a task you would normally do tomorrow morning
- 2Write its brief in the format above
- 3Submit it tonight as a Codex Cloud task
- 4Read the result tomorrow morning. Note where the brief was unclear and update your template
Key terms in this lesson
The big idea: tasks compound. Each clear brief teaches you to write the next one better, and your throughput climbs without working longer hours.
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “Codex Tasks: Long-Running Asynchronous Work”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 9 min
What Perplexity Is: Search-Augmented LLM, Not A Chatbot
Perplexity is built around the idea that every answer should cite its sources. Treating it like ChatGPT misses the point — and the reliability gap that comes with it.
Creators · 10 min
Spaces: Building Team Knowledge Bases In Perplexity
Spaces are Perplexity's project containers — system prompts, files, and shared chat history. They turn the search engine into a research workspace.
Creators · 10 min
Comet Browser: What It Does That Atlas And Operator Don't
Comet is Perplexity's full browser with a research-native sidebar and an action-capable agent. It plays differently than ChatGPT Atlas or Operator — and the differences matter.