Event-driven background task callbacks

Open
#33,542 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

No source files, tests, or entry points are named. Start by locating Codex CLI's process execution and session lifecycle handling, then compare the linked Claude Code references; done means a background task returns the session to idle, consumes no waiting tokens, and resumes the original thread with exit status and output.

Written by the indexing model from the issue text.

Description

automations CLI enhancement tool-calls
What variant of Codex are you using?

CLI

What feature would you like to see?

Please allow Codex CLI to start a background process and return the session to idle. Waiting should require no model calls or token usage.

When the process exits, Codex should automatically notify and resume the original thread with its exit code and output. If another turn is active, the event can be queued until that turn finishes.

Desired flow:

Start background task → session becomes idle → zero-token waiting → task exits → original thread wakes up → Codex continues automatically

Claude Code references:

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.