Allow a VS Code Codex prompt to declare the model and reasoning effort for that invocation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
VS Code extension (IDE extension)
What feature would you like to see?
I want a feature that allows me to select the model/effort as part of my VSC/Codex extension prompt, so that I can develop a prompt in Notepad and have a command that says: model=Sol, effort=high, and then the VSC/Codex extension selects that model/effort as commanded without having to first use the dialog box to select the same. This allows me to develop the prompt for the chat box, copy it into the chat box and have (like in the first two lines of the prompt) the model and effort that I want the prompt to run against.
Additional information
I'm working with ChatGPT for application development and Chat makes the prompt, I copy the prompt and then paste the prompt into VSC/Codex chat box, and then execute the prompt. BUT FIRST, as we are switching level of effort based upon prompt complexity (to save $$$$), I have to manually select the model/effort through the dialog box, and that is both a pain in the butt and takes time...help me OBEWAN.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the VS Code extension's chat box and existing model/effort selection dialog. Trace how a prompt invocation is handled, then define how leading model=Sol and effort=high directives should be recognized and applied, including what happens when either value is invalid; done means the pasted prompt selects those settings without the dialog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100