Tasks

Tasks are the work items inside a workspace. Use them for bugs, features, follow-ups — anything that needs tracking and an owner.

Anatomy of a task

• Title and description.
• Status — pending, in_progress, review, stopped, or done.
• Assignee — a teammate or the Codex agent.
• Linked pull request — populated automatically when the task is shipped.
• Comments — discussion thread, with mentions.

Creating a task

1. Open the Tasks panel from the workbench.
2. Click New task.
3. Fill in title, description, and optional assignee.
4. Save.

Assigning to Codex

Mention the Codex agent as the assignee. The task moves to in_progress; Codex spins up a session and starts working. You can monitor progress inline or open the linked chat thread.

When Codex finishes, the task moves to review with the resulting pull request linked. Approve, request changes, or merge from there.

Webhook-driven tasks

Connect a webhook integration in workspace settings to GitHub, GitLab, or Bitbucket. Incoming events become tasks automatically — bug reports, failing CI runs, review requests. They land in the same queue as work you planned.

Mentions

Use @ in task descriptions and comments to mention teammates or the agent. Mentioned users get a notification; mentioning the agent in a comment kicks off a Codex run scoped to the task.

Filtering and searching

Filter by status, assignee, or linked PR state. Search across titles and descriptions from the task panel header.