Feature Request: Persistent Pre-Prompt via `/prep` Command a **persistent pre-prompt** that is automatically prepended to every user prompt in a Codex session.

Resolved 💬 5 comments Opened Dec 12, 2025 by FromAriel Closed Jan 31, 2026

What feature would you like to see?

Feature Request: Persistent Pre-Prompt via /prep Command

Description

Add support for a persistent pre-prompt that is automatically prepended to every user prompt in a Codex session.

Proposed command:

/prep "instruction text"

Once set, the provided text is prepended to every subsequent prompt sent to the model.

---

Example

User runs:

/prep "Always preserve existing functionality. Output full dataset only."

Then types:

Change the value on line 5 to 42.

Codex sends internally:

Always preserve existing functionality. Output full dataset only.

Change the value on line 5 to 42.

This applies to all prompts until changed or cleared.

---

Motivation

Many Codex workflows require consistent constraints across multiple turns (e.g. coding conventions, no refactors, preserve comments, project-specific rules).

Currently, users must retype these instructions every prompt or risk the model ignoring them even if in Agents.md A persistent pre-prompt removes that friction and improves consistency without changing model behavior.

---

Expected Behavior

  • /prep "text" sets the active pre-prompt
  • Pre-prompt is prepended to every prompt
  • Persists for the current session
  • No changes to normal prompt handling otherwise
  • _/prep clear to remove it_

---

Scope

This is a lightweight client-side feature:

  • No model changes required
  • Simply concatenate pre-prompt + user prompt before submission and display pre-prompt with user prompt and/or preview pre-prompt on input line.

---

Why This Fits Codex

  • Improves iterative coding workflows
  • Reduces accidental constraint violations
  • Aligns with how advanced users already work
  • Minimal surface area, predictable behavior

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗