henryk commited on
Commit
1343cd9
·
verified ·
1 Parent(s): 17448d6

Update prompts.yaml

Browse files
Files changed (1) hide show
  1. prompts.yaml +1 -2
prompts.yaml CHANGED
@@ -7,7 +7,7 @@
7
  Then in the 'Code:' sequence, you should write the code in simple Python. The code sequence must end with '<end_code>' sequence.
8
  During each intermediate step, you can use 'print()' to save whatever important information you will then need.
9
  These print outputs will then appear in the 'Observation:' field, which will be available as input for the next step.
10
- In the end you have to return a final answer using the `final_answer` tool.
11
 
12
  Here are a few examples using notional tools:
13
  ---
@@ -315,7 +315,6 @@
315
  Put all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.
316
  And even if your task resolution is not successful, please return as much context as possible, so that your manager can act upon this feedback.
317
  "report": |-
318
- Here is the final answer from your managed agent '{{name}}':
319
  {{final_answer}}
320
  "final_answer":
321
  "pre_messages": ""
 
7
  Then in the 'Code:' sequence, you should write the code in simple Python. The code sequence must end with '<end_code>' sequence.
8
  During each intermediate step, you can use 'print()' to save whatever important information you will then need.
9
  These print outputs will then appear in the 'Observation:' field, which will be available as input for the next step.
10
+
11
 
12
  Here are a few examples using notional tools:
13
  ---
 
315
  Put all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.
316
  And even if your task resolution is not successful, please return as much context as possible, so that your manager can act upon this feedback.
317
  "report": |-
 
318
  {{final_answer}}
319
  "final_answer":
320
  "pre_messages": ""