### What feature would you like to see? Codex now supports non-interactive execution, and you only need to use the exec parameter. It also allows restoring historical conversations from sessions, such as `codex resume `. However, sometimes we may need to make a call that carries history forward in a non-interactive scenario. In such cases, you might need to use a command like `codex resume exec `. ### Additional information _No response_

Potential duplicates detected. Please review them and close your issue if it is a duplicate. - #3497 - #3817 - #4219 - #4592 - #3492 *Powered by [Codex Action](https://github.com/openai/codex-action)*

Support non-interactive execution with historical session records

Resolved 💬 3 comments Opened Oct 15, 2025 by lingtaolf Closed Oct 16, 2025

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What feature would you like to see?

Codex now supports non-interactive execution, and you only need to use the exec parameter. It also allows restoring historical conversations from sessions, such as codex resume <session>. However, sometimes we may need to make a call that carries history forward in a non-interactive scenario. In such cases, you might need to use a command like codex resume <session> exec <prompt>.

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 10 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#3497
#3817
#4219
#4592
#3492

Powered by Codex Action

lingtaolf · 10 months ago

https://github.com/lingtaolf/codex/pull/1

kvcop · 10 months ago

it already exists and i've used it in a couple of scripts. You should switch places the exec and resume <id>

https://github.com/openai/codex/pull/3537 - this is the pull that enabled current behavior

I think you should consider closing this, or maybe editing this for added documentation, but --help already has this