@trygentic/agentloop 0.17.0-alpha.11 → 0.18.0-alpha.11

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trygentic/agentloop",
-  "version": "0.17.0-alpha.11",
+  "version": "0.18.0-alpha.11",
   "description": "AI-powered autonomous coding agent",
   "bin": {
     "agentloop": "./bin/agentloop"
@@ -9,8 +9,8 @@
     "postinstall": "node ./scripts/postinstall.mjs"
   },
   "optionalDependencies": {
-    "@trygentic/agentloop-darwin-arm64": "0.17.0-alpha.11",
-    "@trygentic/agentloop-linux-x64": "0.17.0-alpha.11"
+    "@trygentic/agentloop-darwin-arm64": "0.18.0-alpha.11",
+    "@trygentic/agentloop-linux-x64": "0.18.0-alpha.11"
   },
   "engines": {
     "node": ">=18.0.0"

package/templates/agents/chat/chat.bt.json

@@ -1,7 +1,7 @@
 {
   "name": "chat-continuous-agent-tree",
   "description": "Continuous behavior tree for the Chat agent. Processes messages in a loop from users and other agents. Unlike task-based agents, chat uses a message queue model with support for async task delegation.",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "mode": "reactive",
   "tree": {
     "type": "root",
@@ -85,8 +85,15 @@
                         {
                           "type": "llm-action",
                           "name": "ProcessAgentQuery",
-                          "prompt": "You are the chat agent responding to a query from another agent in the system.\n\nQuery from {{messageSender}}:\n{{messageContent}}\n\nConversation context:\n{{conversationHistory}}\n\nProvide a helpful response that addresses the agent's query. Be concise but complete.",
+                          "prompt": "You are the chat agent responding to a query from another agent in the system.\n\nQuery from {{messageSender}}:\n{{messageContent}}\n\nConversation context:\n{{conversationHistory}}\n\nYou can use task and status tools to look up information the agent is asking about. Provide a helpful response that addresses the agent's query. Be concise but complete.",
                           "contextKeys": ["messageSender", "messageContent", "conversationHistory"],
+                          "allowedTools": [
+                            "mcp__agentloop__list_tasks",
+                            "mcp__agentloop__get_task",
+                            "mcp__agentloop__get_orchestrator_status",
+                            "mcp__agentloop__get_system_health"
+                          ],
+                          "maxTurns": 5,
                           "outputSchema": {
                             "type": "object",
                             "properties": {
@@ -168,6 +175,7 @@
                 {
                   "type": "llm-selector",
                   "name": "ClassifyUserIntent",
+                  "allowedTools": [],
                   "prompt": "Classify the user's intent based on their message.\n\nUser message: {{messageContent}}\n\nConversation history:\n{{conversationHistory}}\n\nClassify the intent into one of the following categories:\n\n- direct_execution: The user wants to run a SINGLE operational command that can be executed directly without creating tasks. This is for simple, well-known dev commands that don't require writing code or making changes. Examples: \"run the tests\", \"run tests\", \"lint the code\", \"type check\", \"build the project\", \"install dependencies\", \"format the code\", \"check types\".\n  IMPORTANT: \"run the tests\" = direct_execution. \"make all tests pass\" = task_request (requires code changes). \"lint\" = direct_execution. \"fix all lint errors\" = task_request.\n\n- task_request: The user wants something BUILT, CREATED, IMPLEMENTED, FIXED, CHANGED, MODIFIED, ADDED, REMOVED, REFACTORED, CONFIGURED, or SET UP. This includes ANY request that would require writing code, editing files, or making changes to the project. Examples: \"create a todo app\", \"fix the login bug\", \"add authentication\", \"refactor the database module\", \"update the API endpoint\", \"build a dashboard\", \"set up CI/CD\", \"implement user profiles\", \"make the tests pass\", \"optimize the search function\".\n\n- code_question: The user is ASKING a question about how existing code works, what a function does, or how something is structured. They want INFORMATION, not CHANGES. Examples: \"how does the auth module work?\", \"what does this function do?\", \"where is the database config?\", \"explain the routing logic\".\n\n- status_inquiry: The user is asking about task status, progress, what agents are doing, or system health. Examples: \"what's the status?\", \"how's it going?\", \"show me the tasks\", \"is the orchestrator running?\".\n\n- general_chat: The user is having general conversation, asking conceptual questions not about THIS codebase, or chatting. Examples: \"hello\", \"what is a REST API?\", \"explain microservices\", \"thanks\".\n\nIMPORTANT: When in doubt between task_request and other categories, choose task_request. It is better to delegate work that could have been answered conversationally than to try to answer a work request conversationally.",
                   "contextKeys": ["messageContent", "conversationHistory"],
                   "branches": {
@@ -179,6 +187,7 @@
                         "prompt": "You are a helpful AI assistant having a conversation with the user. Respond to the user's message naturally and helpfully.\n\nUser message: {{messageContent}}\n\nConversation history:\n{{conversationHistory}}\n\nIMPORTANT RULES:\n- You are ONLY having a conversation. You are NOT writing code, NOT editing files, NOT running commands.\n- If the user is asking you to create, build, fix, implement, or change ANYTHING, respond with: \"I'll delegate that work to the team. Let me set that up for you.\" and set suggestedActions to [\"delegate_work\"].\n- Do NOT use bash, write, edit, read, or any file/shell tools. You do not have access to them.\n- Only provide conversational responses: explanations, answers to questions, summaries, etc.\n\nProvide a thoughtful, helpful response.",
                         "contextKeys": ["messageContent", "conversationHistory", "codebaseContext"],
                         "subagent": "chat",
+                        "allowedTools": [],
                         "outputSchema": {
                           "type": "object",
                           "properties": {
@@ -207,6 +216,19 @@
                             "prompt": "The user has a question about the codebase. Analyze and answer their question.\n\nUser question: {{messageContent}}\n\nCodebase context:\n{{codebaseContext}}\n\nUse the code-graph-rag MCP tools (semantic_search, list_file_entities, analyze_code_impact, find_similar_code) and Read/Grep/Glob to examine specific files as needed. If code-graph-rag tools fail, fall back to Grep/Glob.\n\nIMPORTANT: You are ONLY answering questions about the code. Do NOT make any changes to files. Do NOT create, modify, or delete anything. If the user is actually requesting changes, respond with: \"That sounds like a code change request. Let me delegate that to the engineering team.\" and set the response accordingly.\n\nProvide a clear, accurate answer based on the actual codebase.",
                             "contextKeys": ["messageContent", "codebaseContext", "conversationHistory"],
                             "subagent": "chat",
+                            "allowedTools": [
+                              "Read",
+                              "Glob",
+                              "Grep",
+                              "mcp__agentloop__list_tasks",
+                              "mcp__agentloop__get_task",
+                              "mcp__agentloop-memory__semantic_search",
+                              "mcp__agentloop-memory__list_file_entities",
+                              "mcp__agentloop-memory__list_entity_relationships",
+                              "mcp__agentloop-memory__analyze_code_impact",
+                              "mcp__agentloop-memory__find_similar_code"
+                            ],
+                            "maxTurns": 10,
                             "outputSchema": {
                               "type": "object",
                               "properties": {
@@ -248,6 +270,7 @@
                           {
                             "type": "llm-action",
                             "name": "ExtractTaskDetails",
+                            "allowedTools": [],
                             "prompt": "The user wants to create a task or make code changes. Extract a HIGH-LEVEL work request from their message.\n\nUser message: {{messageContent}}\n\nConversation history:\n{{conversationHistory}}\n\nIMPORTANT: Extract a single high-level title and description. Do NOT decompose the work into subtasks - the product-manager will handle task breakdown.\n\nExample: If the user says 'Create a todo app', extract title='Create a todo app' and a description covering what the user wants at a high level.",
                             "contextKeys": ["messageContent", "conversationHistory"],
                             "outputSchema": {
@@ -287,7 +310,17 @@
                           {
                             "type": "llm-action",
                             "name": "FormatStatusResponse",
-                            "prompt": "The user is asking about system status. Format a clear status update based on the data.\n\nUser question: {{messageContent}}\n\nSystem status:\n{{systemStatus}}\n\nProvide a clear, informative status update.",
+                            "allowedTools": [
+                              "mcp__agentloop__list_tasks",
+                              "mcp__agentloop__get_task",
+                              "mcp__agentloop__list_subprojects",
+                              "mcp__agentloop__get_subproject",
+                              "mcp__agentloop__get_orchestrator_status",
+                              "mcp__agentloop__get_system_health",
+                              "mcp__agentloop__get_daemon_status"
+                            ],
+                            "maxTurns": 5,
+                            "prompt": "The user is asking about system status. Format a clear status update based on the data.\n\nUser question: {{messageContent}}\n\nSystem status:\n{{systemStatus}}\n\nYou have access to task and status tools if you need to look up additional details. Provide a clear, informative status update.",
                             "contextKeys": ["messageContent", "systemStatus", "conversationHistory"],
                             "outputSchema": {
                               "type": "object",

package/templates/agents/chat/chat.md

@@ -5,11 +5,13 @@ description: >-
   orchestrator. This is the user-facing interface for AgentLoop. Does NOT
   create tasks directly - always delegates via delegate_work which routes
   to the appropriate agent.
-model: inherit
 instanceCount: 1
 showInLiveView: true
 tools:
   - question
+  - Read
+  - Glob
+  - Grep
   - mcp__agentloop__delegate_work
   - mcp__agentloop__list_tasks
   - mcp__agentloop__get_task
@@ -20,6 +22,11 @@ tools:
   - mcp__agentloop__get_orchestrator_status
   - mcp__agentloop__get_system_health
   - mcp__agentloop__get_daemon_status
+  - mcp__agentloop-memory__semantic_search
+  - mcp__agentloop-memory__list_file_entities
+  - mcp__agentloop-memory__list_entity_relationships
+  - mcp__agentloop-memory__analyze_code_impact
+  - mcp__agentloop-memory__find_similar_code
 ---
 
 # AgentLoop
@@ -39,8 +46,9 @@ You are **AgentLoop** - the primary user-facing interface for the multi-agent de
 
 You are a CONVERSATIONAL INTERFACE ONLY. You do NOT write code. You do NOT modify files. You do NOT run shell commands. You ONLY delegate work to other agents.
 
-**You do NOT have access to any of these tools: `bash`, `write`, `edit`, `read`, `glob`, `grep`, `TodoWrite`, or ANY file/shell tools.**
-If you find yourself wanting to use any tool other than `delegate_work`, `list_tasks`, `get_task`, `list_subprojects`, `get_subproject`, `run_orchestrator`, `stop_orchestrator`, `get_orchestrator_status`, `get_system_health`, `get_daemon_status`, or `question` -- STOP. You are making a mistake.
+**You do NOT have access to any of these tools: `bash`, `write`, `edit`, `TodoWrite`, or ANY file-modifying/shell tools.**
+You have READ-ONLY code access (`Read`, `Glob`, `Grep`, and code-graph-rag MCP tools) for answering code questions. You must NEVER use these to modify files - only to examine and explain code.
+If you find yourself wanting to use any tool other than `delegate_work`, `list_tasks`, `get_task`, `list_subprojects`, `get_subproject`, `run_orchestrator`, `stop_orchestrator`, `get_orchestrator_status`, `get_system_health`, `get_daemon_status`, `question`, `Read`, `Glob`, `Grep`, or `mcp__agentloop-memory__*` -- STOP. You are making a mistake.
 
 The ONLY way to get code work done is to call `mcp__agentloop__delegate_work`.