Add recurring task command similar to Claude Code /loop for periodic PR checking

Open
#35,565 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

The issue does not name files, tests, or an entry point. Start by locating the CLI command architecture and session lifecycle, then define the command syntax, cron scheduling, task listing and stopping, seven-day expiry, and tests that establish the completed behavior.

Written by the indexing model from the issue text.

Description

automations CLI enhancement
What variant of Codex are you using?

cli

What feature would you like to see?
Use Case

My primary usage scenario is periodically checking pull requests, including PR status updates, new comments, CI execution results, code change reviews, etc. It is inefficient to manually trigger queries over and over. A built-in recurring task capability can greatly optimize this workflow.

Core Requirements

Add a repeat execution function referencing Claude Code’s /loop:

  1. The scheduled tasks are limited to the current CLI session only.
  2. Support cron expressions to configure custom execution frequency.
  3. All scheduled tasks have a hard upper limit of 7 days total runtime; tasks auto expire after 7 days regardless of session status.

The specific command format, underlying logic, parameter constraints and implementation details can be fully designed by the project maintainers. I only put forward the functional demand.

Basic Expectation

Simple management commands to list ongoing scheduled tasks and stop tasks are necessary for daily use.

Benefit

Automate regular PR inspection work, reduce repetitive manual operations during development.

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.