Configurable prompt macro buttons in Codex desktop

Open
#34,911 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

Start by locating the Codex desktop chat UI and the code that sends prompts to the current conversation. Map where user-managed settings or persistent data belong before deciding how macro creation, editing, ordering, removal, confirmation, and execution fit together. Done means visible, editable macros can send their full configured prompts to the open chat without introducing recurring automation.

Written by the indexing model from the issue text.

Description

app enhancement

Feature request

Add a user-configurable Macros area to the Codex desktop chat UI — ideally in the lower-right side of an open conversation.

A macro would be a reusable, visible button that sends a preconfigured prompt to the current chat. The prompt may be a short instruction or a long multi-line procedure/code block.

Desired behavior

  • Create, edit, reorder, and remove macros from Codex itself.
  • Give each macro a label and a full prompt body.
  • Run the macro in the currently open chat.
  • Support both simple prompts and substantial multi-line instructions.
  • Offer optional confirmation before sending a macro.
  • Keep macros user-managed and explicit; this is not a recurring background automation system.

Example uses

  • Clear or summarize the current chat context.
  • Run a project reset / context-cleanup instruction.
  • Trigger a standard import, release, QA, or verification workflow.
  • Send a complex repeatable command sequence without retyping or relying on clipboard snippets.

The aim is to make frequent, deliberate actions one click away while keeping their prompt contents visible and editable.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.