Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Allow Run Now on an automation with one-time additional context [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19619•Fetched 2026-04-26 05:13:49
View on GitHub
Comments
3
Participants
2
Timeline
5
Reactions
0
Author
heysarverheysarver
Participants
etraut-openaietraut-openaiheysarverheysarver
Timeline (top)
commented ×3labeled ×2

Error Message

  • “Run the repo-maintenance automation, but include this error log.”

Root Cause

This is different from editing the automation itself because the extra context should not persist. It is also different from just starting a normal chat because I want to reuse the automation’s configured prompt, project/worktree, model/settings, and any future automation-specific behavior.

RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

App

What feature would you like to see?

Add a way to run an existing automation ad-hoc with one-time additional context.

Today, if I have an automation that is mostly reusable but needs run-specific context, the workflow is awkward:

  1. Edit the automation prompt to include the temporary context.
  2. Run it, or paste the modified prompt into a new chat.
  3. Remove the temporary context afterward so the saved automation is not permanently changed.

This makes automations less useful as reusable workflows. The saved automation prompt is the stable procedure, but many real runs need a small amount of extra context, such as:

  • “Run the release-review automation, but focus on this PR.”
  • “Run the repo-maintenance automation, but include this error log.”
  • “Run the weekly summary automation now, but also consider this incident.”
  • “Run the code-review automation against this branch/commit/range.”

The ideal UX would be something like:

  • A Run Now... action that opens a short input field for optional run-specific context.
  • The automation starts a new run using:
    • the saved automation prompt,
    • plus the one-time context,
    • without modifying the saved automation definition.
  • The resulting thread should show both the base automation and the extra context used for that run.

This is different from editing the automation itself because the extra context should not persist. It is also different from just starting a normal chat because I want to reuse the automation’s configured prompt, project/worktree, model/settings, and any future automation-specific behavior.

Additional information

Related but not exact duplicates:

  • #13925 - single-use / one-shot automations
  • #17840 - Run Now not starting
  • #18247 - automation permissions / heartbeat context discussion
  • #16695 - per-automation sandbox/profile overrides

Those cover adjacent automation execution and context problems, but I could not find an issue specifically for “Run Now with temporary additional context.”

extent analysis

TL;DR

Implement a "Run Now..." action with an input field for optional run-specific context to enable ad-hoc automation runs without modifying the saved automation definition.

Guidance

  • Introduce a new input field in the "Run Now..." action to capture one-time context, allowing users to provide temporary information without altering the saved automation prompt.
  • Modify the automation execution logic to concatenate the saved automation prompt with the provided one-time context, ensuring the resulting thread displays both the base automation and the extra context used for that run.
  • Consider implementing a mechanism to prevent the one-time context from being saved or persisted, ensuring the automation definition remains unchanged.
  • Review related issues (#13925, #17840, #18247, #16695) to ensure the proposed solution does not introduce conflicts or inconsistencies with existing automation execution and context management features.

Example

No code snippet is provided as the issue lacks specific technical details about the automation framework or implementation.

Notes

The proposed solution focuses on introducing a new input field and modifying the automation execution logic, without altering the underlying automation framework or persistence mechanisms.

Recommendation

Apply a workaround by introducing the "Run Now..." action with an input field for optional run-specific context, as this addresses the primary concern of enabling ad-hoc automation runs without modifying the saved automation definition.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#dependency conflict#environment setup#docker error#permission error#memory optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Allow Run Now on an automation with one-time additional context [3 comments, 2 participants]