Guide/Work with agents

Tasks and agent runs

Manage Codex work from the initial brief to the pull request, and keep your team up to date.

On this page
Interface diagram · example content
Todo1
WEB-3Document the local development setupWebsite
In Progress1
WEB-2Set up the projectWebsite
In Review1
WEB-1Review the README changesWebsite
A task stays on the board as it moves from planning to review.

Understand the workflow

Use the board to track work and the execution history to follow what Codex is doing. They show different parts of the same task.

Board statusHow to use it
TodoRecord the work and its completion criteria.
In ProgressTrack work currently being carried out.
In ReviewCheck the changes and linked pull request.
CompletedKeep a record of work that is finished.

Give Codex a clear task

Open a task and set its project and description. Include the intended change, the files or area to work on, and how you will check the result.

Reusable task brief
Goal: Add a local development section to the README.
Scope: README only.
Done when: Existing install, dev, and test commands are documented.
Check: Compare the commands with the repository configuration.

Follow and continue a run

  1. Open the task’s Executions tab. Each run is listed separately.
  2. Check the status, turn count, available token usage, and plan progress.
  3. Respond to approvals and questions on the machine running Codex. To refine the result, send a follow-up instruction from that execution.
Interface diagram · example content
WEB-1Document the local development setup
1ExecutionsPull requestsActivity
Agent executions Start Codex2
No agent executions yet.
The execution history is the place to start and follow a run.

Connect pull requests

  1. In Workspace Settings → Integrations, connect the Agentboard GitHub App installation for the repository you use.
  2. Open Projects and select the project. Set its Remote repository.
  3. With a pull request associated with the task, check the Pull requests tab in the task details.
Non-draft PRIn Review
Merged PRCompleted

Automatic updates require the repository connection and a task-to-PR association. Draft pull requests do not advance a task to In Review.

Work with your team

Share the task board and progress in a Team workspace. Each person configures the local repository directory on their own machine before starting Codex.

Shared in the workspace

Tasks, projects, and execution progress.

Kept on your device

Local directory paths, Codex thread IDs, and responses to local approvals.

Next guideMCP connectionRead and manage the board from another AI tool.