Feature request: Add an in-app Prompt Snippets panel for high-frequency prompts

Feature request

Please consider adding a lightweight Prompt Snippets / Prompt Panel feature to the Codex App.

The idea is simple: users should be able to save frequently used prompts inside the Codex App and quickly insert or send them when needed, without having to retype them or copy them from Notes, text expanders, or external documents.

This would not replace Skills, AGENTS.md, slash commands, or deep links. Instead, it would fill the gap between a full reusable Skill and an external note-taking workaround.

Problem

In daily Codex App usage, I often reuse short prompts or one-paragraph instructions, for example:

• "Please only review the current uncommitted changes. Do not modify any code."
• "Only verify the VM-related part. Do not inspect any report documents."
• "Generate a concise Chinese acceptance report based on the current diff, including completed work, remaining risks, and next steps."
• "Only run the build validation and confirm whether BUILD SUCCEEDED. Do not perform real-device manual testing."
• "Only re-check the previously failed or uncertain acceptance items. Do not repeat checks that already passed."
• "Inspect the current branch and changed files, then tell me whether this can be submitted."

These prompts are used frequently, but they are usually just a few sentences. They do not always justify creating a full Skill. However, manually retyping them or switching to Notes to find, copy, and paste the right prompt interrupts the Codex workflow.

For high-frequency users, this friction adds up. The prompts themselves are small, but they are important because they define task boundaries, review scope, validation expectations, and output format. When these prompts are managed outside the Codex App, several problems appear:

1. Users have to leave the Codex App to search for the right prompt.
2. It is easy to copy an outdated version of a prompt.
3. Short, frequently used prompts get mixed with long, complex prompts in external notes.
4. Users may put temporary instructions into AGENTS.md or Skills just to avoid retyping them, even when those instructions should not persist across tasks.
5. Beginner users and vibe-coding users may not know how to create and manage Skills, but they still have many repeated prompts they want to reuse.

Why existing features do not fully solve this

Skills are too heavy for many short prompts

Skills are great for reusable workflows, project-specific capabilities, scripts, references, and structured procedures.

But many high-frequency prompts are much smaller than that. For example:

"Please only review the current diff and do not modify code."

Creating a Skill for this kind of prompt feels too heavy. The user has to think about naming, description, trigger scope, implicit invocation behavior, file structure, and whether it will clutter the Skills list.

A Prompt Snippet should be lighter: just a saved piece of text that the user explicitly chooses when needed.

AGENTS.md is persistent guidance, not per-turn prompt reuse

AGENTS.md is useful for stable project rules and long-term working agreements.

But many repeated prompts are only relevant to the current turn or current task. For example:

• This time, only review.
• This time, only build.
• This time, ignore report documents.
• This time, only re-check failed acceptance items.

These instructions should not always be loaded for every future task. Putting them in AGENTS.md can pollute unrelated work and make Codex over-constrained in later conversations.

A Prompt Panel would allow users to send these instructions only when they are actually needed.

Slash commands are not user-managed prompt snippets

Slash commands are useful for controlling Codex and invoking built-in behaviors or Skills.

But what I am asking for is different: a user-managed library of small, frequently used natural-language prompts. The user should be able to create, edit, search, pin, and send these snippets directly in the Codex App.

Deep links are useful, but not a real in-app prompt library

Deep links can help open a new thread with a prefilled prompt, which is useful for external automation.

However, they do not replace an in-app Prompt Panel because:

• They require users to manage links outside Codex.
• Long prompts need URL encoding and are not easy to edit.
• They are better suited for starting new threads, not quickly sending follow-up prompts inside the current thread.
• They do not provide an in-app searchable library.
• They still require switching away from the current Codex workflow.

External Notes and text expanders are workarounds, not a Codex workflow

Right now, the practical workaround is to store prompts in Apple Notes, Notion, Raycast snippets, Alfred snippets, or another text tool.

This works, but it is not ideal for an interactive coding-agent workflow. Codex users often need to steer the agent immediately after a task completes: review the diff, only check failed items, do not modify code, run build only, summarize risks, etc.

These frequent follow-up prompts should be available inside the Codex App itself.

Deprecated Custom Prompts are not the right long-term answer

The older Custom Prompts feature is not a good replacement for this request. It is deprecated, is not an app-first prompt management UI, and still feels closer to a technical command mechanism than a lightweight user-facing snippets panel.

This request is specifically for an in-app, user-friendly prompt snippet library.

Proposed solution

Please add a lightweight Prompt Snippets / Prompt Panel to the Codex App.

A minimal version could include:

1. Create, edit, duplicate, and delete prompt snippets.
2. Each snippet has a title and prompt body.
3. Open the panel from the composer, sidebar, command palette, or slash menu.
4. Click a snippet to either:

• Insert into composer
• Send immediately

1. Search snippets by title or content.
2. Pin favorite snippets.
3. Support global snippets and project/workspace-specific snippets.
4. Snippets are not automatically included in context. They are only sent when the user explicitly selects them.
5. Optional local-only storage or account sync.
6. A warning not to store secrets, tokens, passwords, or private credentials in snippets.

Possible future enhancements

Later versions could add:

• Folders or tags.
• Keyboard shortcuts for favorite snippets.
• Variables such as {branch}, {workspace}, {changed_files}, or {selected_files}.
• A "Promote to Skill" action when a snippet becomes complex enough to deserve a full Skill.
• Import/export for sharing prompt libraries between machines.
• Per-project snippet sets.
• Default behavior per snippet: insert only, or send immediately.

Example use case

After Codex modifies an iOS app, I often want to send this kind of follow-up:

Please only review the current uncommitted changes. Do not modify any code. Focus on whether the build passes, whether the diff matches the original task, and whether there is any regression risk. Please output a concise acceptance report with: conclusion, verified items, remaining risks, and next steps.

This is a prompt I may use many times a day. It is not complex enough to justify a Skill, but copying it from Notes every time is unnecessary friction.

With a Prompt Panel, I could save it as "Review current changes" and send it with one click.

Why this matters

This feature would be especially helpful for ordinary users, students, beginner developers, and vibe-coding users.

Advanced users may be comfortable creating Skills for complex workflows. But many users simply want to save a few reliable prompts that help them steer Codex consistently.

A lightweight Prompt Panel would make good prompting more reusable without forcing every reusable prompt to become a Skill. It would reduce context switching, reduce repeated typing, reduce accidental use of outdated prompts, and make Codex App feel more like a complete coding-agent workspace.

Summary

Please consider adding an in-app Prompt Snippets / Prompt Panel feature.

Current features each solve a different problem:

• Skills are best for reusable workflows.
• AGENTS.md is best for persistent project guidance.
• Slash commands are best for controlling Codex or invoking existing features.
• Deep links are best for external automation and opening prefilled threads.
• External Notes are only a workaround.

There is still a missing lightweight layer for prompts that are too small for Skills but too frequent to keep retyping or copying from Notes.

A built-in Prompt Panel would fill that gap and significantly improve the daily Codex App workflow.