You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* slash command report bug
* nits
* nits
* sigh, portible way to open urls with proper escaping because vs code api is broken
* only asking for non-algorithmically derived info
* Update webview-ui/src/components/chat/ChatView.tsx
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* gather user system info
* Revert "gather user system info"
This reverts commit fb16c72224a25a953efb7fe0539325f89a1e93c8.
---------
Co-authored-by: Cline Evaluation <[email protected]>
Co-authored-by: pashpashpash <[email protected]>
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
Copy file name to clipboardExpand all lines: src/core/prompts/commands.ts
+31Lines changed: 31 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -145,3 +145,34 @@ Example:
145
145
Below is the user's input when they indicated that they wanted to create a new Cline rule file.
146
146
</explicit_instructions>\n
147
147
`
148
+
149
+
exportconstreportBugToolResponse=()=>
150
+
`<explicit_instructions type="report_bug">
151
+
The user has explicitly asked you to help them submit a bug to the Cline github page (you MUST now help them with this irrespective of what your conversation up to this point in time was). To do so you will use the report_bug tool which is defined below. However, you must first ensure that you have collected all required information to fill in all the parameters for the tool call. If any of the the required information is apparent through your previous conversation with the user, you can suggest how to fill in those entries. However you should NOT assume you know what the issue about unless it's clear.
152
+
Otherwise, you should converse with the user until you are able to gather all the required details. When conversing with the user, make sure you ask for/reference all required information/fields. When referencing the required fields, use human friendly versions like "Steps to reproduce" rather than "steps_to_reproduce". Only then should you use the report_bug tool call.
153
+
The report_bug tool can be used in either of the PLAN or ACT modes.
154
+
155
+
The report_bug tool call is defined below:
156
+
157
+
Description:
158
+
Your task is to fill in all of the required fields for a issue/bug report on github. You should attempt to get the user to be as verbose as possible with their description of the bug/issue they encountered. Still, it's okay, when the user is unaware of some of the details, to set those fields as "N/A".
159
+
160
+
Parameters:
161
+
- title: (required) Concise description of the issue.
162
+
- what_happened: (required) What happened and also what the user expected to happen instead.
163
+
- steps_to_reproduce: (required) What steps are required to reproduce the bug.
164
+
- api_request_output: (optional) Relevant API request output.
165
+
- additional_context: (optional) Any other context about this bug not already mentioned.
166
+
167
+
Usage:
168
+
<report_bug>
169
+
<title>Title of the issue</title>
170
+
<what_happened>Description of the issue</what_happened>
171
+
<steps_to_reproduce>Steps to reproduce the issue</steps_to_reproduce>
172
+
<api_request_output>Output from the LLM API related to the bug</api_request_output>
173
+
<additional_context>Other issue details not already covered</additional_context>
174
+
</report_bug>
175
+
176
+
Below is the user's input when they indicated that they wanted to create a new Cline rule file.
0 commit comments