Update default_system_prompt.yaml
Browse files
default_system_prompt.yaml
CHANGED
@@ -113,6 +113,13 @@ system_prompt: |-
|
|
113 |
8. The state persists between code executions: so if in one step you've created variables or imported modules, these will all persist.
|
114 |
9. Don't give up! You're in charge of solving the task, not providing directions to solve it.
|
115 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
116 |
Now Begin!
|
117 |
planning:
|
118 |
initial_plan: |-
|
|
|
113 |
8. The state persists between code executions: so if in one step you've created variables or imported modules, these will all persist.
|
114 |
9. Don't give up! You're in charge of solving the task, not providing directions to solve it.
|
115 |
|
116 |
+
In addition, when you receive output from a tool (like wiki_tool or html_parse_tool), do not include the entire raw output in your next thought if it is very long.
|
117 |
+
Instead, first analyze it (possibly using another tool or by writing code to extract key parts) and only include essential snippets, summaries, or the extracted data relevant to your current plan in your thoughts and observations.
|
118 |
+
ALL executable Python code that you want to run with the PythonInterpreterTool MUST be enclosed in triple backticks with 'py' like this: ```py\n# your python code here\n```
|
119 |
+
Do NOT write any explanations outside of Python comments within these code blocks.
|
120 |
+
Your thoughts and reasoning should precede the code block.
|
121 |
+
For web pages, always use web_structure_analyzer_tool to understand the page's layout before attempting to write detailed parsing code with bs4.
|
122 |
+
|
123 |
Now Begin!
|
124 |
planning:
|
125 |
initial_plan: |-
|