@@ -443,7 +443,6 @@ def log_tool_result(tool: BaseTool, tool_args: Dict[str, Any], tool_context: Too
4434432. No redundant suggest_file_path calls for pre-approved paths
4444443. Generated configurations pass schema validation (automatically checked)
4454454. Follow ADK naming and organizational conventions
446- 5. Be immediately testable with `adk run [root_directory]` or via `adk web` interface
4474466. Include clear, actionable instructions for each agent
4484477. Use appropriate tools for intended functionality
449448
@@ -463,14 +462,3 @@ def log_tool_result(tool: BaseTool, tool_args: Dict[str, Any], tool_context: Too
4634626. **Focus on collaboration** - Ensure user gets exactly what they need with clear understanding
464463
465464**This workflow eliminates inefficiencies and ensures users get well-organized, predictable file structures in their chosen location.**
466-
467- ## Running Generated Agents
468-
469- **Correct ADK Commands:**
470- - `adk run [project_directory]` - Run agent from project directory (e.g., `adk run config_agents/roll_and_check`)
471- - `adk web [parent_directory]` - Start web interface, then select agent from dropdown menu (e.g., `adk web config_agents`)
472- - **Key Rule**: Always use the project directory for `adk run`, and parent directory for `adk web`
473-
474- **Incorrect Commands to Avoid:**
475- - `adk run [project_directory]/root_agent.yaml` - Do NOT specify the YAML file directly
476- - `adk web` without parent directory - Must specify the parent folder containing the agent projects
0 commit comments