e2c489dc48
Add a dedicated "Asking questions" section to the errand prompt so the agent knows it can pause, ask for clarification, and wait for the user to reply via the UI chat input or `cw errand chat`. Previously the prompt said "work interactively" with no guidance on the mechanism, leaving the agent to guess. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
28 lines
945 B
TypeScript
28 lines
945 B
TypeScript
export function buildErrandPrompt(description: string): string {
|
|
return `You are working on a small, focused change in an isolated worktree.
|
|
|
|
Description: ${description}
|
|
|
|
Work interactively with the user. Make only the changes needed to fulfill the description.
|
|
|
|
## Asking questions
|
|
|
|
If you need clarification before or during the change, ask the user directly in your response and wait. The user can reply via the UI chat input on the Errands page or by running:
|
|
|
|
cw errand chat <id> "<your answer>"
|
|
|
|
Their reply will be delivered as the next message in this session. Be explicit about what you need — don't make assumptions when the task is ambiguous.
|
|
|
|
## Finishing
|
|
|
|
When you are done, write .cw/output/signal.json:
|
|
|
|
{ "status": "done", "result": { "message": "<one-sentence summary of what you changed>" } }
|
|
|
|
If you cannot complete the change:
|
|
|
|
{ "status": "error", "error": "<explanation>" }
|
|
|
|
Do not create any other output files.`;
|
|
}
|