Custom prompts - passing arguments

[michalkos]

What feature would you like to see?

Please implement functionality to allow custom arguments (e.g., $ARGUMENTS) to be passed and rendered within the .md file when executing slash commands.

Additionally, the first line of the .md file could be used as a command title in the TUI. If the line exceeds the maximum allowed length, it should be truncated accordingly.

Once [pull request #2471](#2471) is merged, it would be great to support this functionality in custom commands as well.

Example

# Create a git commit

Based on the code changes, create a single git commit.

If `--push` argument is present, you can run `git push`.

**DO NOT** run `git add` unless asked by argument `--add`.

**DO NOT** add information that the commit is generated by Codex.

## Context

- Current git status: !`git status`
- Current git diff (staged and unstaged changes): !`git diff HEAD`
- Current branch: !`git branch --show-current`
- Recent commits: !`git log --oneline -10`

## Passed arguments 

`$ARGUMENTS`

Are you interested in implementing this feature?

No response

Additional information

No response

[cs-asimoes]

+1, would be really useful! i was just reading the source code to understand if this was already there!

[suvam-jaiswal]

+1, arguments to saved prompts and adding additional content like this is super useful

[SuperPauly]

It would be nice to have a more Git centric approach where codex ask if you want to create a new branch for this change.

Also does appropriate Git commits along the way so if you leave it running the user and Codex can easily step back to a point where it was in a working state regardless of Codex running or not.

This way you can see in the Git logs the branches and iterative changes over time to pick up any mistakes or changes that may be important or may have caused problems.

As this also would you help diagnose issues and looking at the state of repository with the many, many tools available for Git repository viewing and analysis out there already.

[michalkos]

@SuperPauly, how you configure the command is entirely up to you. The example simply demonstrates how to use arguments in the setup.

[dedrisian-oai]

Thanks! Tracking this.

[SystemicVoid]

+1 That would be very useful, thanks!

[sergigp]

This will make prompts much more powerful. Imo ideally we should be able to pass multiple arguments with $1, $2, ...

[avxkim]

i initially thought i could use something like: /code-review pass PR link and do it, but just found out, that it doesn't accept any args... Hope they will implement this soon.

[alexx-ftw]

This will be a game changer for me. I rely on this a ton with Claude Code. +1

[evandavid1]

Status update / proposal

• Draft PR: Custom prompts: passing arguments ($1..$9, $ARGUMENTS) + @ file picker + frontmatter hints #3565 (minimal, backward‑compatible).
• Scope:
  • Arguments: $1..$9, $ARGUMENTS, and $$
    (literal); simple quoting for paths with spaces.
  • “@” file picker: inserts quoted file paths (no
    content inlining, no auto‑exec).
  • Optional frontmatter: description and argument-
    hint shown in the slash palette; frontmatter is
    stripped before send.
• Safety/back‑compat: no changes to approvals/
  sandbox; protocol only adds optional fields; existing
  prompts continue to work.
• Tests/docs: unit + TUI snapshot tests added; docs/
  prompts.md updated.

If this approach aligns, I’ll mark #3565 ready for
review. I’m happy to modify as needed.