Add tool_agent_caller_loop and group chat notebook. (#405)

* Add tool_agent_caller_loop and group chat notebook.

* Fix types

* fix ref

---------

Co-authored-by: Jack Gerrits <[email protected]>

Author: ekzhu

python/docs/src/core-concepts/overview.md

@@ -116,7 +116,7 @@ implementation of the contracts determines how agents handle messages.
 The behavior contract is sometimes referred to as the message protocol.
 It is the developer's responsibility to implement the behavior contract.
 Multi-agent patterns are design patterns that emerge from behavior contracts
-(see [Multi-Agent Design Patterns](../getting-started/multi-agent-design-patterns.ipynb)).
+(see [Multi-Agent Design Patterns](../getting-started/multi-agent-design-patterns.md)).
 
 ### An Example Application
 

python/docs/src/getting-started/group-chat.ipynb

@@ -0,0 +1,18 @@
+# Multi-Agent Design Patterns
+
+Agents can work together in a variety of ways to solve problems.
+Research works like [AutoGen](https://aka.ms/autogen-paper),
+[MetaGPT](https://arxiv.org/abs/2308.00352)
+and [ChatDev](https://arxiv.org/abs/2307.07924) have shown
+multi-agent systems out-performing single agent systems at complex tasks
+like software development.
+
+A multi-agent design pattern is a structure that emerges from message protocols:
+it describes how agents interact with each other to solve problems.
+For example, the [tool-equiped agent](./tools.ipynb#tool-equipped-agent) in
+the previous section employs a design pattern called ReAct,
+which involves an agent interacting with tools.
+
+You can implement any multi-agent design pattern using AGNext agents.
+In the next two sections, we will discuss two common design patterns:
+group chat for task decomposition, and reflection for robustness.

python/docs/src/getting-started/multi-agent-design-patterns.md

@@ -4,30 +4,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "# Multi-Agent Design Patterns\n",
-    "\n",
-    "Agents can work together in a variety of ways to solve problems.\n",
-    "Research works like [AutoGen](https://aka.ms/autogen-paper),\n",
-    "[MetaGPT](https://arxiv.org/abs/2308.00352)\n",
-    "and [ChatDev](https://arxiv.org/abs/2307.07924) have shown\n",
-    "multi-agent systems out-performing single agent systems at complex tasks\n",
-    "like software development.\n",
-    "\n",
-    "A multi-agent design pattern is a structure that emerges from message protocols:\n",
-    "it describes how agents interact with each other to solve problems.\n",
-    "For example, the [tool-equiped agent](./tools.ipynb#tool-equipped-agent) in\n",
-    "the previous section employs a design pattern called ReAct,\n",
-    "which involves an agent interacting with tools.\n",
-    "\n",
-    "You can implement any multi-agent design pattern using AGNext agents.\n",
-    "In this section, we use the reflection pattern as an example."
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "## Reflection\n",
+    "# Reflection\n",
     "\n",
     "Reflection is a design pattern where an LLM generation is followed by a reflection,\n",
     "which in itself is another LLM generation conditioned on the output of the first one.\n",
@@ -50,7 +27,7 @@
     "will generate a code snippet, and the reviewer agent will generate a critique\n",
     "of the code snippet.\n",
     "\n",
-    "### Message Protocol\n",
+    "## Message Protocol\n",
     "\n",
     "Before we define the agents, we need to first define the message protocol for the agents."
    ]
@@ -107,7 +84,7 @@
     "\n",
     "![coder-reviewer data flow](coder-reviewer-data-flow.svg)\n",
     "\n",
-    "### Agents\n",
+    "## Agents\n",
     "\n",
     "Now, let's define the agents for the reflection design pattern."
    ]
@@ -376,7 +353,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "### Logging\n",
+    "## Logging\n",
     "\n",
     "Turn on logging to see the messages exchanged between the agents."
    ]
@@ -397,7 +374,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "### Running the Design Pattern\n",
+    "## Running the Design Pattern\n",
     "\n",
     "Let's test the design pattern with a coding task."
    ]