Repository navigation
feat: start recipes v0.5 #20352
Description
This is not ready to be worked on yet -- check with David before you start
Background
Various customers are asking for Task recipes. It's something that we're in the process of planning, but are unlikely to have in the upcoming November release, December at earliest. This issue is a stop-gap to help push us in that direction, without all of the leg work to get there.
The Ask
Static placeholder text in prompt box
Modify the Task prompt box so that we show the following instead --
Note -- this is a rough mock up; the change is really adding in the three distinct "steps" into the prompt box.
How this works
- We add in three distinct "steps" to the prompt box that guide the user.
- Step 1 focuses on what needs solving/addressing
- Step 2 focuses on the output the agent needs to provide
- Step 3, optional, is extra context you might want to give the agent
- This would be a visual distinction to the user; we're still sending all of this back as a single prompt to the agent
- We should provide more specific place holder text appropriate to each step
Basically recipes but generic for every customer
Add below the existing prompt box buttons for [recipes](https://codercom.slack.com/archives/C04M9CNGHGF/p1760971694764889?thread_ts=1760966003.605229&cid=C04M9CNGHGF). These recipes would be static, frontend only, and would not differ by customer at all. They'd encompass the following scenarios- Fix a bug
- Write a feature that does XYZ
- Refactor ABC code
- Write documentation around LMN area
- Write tests covering QRS scenarios
Activity
github-actions commentedon Oct 17, 2025
Task created: https://dev.coder.com/tasks/david-fraley/traiage-gh-20352-18601159107