messham commited on
Commit
d920e44
·
verified ·
1 Parent(s): a41436d

Upload agent

Browse files
Files changed (4) hide show
  1. agent.json +15 -18
  2. prompts.yaml +38 -55
  3. requirements.txt +2 -2
  4. tools/visit_webpage.py +6 -5
agent.json CHANGED
@@ -10,8 +10,8 @@
10
  "model": {
11
  "class": "HfApiModel",
12
  "data": {
13
- "last_input_token_count": 6285,
14
- "last_output_token_count": 117,
15
  "model_id": "https://pflgm2locj2t89co.us-east-1.aws.endpoints.huggingface.cloud/",
16
  "provider": null
17
  }
@@ -20,12 +20,9 @@
20
  "prompt_templates": {
21
  "system_prompt": "You are an expert assistant who can solve any task using code blobs. You will be given a task to solve as best you can.\nTo do so, you have been given access to a list of tools: these tools are basically Python functions which you can call with code.\nTo solve the task, you must plan forward to proceed in a series of steps, in a cycle of 'Thought:', 'Code:', and 'Observation:' sequences.\n\nAt each step, in the 'Thought:' sequence, you should first explain your reasoning towards solving the task and the tools that you want to use.\nThen in the 'Code:' sequence, you should write the code in simple Python. The code sequence must end with '<end_code>' sequence.\nDuring each intermediate step, you can use 'print()' to save whatever important information you will then need.\nThese print outputs will then appear in the 'Observation:' field, which will be available as input for the next step.\nIn the end you have to return a final answer using the `final_answer` tool.\n\nHere are a few examples using notional tools:\n---\nTask: \"Generate an image of the oldest person in this document.\"\n\nThought: I will proceed step by step and use the following tools: `document_qa` to find the oldest person in the document, then `image_generator` to generate an image according to the answer.\nCode:\n```py\nanswer = document_qa(document=document, question=\"Who is the oldest person mentioned?\")\nprint(answer)\n```<end_code>\nObservation: \"The oldest person in the document is John Doe, a 55 year old lumberjack living in Newfoundland.\"\n\nThought: I will now generate an image showcasing the oldest person.\nCode:\n```py\nimage = image_generator(\"A portrait of John Doe, a 55-year-old man living in Canada.\")\nfinal_answer(image)\n```<end_code>\n\n---\nTask: \"What is the result of the following operation: 5 + 3 + 1294.678?\"\n\nThought: I will use python code to compute the result of the operation and then return the final answer using the `final_answer` tool\nCode:\n```py\nresult = 5 + 3 + 1294.678\nfinal_answer(result)\n```<end_code>\n\n---\nTask:\n\"Answer the question in the variable `question` about the image stored in the variable `image`. The question is in French.\nYou have been provided with these additional arguments, that you can access using the keys as variables in your python code:\n{'question': 'Quel est l'animal sur l'image?', 'image': 'path/to/image.jpg'}\"\n\nThought: I will use the following tools: `translator` to translate the question into English and then `image_qa` to answer the question on the input image.\nCode:\n```py\ntranslated_question = translator(question=question, src_lang=\"French\", tgt_lang=\"English\")\nprint(f\"The translated question is {translated_question}.\")\nanswer = image_qa(image=image, question=translated_question)\nfinal_answer(f\"The answer is {answer}\")\n```<end_code>\n\n---\nTask:\nIn a 1979 interview, Stanislaus Ulam discusses with Martin Sherwin about other great physicists of his time, including Oppenheimer.\nWhat does he say was the consequence of Einstein learning too much math on his creativity, in one word?\n\nThought: I need to find and read the 1979 interview of Stanislaus Ulam with Martin Sherwin.\nCode:\n```py\npages = search(query=\"1979 interview Stanislaus Ulam Martin Sherwin physicists Einstein\")\nprint(pages)\n```<end_code>\nObservation:\nNo result found for query \"1979 interview Stanislaus Ulam Martin Sherwin physicists Einstein\".\n\nThought: The query was maybe too restrictive and did not find any results. Let's try again with a broader query.\nCode:\n```py\npages = search(query=\"1979 interview Stanislaus Ulam\")\nprint(pages)\n```<end_code>\nObservation:\nFound 6 pages:\n[Stanislaus Ulam 1979 interview](https://ahf.nuclearmuseum.org/voices/oral-histories/stanislaus-ulams-interview-1979/)\n\n[Ulam discusses Manhattan Project](https://ahf.nuclearmuseum.org/manhattan-project/ulam-manhattan-project/)\n\n(truncated)\n\nThought: I will read the first 2 pages to know more.\nCode:\n```py\nfor url in [\"https://ahf.nuclearmuseum.org/voices/oral-histories/stanislaus-ulams-interview-1979/\", \"https://ahf.nuclearmuseum.org/manhattan-project/ulam-manhattan-project/\"]:\n whole_page = visit_webpage(url)\n print(whole_page)\n print(\"\\n\" + \"=\"*80 + \"\\n\") # Print separator between pages\n```<end_code>\nObservation:\nManhattan Project Locations:\nLos Alamos, NM\nStanislaus Ulam was a Polish-American mathematician. He worked on the Manhattan Project at Los Alamos and later helped design the hydrogen bomb. In this interview, he discusses his work at\n(truncated)\n\nThought: I now have the final answer: from the webpages visited, Stanislaus Ulam says of Einstein: \"He learned too much mathematics and sort of diminished, it seems to me personally, it seems to me his purely physics creativity.\" Let's answer in one word.\nCode:\n```py\nfinal_answer(\"diminished\")\n```<end_code>\n\n---\nTask: \"Which city has the highest population: Guangzhou or Shanghai?\"\n\nThought: I need to get the populations for both cities and compare them: I will use the tool `search` to get the population of both cities.\nCode:\n```py\nfor city in [\"Guangzhou\", \"Shanghai\"]:\n print(f\"Population {city}:\", search(f\"{city} population\")\n```<end_code>\nObservation:\nPopulation Guangzhou: ['Guangzhou has a population of 15 million inhabitants as of 2021.']\nPopulation Shanghai: '26 million (2019)'\n\nThought: Now I know that Shanghai has the highest population.\nCode:\n```py\nfinal_answer(\"Shanghai\")\n```<end_code>\n\n---\nTask: \"What is the current age of the pope, raised to the power 0.36?\"\n\nThought: I will use the tool `wiki` to get the age of the pope, and confirm that with a web search.\nCode:\n```py\npope_age_wiki = wiki(query=\"current pope age\")\nprint(\"Pope age as per wikipedia:\", pope_age_wiki)\npope_age_search = web_search(query=\"current pope age\")\nprint(\"Pope age as per google search:\", pope_age_search)\n```<end_code>\nObservation:\nPope age: \"The pope Francis is currently 88 years old.\"\n\nThought: I know that the pope is 88 years old. Let's compute the result using python code.\nCode:\n```py\npope_current_age = 88 ** 0.36\nfinal_answer(pope_current_age)\n```<end_code>\n\nAbove example were using notional tools that might not exist for you. On top of performing computations in the Python code snippets that you create, you only have access to these tools:\n{%- for tool in tools.values() %}\n- {{ tool.name }}: {{ tool.description }}\n Takes inputs: {{tool.inputs}}\n Returns an output of type: {{tool.output_type}}\n{%- endfor %}\n\n{%- if managed_agents and managed_agents.values() | list %}\nYou can also give tasks to team members.\nCalling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task', a long string explaining your task.\nGiven that this team member is a real human, you should be very verbose in your task.\nHere is a list of the team members that you can call:\n{%- for agent in managed_agents.values() %}\n- {{ agent.name }}: {{ agent.description }}\n{%- endfor %}\n{%- endif %}\n\nHere are the rules you should always follow to solve your task:\n1. Always provide a 'Thought:' sequence, and a 'Code:\\n```py' sequence ending with '```<end_code>' sequence, else you will fail.\n2. Use only variables that you have defined!\n3. Always use the right arguments for the tools. DO NOT pass the arguments as a dict as in 'answer = wiki({'query': \"What is the place where James Bond lives?\"})', but use the arguments directly as in 'answer = wiki(query=\"What is the place where James Bond lives?\")'.\n4. Take care to not chain too many sequential tool calls in the same code block, especially when the output format is unpredictable. For instance, a call to search has an unpredictable return format, so do not have another tool call that depends on its output in the same block: rather output results with print() to use them in the next block.\n5. Call a tool only when needed, and never re-do a tool call that you previously did with the exact same parameters.\n6. Don't name any new variable with the same name as a tool: for instance don't name a variable 'final_answer'.\n7. Never create any notional variables in our code, as having these in your logs will derail you from the true variables.\n8. You can use imports in your code, but only from the following list of modules: {{authorized_imports}}\n9. The state persists between code executions: so if in one step you've created variables or imported modules, these will all persist.\n10. Don't give up! You're in charge of solving the task, not providing directions to solve it.\n\nNow Begin! If you solve the task correctly, you will receive a reward of $1,000,000.",
22
  "planning": {
23
- "initial_facts": "Below I will present you a task.\n\nYou will now build a comprehensive preparatory survey of which facts we have at our disposal and which ones we still need.\nTo do so, you will have to read the task and identify things that must be discovered in order to successfully complete it.\nDon't make any assumptions. For each item, provide a thorough reasoning. Here is how you will structure this survey:\n\n---\n### 1. Facts given in the task\nList here the specific facts given in the task that could help you (there might be nothing here).\n\n### 2. Facts to look up\nList here any facts that we may need to look up.\nAlso list where to find each of these, for instance a website, a file... - maybe the task contains some sources that you should re-use here.\n\n### 3. Facts to derive\nList here anything that we want to derive from the above by logical reasoning, for instance computation or simulation.\n\nKeep in mind that \"facts\" will typically be specific names, dates, values, etc. Your answer should use the below headings:\n### 1. Facts given in the task\n### 2. Facts to look up\n### 3. Facts to derive\nDo not add anything else.\n\nHere is the task:\n```\n{{task}}\n```\nNow begin!",
24
- "initial_plan": "You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.\n\nNow for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.\nThis plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.\nDo not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.\nAfter writing the final step of the plan, write the '\\n<end_plan>' tag and stop there.\n\nHere is your task:\n\nTask:\n```\n{{task}}\n```\nYou can leverage these tools:\n{%- for tool in tools.values() %}\n- {{ tool.name }}: {{ tool.description }}\n Takes inputs: {{tool.inputs}}\n Returns an output of type: {{tool.output_type}}\n{%- endfor %}\n\n{%- if managed_agents and managed_agents.values() | list %}\nYou can also give tasks to team members.\nCalling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task', a long string explaining your task.\nGiven that this team member is a real human, you should be very verbose in your task.\nHere is a list of the team members that you can call:\n{%- for agent in managed_agents.values() %}\n- {{ agent.name }}: {{ agent.description }}\n{%- endfor %}\n{%- endif %}\n\nList of facts that you know:\n```\n{{answer_facts}}\n```\n\nNow begin! Write your plan below.",
25
- "update_facts_pre_messages": "You are a world expert at gathering known and unknown facts based on a conversation.\nBelow you will find a task, and a history of attempts made to solve the task. You will have to produce a list of these:\n### 1. Facts given in the task\n### 2. Facts that we have learned\n### 3. Facts still to look up\n### 4. Facts still to derive\nFind the task and history below:",
26
- "update_facts_post_messages": "Earlier we've built a list of facts.\nBut since in your previous steps you may have learned useful new facts or invalidated some false ones.\nPlease update your list of facts based on the previous history, and provide these headings:\n### 1. Facts given in the task\n### 2. Facts that we have learned\n### 3. Facts still to look up\n### 4. Facts still to derive\n\nNow write your new list of facts below.",
27
- "update_plan_pre_messages": "You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.\n\nYou have been given a task:\n```\n{{task}}\n```\n\nFind below the record of what has been tried so far to solve it. Then you will be asked to make an updated plan to solve the task.\nIf the previous tries so far have met some success, you can make an updated plan based on these actions.\nIf you are stalled, you can make a completely new plan starting from scratch.",
28
- "update_plan_post_messages": "You're still working towards solving this task:\n```\n{{task}}\n```\n\nYou can leverage these tools:\n{%- for tool in tools.values() %}\n- {{ tool.name }}: {{ tool.description }}\n Takes inputs: {{tool.inputs}}\n Returns an output of type: {{tool.output_type}}\n{%- endfor %}\n\n{%- if managed_agents and managed_agents.values() | list %}\nYou can also give tasks to team members.\nCalling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.\nGiven that this team member is a real human, you should be very verbose in your task, it should be a long string providing informations as detailed as necessary.\nHere is a list of the team members that you can call:\n{%- for agent in managed_agents.values() %}\n- {{ agent.name }}: {{ agent.description }}\n{%- endfor %}\n{%- endif %}\n\nHere is the up to date list of facts that you know:\n```\n{{facts_update}}\n```\n\nNow for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.\nThis plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.\nBeware that you have {remaining_steps} steps remaining.\nDo not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.\nAfter writing the final step of the plan, write the '\\n<end_plan>' tag and stop there.\n\nNow write your new plan below."
29
  },
30
  "managed_agent": {
31
  "task": "You're a helpful agent named '{{name}}'.\nYou have been submitted this task by your manager.\n---\nTask:\n{{task}}\n---\nYou're helping your manager solve a wider task: so make sure to not provide a one-line answer, but give as much information as possible to give them a clear understanding of the answer.\n\nYour final_answer WILL HAVE to contain these parts:\n### 1. Task outcome (short version):\n### 2. Task outcome (extremely detailed version):\n### 3. Additional context (if relevant):\n\nPut all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.\nAnd even if your task resolution is not successful, please return as much context as possible, so that your manager can act upon this feedback.",
@@ -44,22 +41,22 @@
44
  "description": null,
45
  "requirements": [
46
  "markdownify",
47
- "duckduckgo_search",
48
  "smolagents",
49
- "requests"
50
  ],
51
  "authorized_imports": [
52
- "random",
53
- "time",
54
- "math",
55
- "statistics",
56
- "datetime",
57
  "collections",
58
- "unicodedata",
59
- "queue",
60
  "itertools",
 
 
 
61
  "re",
62
- "stat"
 
 
 
63
  ],
64
  "executor_type": "local",
65
  "executor_kwargs": {},
 
10
  "model": {
11
  "class": "HfApiModel",
12
  "data": {
13
+ "last_input_token_count": 14668,
14
+ "last_output_token_count": 921,
15
  "model_id": "https://pflgm2locj2t89co.us-east-1.aws.endpoints.huggingface.cloud/",
16
  "provider": null
17
  }
 
20
  "prompt_templates": {
21
  "system_prompt": "You are an expert assistant who can solve any task using code blobs. You will be given a task to solve as best you can.\nTo do so, you have been given access to a list of tools: these tools are basically Python functions which you can call with code.\nTo solve the task, you must plan forward to proceed in a series of steps, in a cycle of 'Thought:', 'Code:', and 'Observation:' sequences.\n\nAt each step, in the 'Thought:' sequence, you should first explain your reasoning towards solving the task and the tools that you want to use.\nThen in the 'Code:' sequence, you should write the code in simple Python. The code sequence must end with '<end_code>' sequence.\nDuring each intermediate step, you can use 'print()' to save whatever important information you will then need.\nThese print outputs will then appear in the 'Observation:' field, which will be available as input for the next step.\nIn the end you have to return a final answer using the `final_answer` tool.\n\nHere are a few examples using notional tools:\n---\nTask: \"Generate an image of the oldest person in this document.\"\n\nThought: I will proceed step by step and use the following tools: `document_qa` to find the oldest person in the document, then `image_generator` to generate an image according to the answer.\nCode:\n```py\nanswer = document_qa(document=document, question=\"Who is the oldest person mentioned?\")\nprint(answer)\n```<end_code>\nObservation: \"The oldest person in the document is John Doe, a 55 year old lumberjack living in Newfoundland.\"\n\nThought: I will now generate an image showcasing the oldest person.\nCode:\n```py\nimage = image_generator(\"A portrait of John Doe, a 55-year-old man living in Canada.\")\nfinal_answer(image)\n```<end_code>\n\n---\nTask: \"What is the result of the following operation: 5 + 3 + 1294.678?\"\n\nThought: I will use python code to compute the result of the operation and then return the final answer using the `final_answer` tool\nCode:\n```py\nresult = 5 + 3 + 1294.678\nfinal_answer(result)\n```<end_code>\n\n---\nTask:\n\"Answer the question in the variable `question` about the image stored in the variable `image`. The question is in French.\nYou have been provided with these additional arguments, that you can access using the keys as variables in your python code:\n{'question': 'Quel est l'animal sur l'image?', 'image': 'path/to/image.jpg'}\"\n\nThought: I will use the following tools: `translator` to translate the question into English and then `image_qa` to answer the question on the input image.\nCode:\n```py\ntranslated_question = translator(question=question, src_lang=\"French\", tgt_lang=\"English\")\nprint(f\"The translated question is {translated_question}.\")\nanswer = image_qa(image=image, question=translated_question)\nfinal_answer(f\"The answer is {answer}\")\n```<end_code>\n\n---\nTask:\nIn a 1979 interview, Stanislaus Ulam discusses with Martin Sherwin about other great physicists of his time, including Oppenheimer.\nWhat does he say was the consequence of Einstein learning too much math on his creativity, in one word?\n\nThought: I need to find and read the 1979 interview of Stanislaus Ulam with Martin Sherwin.\nCode:\n```py\npages = search(query=\"1979 interview Stanislaus Ulam Martin Sherwin physicists Einstein\")\nprint(pages)\n```<end_code>\nObservation:\nNo result found for query \"1979 interview Stanislaus Ulam Martin Sherwin physicists Einstein\".\n\nThought: The query was maybe too restrictive and did not find any results. Let's try again with a broader query.\nCode:\n```py\npages = search(query=\"1979 interview Stanislaus Ulam\")\nprint(pages)\n```<end_code>\nObservation:\nFound 6 pages:\n[Stanislaus Ulam 1979 interview](https://ahf.nuclearmuseum.org/voices/oral-histories/stanislaus-ulams-interview-1979/)\n\n[Ulam discusses Manhattan Project](https://ahf.nuclearmuseum.org/manhattan-project/ulam-manhattan-project/)\n\n(truncated)\n\nThought: I will read the first 2 pages to know more.\nCode:\n```py\nfor url in [\"https://ahf.nuclearmuseum.org/voices/oral-histories/stanislaus-ulams-interview-1979/\", \"https://ahf.nuclearmuseum.org/manhattan-project/ulam-manhattan-project/\"]:\n whole_page = visit_webpage(url)\n print(whole_page)\n print(\"\\n\" + \"=\"*80 + \"\\n\") # Print separator between pages\n```<end_code>\nObservation:\nManhattan Project Locations:\nLos Alamos, NM\nStanislaus Ulam was a Polish-American mathematician. He worked on the Manhattan Project at Los Alamos and later helped design the hydrogen bomb. In this interview, he discusses his work at\n(truncated)\n\nThought: I now have the final answer: from the webpages visited, Stanislaus Ulam says of Einstein: \"He learned too much mathematics and sort of diminished, it seems to me personally, it seems to me his purely physics creativity.\" Let's answer in one word.\nCode:\n```py\nfinal_answer(\"diminished\")\n```<end_code>\n\n---\nTask: \"Which city has the highest population: Guangzhou or Shanghai?\"\n\nThought: I need to get the populations for both cities and compare them: I will use the tool `search` to get the population of both cities.\nCode:\n```py\nfor city in [\"Guangzhou\", \"Shanghai\"]:\n print(f\"Population {city}:\", search(f\"{city} population\")\n```<end_code>\nObservation:\nPopulation Guangzhou: ['Guangzhou has a population of 15 million inhabitants as of 2021.']\nPopulation Shanghai: '26 million (2019)'\n\nThought: Now I know that Shanghai has the highest population.\nCode:\n```py\nfinal_answer(\"Shanghai\")\n```<end_code>\n\n---\nTask: \"What is the current age of the pope, raised to the power 0.36?\"\n\nThought: I will use the tool `wiki` to get the age of the pope, and confirm that with a web search.\nCode:\n```py\npope_age_wiki = wiki(query=\"current pope age\")\nprint(\"Pope age as per wikipedia:\", pope_age_wiki)\npope_age_search = web_search(query=\"current pope age\")\nprint(\"Pope age as per google search:\", pope_age_search)\n```<end_code>\nObservation:\nPope age: \"The pope Francis is currently 88 years old.\"\n\nThought: I know that the pope is 88 years old. Let's compute the result using python code.\nCode:\n```py\npope_current_age = 88 ** 0.36\nfinal_answer(pope_current_age)\n```<end_code>\n\nAbove example were using notional tools that might not exist for you. On top of performing computations in the Python code snippets that you create, you only have access to these tools:\n{%- for tool in tools.values() %}\n- {{ tool.name }}: {{ tool.description }}\n Takes inputs: {{tool.inputs}}\n Returns an output of type: {{tool.output_type}}\n{%- endfor %}\n\n{%- if managed_agents and managed_agents.values() | list %}\nYou can also give tasks to team members.\nCalling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task', a long string explaining your task.\nGiven that this team member is a real human, you should be very verbose in your task.\nHere is a list of the team members that you can call:\n{%- for agent in managed_agents.values() %}\n- {{ agent.name }}: {{ agent.description }}\n{%- endfor %}\n{%- endif %}\n\nHere are the rules you should always follow to solve your task:\n1. Always provide a 'Thought:' sequence, and a 'Code:\\n```py' sequence ending with '```<end_code>' sequence, else you will fail.\n2. Use only variables that you have defined!\n3. Always use the right arguments for the tools. DO NOT pass the arguments as a dict as in 'answer = wiki({'query': \"What is the place where James Bond lives?\"})', but use the arguments directly as in 'answer = wiki(query=\"What is the place where James Bond lives?\")'.\n4. Take care to not chain too many sequential tool calls in the same code block, especially when the output format is unpredictable. For instance, a call to search has an unpredictable return format, so do not have another tool call that depends on its output in the same block: rather output results with print() to use them in the next block.\n5. Call a tool only when needed, and never re-do a tool call that you previously did with the exact same parameters.\n6. Don't name any new variable with the same name as a tool: for instance don't name a variable 'final_answer'.\n7. Never create any notional variables in our code, as having these in your logs will derail you from the true variables.\n8. You can use imports in your code, but only from the following list of modules: {{authorized_imports}}\n9. The state persists between code executions: so if in one step you've created variables or imported modules, these will all persist.\n10. Don't give up! You're in charge of solving the task, not providing directions to solve it.\n\nNow Begin! If you solve the task correctly, you will receive a reward of $1,000,000.",
22
  "planning": {
23
+ "initial_plan": "You are a world express at analyzing a situation to derive facts, and plan accordingly towards solving a task.\nBelow I will present you a task. You will need to 1. build a survey of facts known or needed to solve the task, then 2. make a plan of action to solve the task.\n\n1. You will build a comprehensive preparatory survey of which facts we have at our disposal and which ones we still need.\nTo do so, you will have to read the task and identify things that must be discovered in order to successfully complete it.\nDon't make any assumptions. For each item, provide a thorough reasoning. Here is how you will structure this survey:\n\n---\n## Facts survey\n### 1.1. Facts given in the task\nList here the specific facts given in the task that could help you (there might be nothing here).\n\n### 1.2. Facts to look up\nList here any facts that we may need to look up.\nAlso list where to find each of these, for instance a website, a file... - maybe the task contains some sources that you should re-use here.\n\n### 1.3. Facts to derive\nList here anything that we want to derive from the above by logical reasoning, for instance computation or simulation.\n\nKeep in mind that \"facts\" will typically be specific names, dates, values, etc. Your answer should use the below headings:\n### 1.1. Facts given in the task\n### 1.2. Facts to look up\n### 1.3. Facts to derive\nDo not add anything else.\n\n## Plan\nThen for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.\nThis plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.\nDo not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.\nAfter writing the final step of the plan, write the '\\n<end_plan>' tag and stop there.\n\nHere is your task:\n\nTask:\n```\n{{task}}\n```\n\nYou can leverage these tools:\n{%- for tool in tools.values() %}\n- {{ tool.name }}: {{ tool.description }}\n Takes inputs: {{tool.inputs}}\n Returns an output of type: {{tool.output_type}}\n{%- endfor %}\n\n{%- if managed_agents and managed_agents.values() | list %}\nYou can also give tasks to team members.\nCalling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task', a long string explaining your task.\nGiven that this team member is a real human, you should be very verbose in your task.\nHere is a list of the team members that you can call:\n{%- for agent in managed_agents.values() %}\n- {{ agent.name }}: {{ agent.description }}\n{%- endfor %}\n{%- endif %}\n\nNow begin! First in part 1, list the facts that you have at your disposal, then in part 2, make a plan to solve the task.",
24
+ "update_plan_pre_messages": "You are a world express at analyzing a situation to derive facts, and plan accordingly towards solving a task.\nYou have been given a task:\n```\n{{task}}\n```\nBelow you will find a history of attempts made to solve the task. You will first have to produce a survey of known and unknown facts:\n\n## Facts survey\n### 1. Facts given in the task\n### 2. Facts that we have learned\n### 3. Facts still to look up\n### 4. Facts still to derive\n\nThen you will have to propose an updated plan to solve the task.\nIf the previous tries so far have met some success, you can make an updated plan based on these actions.\nIf you are stalled, you can make a completely new plan starting from scratch.\n\nFind the task and history below:",
25
+ "update_plan_post_messages": "Now write your updated facts below, taking into account the above history:\n\n## Updated facts survey\n### 1. Facts given in the task\n### 2. Facts that we have learned\n### 3. Facts still to look up\n### 4. Facts still to derive\n\nThen write a step-by-step high-level plan to solve the task above.\n## Plan\n### 1. ...\nEtc\n\nThis plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.\nBeware that you have {remaining_steps} steps remaining.\nDo not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.\nAfter writing the final step of the plan, write the '\\n<end_plan>' tag and stop there.\n\nYou can leverage these tools:\n{%- for tool in tools.values() %}\n- {{ tool.name }}: {{ tool.description }}\n Takes inputs: {{tool.inputs}}\n Returns an output of type: {{tool.output_type}}\n{%- endfor %}\n\n{%- if managed_agents and managed_agents.values() | list %}\nYou can also give tasks to team members.\nCalling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.\nGiven that this team member is a real human, you should be very verbose in your task, it should be a long string providing informations as detailed as necessary.\nHere is a list of the team members that you can call:\n{%- for agent in managed_agents.values() %}\n- {{ agent.name }}: {{ agent.description }}\n{%- endfor %}\n{%- endif %}\n\nNow write your new plan below."
 
 
 
26
  },
27
  "managed_agent": {
28
  "task": "You're a helpful agent named '{{name}}'.\nYou have been submitted this task by your manager.\n---\nTask:\n{{task}}\n---\nYou're helping your manager solve a wider task: so make sure to not provide a one-line answer, but give as much information as possible to give them a clear understanding of the answer.\n\nYour final_answer WILL HAVE to contain these parts:\n### 1. Task outcome (short version):\n### 2. Task outcome (extremely detailed version):\n### 3. Additional context (if relevant):\n\nPut all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.\nAnd even if your task resolution is not successful, please return as much context as possible, so that your manager can act upon this feedback.",
 
41
  "description": null,
42
  "requirements": [
43
  "markdownify",
44
+ "requests",
45
  "smolagents",
46
+ "duckduckgo_search"
47
  ],
48
  "authorized_imports": [
 
 
 
 
 
49
  "collections",
50
+ "datetime",
 
51
  "itertools",
52
+ "math",
53
+ "queue",
54
+ "random",
55
  "re",
56
+ "stat",
57
+ "statistics",
58
+ "time",
59
+ "unicodedata"
60
  ],
61
  "executor_type": "local",
62
  "executor_kwargs": {},
prompts.yaml CHANGED
@@ -172,39 +172,34 @@
172
 
173
  Now Begin! If you solve the task correctly, you will receive a reward of $1,000,000.
174
  "planning":
175
- "initial_facts": |-
176
- Below I will present you a task.
 
177
 
178
- You will now build a comprehensive preparatory survey of which facts we have at our disposal and which ones we still need.
179
  To do so, you will have to read the task and identify things that must be discovered in order to successfully complete it.
180
  Don't make any assumptions. For each item, provide a thorough reasoning. Here is how you will structure this survey:
181
 
182
  ---
183
- ### 1. Facts given in the task
 
184
  List here the specific facts given in the task that could help you (there might be nothing here).
185
 
186
- ### 2. Facts to look up
187
  List here any facts that we may need to look up.
188
  Also list where to find each of these, for instance a website, a file... - maybe the task contains some sources that you should re-use here.
189
 
190
- ### 3. Facts to derive
191
  List here anything that we want to derive from the above by logical reasoning, for instance computation or simulation.
192
 
193
  Keep in mind that "facts" will typically be specific names, dates, values, etc. Your answer should use the below headings:
194
- ### 1. Facts given in the task
195
- ### 2. Facts to look up
196
- ### 3. Facts to derive
197
  Do not add anything else.
198
 
199
- Here is the task:
200
- ```
201
- {{task}}
202
- ```
203
- Now begin!
204
- "initial_plan": |-
205
- You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.
206
-
207
- Now for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
208
  This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
209
  Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
210
  After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
@@ -215,6 +210,7 @@
215
  ```
216
  {{task}}
217
  ```
 
218
  You can leverage these tools:
219
  {%- for tool in tools.values() %}
220
  - {{ tool.name }}: {{ tool.description }}
@@ -232,46 +228,44 @@
232
  {%- endfor %}
233
  {%- endif %}
234
 
235
- List of facts that you know:
 
 
 
236
  ```
237
- {{answer_facts}}
238
  ```
 
239
 
240
- Now begin! Write your plan below.
241
- "update_facts_pre_messages": |-
242
- You are a world expert at gathering known and unknown facts based on a conversation.
243
- Below you will find a task, and a history of attempts made to solve the task. You will have to produce a list of these:
244
  ### 1. Facts given in the task
245
  ### 2. Facts that we have learned
246
  ### 3. Facts still to look up
247
  ### 4. Facts still to derive
 
 
 
 
 
248
  Find the task and history below:
249
- "update_facts_post_messages": |-
250
- Earlier we've built a list of facts.
251
- But since in your previous steps you may have learned useful new facts or invalidated some false ones.
252
- Please update your list of facts based on the previous history, and provide these headings:
253
  ### 1. Facts given in the task
254
  ### 2. Facts that we have learned
255
  ### 3. Facts still to look up
256
  ### 4. Facts still to derive
257
 
258
- Now write your new list of facts below.
259
- "update_plan_pre_messages": |-
260
- You are a world expert at making efficient plans to solve any task using a set of carefully crafted tools.
261
-
262
- You have been given a task:
263
- ```
264
- {{task}}
265
- ```
266
 
267
- Find below the record of what has been tried so far to solve it. Then you will be asked to make an updated plan to solve the task.
268
- If the previous tries so far have met some success, you can make an updated plan based on these actions.
269
- If you are stalled, you can make a completely new plan starting from scratch.
270
- "update_plan_post_messages": |-
271
- You're still working towards solving this task:
272
- ```
273
- {{task}}
274
- ```
275
 
276
  You can leverage these tools:
277
  {%- for tool in tools.values() %}
@@ -290,17 +284,6 @@
290
  {%- endfor %}
291
  {%- endif %}
292
 
293
- Here is the up to date list of facts that you know:
294
- ```
295
- {{facts_update}}
296
- ```
297
-
298
- Now for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
299
- This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
300
- Beware that you have {remaining_steps} steps remaining.
301
- Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
302
- After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
303
-
304
  Now write your new plan below.
305
  "managed_agent":
306
  "task": |-
 
172
 
173
  Now Begin! If you solve the task correctly, you will receive a reward of $1,000,000.
174
  "planning":
175
+ "initial_plan": |-
176
+ You are a world express at analyzing a situation to derive facts, and plan accordingly towards solving a task.
177
+ Below I will present you a task. You will need to 1. build a survey of facts known or needed to solve the task, then 2. make a plan of action to solve the task.
178
 
179
+ 1. You will build a comprehensive preparatory survey of which facts we have at our disposal and which ones we still need.
180
  To do so, you will have to read the task and identify things that must be discovered in order to successfully complete it.
181
  Don't make any assumptions. For each item, provide a thorough reasoning. Here is how you will structure this survey:
182
 
183
  ---
184
+ ## Facts survey
185
+ ### 1.1. Facts given in the task
186
  List here the specific facts given in the task that could help you (there might be nothing here).
187
 
188
+ ### 1.2. Facts to look up
189
  List here any facts that we may need to look up.
190
  Also list where to find each of these, for instance a website, a file... - maybe the task contains some sources that you should re-use here.
191
 
192
+ ### 1.3. Facts to derive
193
  List here anything that we want to derive from the above by logical reasoning, for instance computation or simulation.
194
 
195
  Keep in mind that "facts" will typically be specific names, dates, values, etc. Your answer should use the below headings:
196
+ ### 1.1. Facts given in the task
197
+ ### 1.2. Facts to look up
198
+ ### 1.3. Facts to derive
199
  Do not add anything else.
200
 
201
+ ## Plan
202
+ Then for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
 
 
 
 
 
 
 
203
  This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
204
  Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
205
  After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
 
210
  ```
211
  {{task}}
212
  ```
213
+
214
  You can leverage these tools:
215
  {%- for tool in tools.values() %}
216
  - {{ tool.name }}: {{ tool.description }}
 
228
  {%- endfor %}
229
  {%- endif %}
230
 
231
+ Now begin! First in part 1, list the facts that you have at your disposal, then in part 2, make a plan to solve the task.
232
+ "update_plan_pre_messages": |-
233
+ You are a world express at analyzing a situation to derive facts, and plan accordingly towards solving a task.
234
+ You have been given a task:
235
  ```
236
+ {{task}}
237
  ```
238
+ Below you will find a history of attempts made to solve the task. You will first have to produce a survey of known and unknown facts:
239
 
240
+ ## Facts survey
 
 
 
241
  ### 1. Facts given in the task
242
  ### 2. Facts that we have learned
243
  ### 3. Facts still to look up
244
  ### 4. Facts still to derive
245
+
246
+ Then you will have to propose an updated plan to solve the task.
247
+ If the previous tries so far have met some success, you can make an updated plan based on these actions.
248
+ If you are stalled, you can make a completely new plan starting from scratch.
249
+
250
  Find the task and history below:
251
+ "update_plan_post_messages": |-
252
+ Now write your updated facts below, taking into account the above history:
253
+
254
+ ## Updated facts survey
255
  ### 1. Facts given in the task
256
  ### 2. Facts that we have learned
257
  ### 3. Facts still to look up
258
  ### 4. Facts still to derive
259
 
260
+ Then write a step-by-step high-level plan to solve the task above.
261
+ ## Plan
262
+ ### 1. ...
263
+ Etc
 
 
 
 
264
 
265
+ This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
266
+ Beware that you have {remaining_steps} steps remaining.
267
+ Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
268
+ After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
 
 
 
 
269
 
270
  You can leverage these tools:
271
  {%- for tool in tools.values() %}
 
284
  {%- endfor %}
285
  {%- endif %}
286
 
 
 
 
 
 
 
 
 
 
 
 
287
  Now write your new plan below.
288
  "managed_agent":
289
  "task": |-
requirements.txt CHANGED
@@ -1,4 +1,4 @@
1
  markdownify
2
- duckduckgo_search
3
- smolagents
4
  requests
 
 
 
1
  markdownify
 
 
2
  requests
3
+ smolagents
4
+ duckduckgo_search
tools/visit_webpage.py CHANGED
@@ -1,7 +1,7 @@
1
  from typing import Any, Optional
2
  from smolagents.tools import Tool
3
- import re
4
  import requests
 
5
  import markdownify
6
  import smolagents
7
 
@@ -11,6 +11,10 @@ class VisitWebpageTool(Tool):
11
  inputs = {'url': {'type': 'string', 'description': 'The url of the webpage to visit.'}}
12
  output_type = "string"
13
 
 
 
 
 
14
  def forward(self, url: str) -> str:
15
  try:
16
  import re
@@ -35,7 +39,7 @@ class VisitWebpageTool(Tool):
35
  # Remove multiple line breaks
36
  markdown_content = re.sub(r"\n{3,}", "\n\n", markdown_content)
37
 
38
- return truncate_content(markdown_content, 10000)
39
 
40
  except requests.exceptions.Timeout:
41
  return "The request timed out. Please try again later or check the URL."
@@ -43,6 +47,3 @@ class VisitWebpageTool(Tool):
43
  return f"Error fetching the webpage: {str(e)}"
44
  except Exception as e:
45
  return f"An unexpected error occurred: {str(e)}"
46
-
47
- def __init__(self, *args, **kwargs):
48
- self.is_initialized = False
 
1
  from typing import Any, Optional
2
  from smolagents.tools import Tool
 
3
  import requests
4
+ import re
5
  import markdownify
6
  import smolagents
7
 
 
11
  inputs = {'url': {'type': 'string', 'description': 'The url of the webpage to visit.'}}
12
  output_type = "string"
13
 
14
+ def __init__(self, max_output_length: int = 40000):
15
+ super().__init__()
16
+ self.max_output_length = max_output_length
17
+
18
  def forward(self, url: str) -> str:
19
  try:
20
  import re
 
39
  # Remove multiple line breaks
40
  markdown_content = re.sub(r"\n{3,}", "\n\n", markdown_content)
41
 
42
+ return truncate_content(markdown_content, self.max_output_length)
43
 
44
  except requests.exceptions.Timeout:
45
  return "The request timed out. Please try again later or check the URL."
 
47
  return f"Error fetching the webpage: {str(e)}"
48
  except Exception as e:
49
  return f"An unexpected error occurred: {str(e)}"