Add context-aware suggested next prompts to the composer
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Codex CLI 0.153.0. The request could also benefit the App and IDE Extension composers.
What feature would you like to see?
Add an optional context-aware suggestion for the logical next user prompt after Codex completes a turn.
For example, after implementing a change, Codex could suggest:
Run the full test suite and fix any failures.
The suggestion could appear as ghost text or a suggestion chip in the composer. A user should be able to accept it with Tab or Right Arrow, dismiss it with Escape, or simply start typing something else. It must never run automatically.
This is similar to the next-step suggestions available in Claude Code and would reduce repetitive typing during common agentic loops such as implement, test, review, and commit.
Ideally this would be opt-in through a setting and generated from the current conversation and workspace state, so it recommends a concrete next action rather than a generic canned prompt.
Additional information
There currently appears to be shell completion and support for reusable custom prompts, but no native option for dynamically predicting the next conversational prompt. A static AGENTS.md instruction can make Codex print a recommendation in its response, but it cannot prefill or offer that recommendation directly in the composer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Codex CLI composer and reviewing the existing shell-completion and reusable custom-prompt flows. Define how an opt-in suggestion is generated from conversation and workspace state, how it is accepted or dismissed, and how to verify that it never runs automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100