notebooks complete

Author: felixs8696

src/agentex/lib/cli/templates/default/README.md.j2

@@ -62,6 +62,7 @@ This file is essential for both local development and deployment of your agent.
 │   └── acp.py               # ACP server and event handlers
 ├── Dockerfile               # Container definition
 ├── manifest.yaml            # Deployment config
+├── dev.ipynb                # Development notebook for testing
 {% if use_uv %}
 └── pyproject.toml          # Dependencies (uv)
 {% else %}
@@ -76,7 +77,27 @@ This file is essential for both local development and deployment of your agent.
 - Add your own tools and capabilities
 - Implement custom state management
 
-### 2. Manage Dependencies
+### 2. Test Your Agent with the Development Notebook
+Use the included `dev.ipynb` Jupyter notebook to test your agent interactively:
+
+```bash
+# Start Jupyter notebook (make sure you have jupyter installed)
+jupyter notebook dev.ipynb
+
+# Or use VS Code to open the notebook directly
+code dev.ipynb
+```
+
+The notebook includes:
+- **Setup**: Connect to your local AgentEx backend
+- **Task creation**: Create a new task for the conversation
+- **Event sending**: Send events to the agent and get responses
+- **Async message subscription**: Subscribe to server-side events to receive agent responses
+- **Rich message display**: Beautiful formatting with timestamps and author information
+
+The notebook automatically uses your agent name (`{{ agent_name }}`) and demonstrates the agentic ACP workflow: create task → send event → subscribe to responses.
+
+### 3. Manage Dependencies
 
 {% if use_uv %}
 You chose **uv** for package management. Here's how to work with dependencies:
@@ -115,7 +136,7 @@ pip install -r requirements.txt
 - Wide compatibility
 {% endif %}
 
-### 3. Configure Credentials
+### 4. Configure Credentials
 Options:
 1. Add any required credentials to your manifest.yaml via the `env` section
 2. Export them in your shell: `export OPENAI_API_KEY=...`

src/agentex/lib/cli/templates/temporal/README.md.j2

@@ -68,6 +68,7 @@ This file is essential for both local development and deployment of your agent.
 │   └── run_worker.py        # Temporal worker setup
 ├── Dockerfile               # Container definition
 ├── manifest.yaml            # Deployment config
+├── dev.ipynb                # Development notebook for testing
 {% if use_uv %}
 └── pyproject.toml          # Dependencies (uv)
 {% else %}
@@ -82,12 +83,32 @@ This file is essential for both local development and deployment of your agent.
 - Add your own tools and capabilities
 - Implement custom state management
 
-### 2. Develop Temporal Workflows
+### 2. Test Your Agent with the Development Notebook
+Use the included `dev.ipynb` Jupyter notebook to test your agent interactively:
+
+```bash
+# Start Jupyter notebook (make sure you have jupyter installed)
+jupyter notebook dev.ipynb
+
+# Or use VS Code to open the notebook directly
+code dev.ipynb
+```
+
+The notebook includes:
+- **Setup**: Connect to your local AgentEx backend
+- **Task creation**: Create a new task for the conversation
+- **Event sending**: Send events to the agent and get responses
+- **Async message subscription**: Subscribe to server-side events to receive agent responses
+- **Rich message display**: Beautiful formatting with timestamps and author information
+
+The notebook automatically uses your agent name (`{{ agent_name }}`) and demonstrates the agentic ACP workflow: create task → send event → subscribe to responses.
+
+### 3. Develop Temporal Workflows
 - Edit `workflow.py` to define your agent's async workflow logic
 - Modify `activities.py` to add custom activities
 - Use `run_worker.py` to configure the Temporal worker
 
-### 3. Manage Dependencies
+### 4. Manage Dependencies
 
 {% if use_uv %}
 You chose **uv** for package management. Here's how to work with dependencies:
@@ -135,7 +156,7 @@ pip install -r requirements.txt
 - Wide compatibility
 {% endif %}
 
-### 4. Configure Credentials
+### 5. Configure Credentials
 - Add any required credentials to your manifest.yaml
 - For local development, create a `.env` file in the project directory
 - Use `load_dotenv()` only in development mode: