# Codex research workflow · starter kit

Use this kit in a new local folder. Start with the supplied example or edit TASK.md for your own question. Open that folder in Codex. If your project already has AGENTS.md, merge only relevant guidance; do not replace existing instructions.

## Start

Copy this message into Codex:

Read AGENTS.md and TASK.md in this folder. Complete the assigned research brief using the source map, save the outputs and checks, and pause at the requested handoff. Report what you actually checked and what remains unresolved.

The example first task deliberately pauses before a planned continuation. Ordinary tasks need no forced pause. Browser/source access depends on your Codex tools and account. Use only material you may share with the selected service. File instructions do not change sandbox or connector permissions.

## Continue

Usually continue the same chat in the Codex app, or use codex resume in the CLI (codex resume --last selects the latest session in the current directory). A changed assignment does not itself require a new chat. The files make the work inspectable in either case; a fresh session can use them for a handoff, as in the recorded example. This kit was tested in Codex, not other agents.

Update TASK.md when the assignment changes. Then copy:

Read AGENTS.md, the current TASK.md and STATE.md. Inspect the referenced outputs. Compare the current assignment and inputs with the checkpoint, preserve what still applies, and complete the remaining work. Separate reused checks from checks of new or changed output. Save CHECKS.md and STATE.md and report any unresolved question.

brief.md, CHECKS.md and STATE.md are created by the agent. They are ordinary files, not built-in Codex commands or automatic memory. Saving them does not schedule a future run. Keep snapshots/version history before changing an accepted output.

## Read the example

The example directory contains the recorded handoff and continuation; record/TEST.md describes scope and limitations. Copy starter/ into a fresh folder to run your own task. Do not confuse the proposed design-team workshop with an executed team experiment.

## Inspiration and documentation

Atlas adapted the general ideas of explicit deliverables, inspectable checks and durable state. The files and interface are original Atlas work.
- https://x.com/beamnxw/status/2107522996046905797
- https://x.com/0xwhrrari/status/2093685107534000560
- https://developers.openai.com/blog/codex-as-a-platform
- https://learn.chatgpt.com/docs/agent-configuration/agents-md
- https://learn.chatgpt.com/docs/agent-approvals-security

## Inspect the recorded example

The example/ folders contain selected outputs, not a workspace to resume in place. To repeat the changed assignment, finish starter/TASK.md first, then replace it with example/resumed/TASK.md in your own working folder and use the resume message. CHECKS.md and STATE.md in example/resumed/ are publication copies: local diagnostic paths are described rather than linked. The original run is preserved by Atlas. Read record/TEST.md for scope and results.