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

package/README.md

@@ -81,22 +81,11 @@ On first launch, AgentLoop opens the **Model Selection** screen. Choose how you
 1. **AgentLoop Subscription** - Use subscription credits for premium models
 2. **Free Models** - Provided by OpenCode, no API key required
 3. **Bring Your Own API Key** - Connect your preferred provider:
-   - **Anthropic** - Direct API key or Claude Code CLI (recommended for Pro/Max subscribers)
+   - **Anthropic** - Direct API key
    - **OpenAI** - Direct API key
    - **Google Gemini** - Direct API key
    - **OpenRouter** - Access 100+ models
 
-For Claude models with your Pro/Max subscription:
-```bash
-# Install Claude Code CLI
-npm install -g @anthropic-ai/claude-code
-
-# Authenticate
-claude
-```
-
-Then restart AgentLoop—your Claude models will appear automatically.
-
 To change models later, use the `/models` command.
 
 ### Interacting with AgentLoop

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trygentic/agentloop",
-  "version": "0.16.0-alpha.11",
+  "version": "0.17.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.16.0-alpha.11",
-    "@trygentic/agentloop-linux-x64": "0.16.0-alpha.11"
+    "@trygentic/agentloop-darwin-arm64": "0.17.0-alpha.11",
+    "@trygentic/agentloop-linux-x64": "0.17.0-alpha.11"
   },
   "engines": {
     "node": ">=18.0.0"

package/templates/agents/_base/proactive.bt.json

@@ -0,0 +1,43 @@
+{
+  "name": "proactive-base",
+  "description": "Base behavior tree for proactive agents that actively monitor, scan, or poll on their own initiative rather than waiting for external signals. Provides the standard tick loop: wait for tick (yields to prevent busy-spinning), scan environment (placeholder), process results (placeholder), and loop back. Child agents extend this tree and override the <<ScanEnvironment>> and <<ProcessResults>> placeholders with their agent-specific logic via the 'overrides' mechanism. Current example: orchestrator. Future examples: DevOps monitors, marketing agents with browser automation, etc.",
+  "version": "1.0.0",
+  "mode": "proactive",
+  "tree": {
+    "type": "root",
+    "child": {
+      "type": "sequence",
+      "comment": "Main tick loop - runs continuously, yielding each iteration to the tick timer to prevent busy-spinning",
+      "children": [
+        {
+          "type": "action",
+          "call": "WaitForTick",
+          "comment": "Yield to the tick loop timer. Returns RUNNING until the next tick fires, preventing busy-spinning. The tick interval is configured by the agent runner (default 500ms for orchestrator)."
+        },
+        {
+          "type": "action",
+          "call": "ScanEnvironment",
+          "name": "ScanEnvironment",
+          "comment": "<<SCANNING>> placeholder - child agents MUST override this node with their agent-specific scanning/monitoring logic using overrides.nodes.ScanEnvironment. Examples: orchestrator scans the task board for ready tasks, DevOps agent checks infrastructure health, marketing agent polls social feeds."
+        },
+        {
+          "type": "action",
+          "call": "ProcessResults",
+          "name": "ProcessResults",
+          "comment": "<<PROCESSING>> placeholder - child agents MUST override this node with their agent-specific action logic using overrides.nodes.ProcessResults. Examples: orchestrator assigns tasks to agents, DevOps agent triggers alerts or remediation, marketing agent schedules posts."
+        },
+        {
+          "type": "action",
+          "call": "Loop",
+          "comment": "Return RUNNING to restart the BT from the root - wait for next tick"
+        }
+      ]
+    }
+  },
+  "blackboardDefaults": {
+    "loopCount": 0,
+    "lastTickAt": null,
+    "scanResults": null,
+    "lastScanAt": null
+  }
+}

package/templates/agents/_base/reactive-delegation.bt.json

@@ -0,0 +1,73 @@
+{
+  "name": "reactive-delegation-base",
+  "description": "Base behavior tree for reactive delegation-based agents (product-manager). Provides the standard continuous loop: wait for agent message or task assignment, fetch context, process (placeholder), report completion, clear context, and loop back. Child agents extend this tree and override the <<processing>> placeholder with their agent-specific workflow via the 'overrides' mechanism.",
+  "version": "1.0.0",
+  "mode": "reactive",
+  "tree": {
+    "type": "root",
+    "child": {
+      "type": "sequence",
+      "comment": "Main continuous loop - never exits unless agent is stopped",
+      "children": [
+        {
+          "type": "action",
+          "call": "WaitForAgentMessage",
+          "comment": "Block until a delegation request arrives via agent-to-agent messaging (primary) or orchestrator task assignment (fallback). Sets taskTitle, taskDescription, and isAgentMessage on blackboard."
+        },
+        {
+          "type": "action",
+          "call": "FetchTaskContext",
+          "comment": "Load task details if a real DB task was assigned, or use the request data already on the blackboard (for both agent messages and direct requests)"
+        },
+        {
+          "type": "action",
+          "call": "ProcessDelegation",
+          "name": "ProcessDelegation",
+          "comment": "<<PROCESSING>> placeholder - child agents MUST override this node with their agent-specific workflow using overrides.nodes.ProcessDelegation"
+        },
+        {
+          "type": "action",
+          "call": "AddCompletionComment",
+          "comment": "Add a completion comment summarizing the agent's work"
+        },
+        {
+          "type": "action",
+          "call": "ReportTriggerPass"
+        },
+        {
+          "type": "action",
+          "call": "ClearTaskContext",
+          "comment": "Reset task-specific blackboard keys to prepare for next delegation request"
+        },
+        {
+          "type": "action",
+          "call": "Loop",
+          "comment": "Return to start - wait for next delegation request"
+        }
+      ]
+    }
+  },
+  "blackboardDefaults": {
+    "taskComments": null,
+    "taskDetails": null,
+    "requestedStatus": "done",
+    "statusChangeReason": "Processing complete",
+    "currentTaskId": null,
+    "taskAssignedAt": null,
+    "loopCount": 0,
+    "custom": {
+      "loopCount": 0,
+      "shouldLoop": false,
+      "continuousTaskId": null,
+      "currentTaskId": null,
+      "taskAssignedAt": null,
+      "agentMessageId": null,
+      "agentMessageContent": null,
+      "agentMessageSender": null,
+      "agentMessageType": null,
+      "isDirectRequest": false,
+      "isAgentMessage": false,
+      "isColumnTriggered": false
+    }
+  }
+}

package/templates/agents/_base/reactive-message.bt.json

@@ -0,0 +1,58 @@
+{
+  "name": "reactive-message-base",
+  "description": "Base behavior tree for reactive message-based agents (chat). Provides the standard continuous loop: wait for message, fetch context, process (placeholder), update history, clear context, and loop back. Child agents extend this tree and override the <<processing>> placeholder with their agent-specific workflow via the 'overrides' mechanism.",
+  "version": "1.0.0",
+  "mode": "reactive",
+  "tree": {
+    "type": "root",
+    "child": {
+      "type": "sequence",
+      "comment": "Main continuous loop - processes messages indefinitely",
+      "children": [
+        {
+          "type": "action",
+          "call": "WaitForMessage",
+          "comment": "Block until a message arrives (user input or agent message). Polls the message queue."
+        },
+        {
+          "type": "action",
+          "call": "FetchMessageContext",
+          "comment": "Load message details, sender info, conversation history, and any relevant context"
+        },
+        {
+          "type": "action",
+          "call": "ProcessMessage",
+          "name": "ProcessMessage",
+          "comment": "<<PROCESSING>> placeholder - child agents MUST override this node with their agent-specific workflow using overrides.nodes.ProcessMessage"
+        },
+        {
+          "type": "action",
+          "call": "UpdateConversationHistory",
+          "comment": "Add this exchange to conversation history"
+        },
+        {
+          "type": "action",
+          "call": "ClearMessageContext",
+          "comment": "Reset message-specific blackboard keys for next message"
+        },
+        {
+          "type": "action",
+          "call": "Loop",
+          "comment": "Return to start to wait for next message"
+        }
+      ]
+    }
+  },
+  "blackboardDefaults": {
+    "currentMessage": null,
+    "messageSender": null,
+    "messageType": null,
+    "messageContent": null,
+    "conversationHistory": [],
+    "currentTaskId": null,
+    "taskAssignedAt": null,
+    "loopCount": 0,
+    "messageCount": 0,
+    "lastActivityAt": null
+  }
+}

package/templates/agents/_base/reactive-task.bt.json

@@ -0,0 +1,51 @@
+{
+  "name": "reactive-task-base",
+  "description": "Base behavior tree for reactive task-based agents (engineer, qa-tester, release). Provides the standard continuous loop: wait for task assignment, fetch context, process (placeholder), clear context, and loop back. Child agents extend this tree and override the <<processing>> placeholder with their agent-specific workflow via the 'overrides' mechanism.",
+  "version": "1.0.0",
+  "mode": "reactive",
+  "tree": {
+    "type": "root",
+    "child": {
+      "type": "sequence",
+      "comment": "Main continuous loop - never exits unless agent is stopped",
+      "children": [
+        {
+          "type": "action",
+          "call": "WaitForTask",
+          "comment": "Block until orchestrator assigns a task via ContinuousAgentRunner.assignTask()"
+        },
+        {
+          "type": "action",
+          "call": "FetchTaskContext",
+          "comment": "Load task details, comments, and determine context for processing"
+        },
+        {
+          "type": "action",
+          "call": "ProcessTask",
+          "name": "ProcessTask",
+          "comment": "<<PROCESSING>> placeholder - child agents MUST override this node with their agent-specific workflow using overrides.nodes.ProcessTask"
+        },
+        {
+          "type": "action",
+          "call": "ClearTaskContext",
+          "comment": "Reset task-specific blackboard keys to prepare for next task assignment"
+        },
+        {
+          "type": "action",
+          "call": "Loop",
+          "comment": "Return RUNNING to restart the BT from the root - wait for next task"
+        }
+      ]
+    }
+  },
+  "blackboardDefaults": {
+    "taskComments": null,
+    "taskDetails": null,
+    "requestedStatus": null,
+    "statusChangeReason": null,
+    "currentTaskId": null,
+    "taskAssignedAt": null,
+    "loopCount": 0,
+    "isColumnTriggered": false
+  }
+}

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

@@ -2,6 +2,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",
+  "mode": "reactive",
   "tree": {
     "type": "root",
     "child": {
@@ -43,7 +44,7 @@
             },
             {
               "type": "sequence",
-              "comment": "Async task request - delegate work to orchestrator without blocking",
+              "comment": "Async task request - delegate work to product-manager without blocking",
               "children": [
                 {
                   "type": "condition",
@@ -51,13 +52,13 @@
                 },
                 {
                   "type": "action",
-                  "call": "QueueAsyncTask",
-                  "comment": "Create task in orchestrator and return immediately (fire-and-forget)"
+                  "call": "DelegateWork",
+                  "comment": "Delegate work to product-manager via delegate_work (fire-and-forget)"
                 },
                 {
                   "type": "action",
                   "call": "SendTaskQueuedResponse",
-                  "comment": "Acknowledge to user that task was queued"
+                  "comment": "Acknowledge to user that work was delegated"
                 }
               ]
             },
@@ -167,7 +168,7 @@
                 {
                   "type": "llm-selector",
                   "name": "ClassifyUserIntent",
-                  "prompt": "Classify the user's intent based on their message.\n\nUser message: {{messageContent}}\n\nConversation history:\n{{conversationHistory}}\n\nClassify the intent to determine the best response strategy.",
+                  "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": {
                     "general_chat": {
@@ -175,10 +176,9 @@
                       "child": {
                         "type": "llm-action",
                         "name": "GenerateGeneralResponse",
-                        "prompt": "You are a helpful AI assistant. Respond to the user's message naturally and helpfully.\n\nUser message: {{messageContent}}\n\nConversation history:\n{{conversationHistory}}\n\nProvide a thoughtful, helpful response.",
+                        "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",
-                        "maxTurns": 20,
                         "outputSchema": {
                           "type": "object",
                           "properties": {
@@ -204,10 +204,9 @@
                           {
                             "type": "llm-action",
                             "name": "AnswerCodeQuestion",
-                            "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\nProvide a clear, accurate answer based on the actual codebase.",
+                            "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",
-                            "maxTurns": 30,
                             "outputSchema": {
                               "type": "object",
                               "properties": {
@@ -223,23 +222,40 @@
                         ]
                       }
                     },
+                    "direct_execution": {
+                      "description": "Single operational command (run tests, lint, build, etc.) - execute directly without creating tasks",
+                      "child": {
+                        "type": "sequence",
+                        "children": [
+                          {
+                            "type": "action",
+                            "call": "AnalyzeCodebase",
+                            "comment": "Gather codebase context to detect package manager and project type"
+                          },
+                          {
+                            "type": "action",
+                            "call": "ExecuteDirectCommand",
+                            "comment": "Map natural language to shell command and execute directly"
+                          }
+                        ]
+                      }
+                    },
                     "task_request": {
-                      "description": "User wants to create a task or make code changes - delegate to orchestrator",
+                      "description": "User wants to create, build, implement, fix, change, or modify something - delegate to product-manager via delegate_work",
                       "child": {
                         "type": "sequence",
                         "children": [
                           {
                             "type": "llm-action",
                             "name": "ExtractTaskDetails",
-                            "prompt": "The user wants to create a task or make code changes. Extract the task details from their message.\n\nUser message: {{messageContent}}\n\nConversation history:\n{{conversationHistory}}\n\nExtract a clear task title and description that an engineer agent can execute.",
+                            "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": {
                               "type": "object",
                               "properties": {
-                                "taskTitle": { "type": "string", "description": "Concise task title" },
-                                "taskDescription": { "type": "string", "description": "Detailed task description with acceptance criteria" },
-                                "priority": { "type": "string", "enum": ["low", "medium", "high", "critical"], "description": "Suggested task priority" },
-                                "isAsync": { "type": "boolean", "description": "Whether this should be processed asynchronously" }
+                                "taskTitle": { "type": "string", "description": "Concise high-level title for the work request" },
+                                "taskDescription": { "type": "string", "description": "High-level description of what the user wants - do NOT decompose into subtasks" },
+                                "priority": { "type": "string", "enum": ["low", "medium", "high", "critical"], "description": "Suggested task priority" }
                               },
                               "required": ["taskTitle", "taskDescription"]
                             },
@@ -248,7 +264,8 @@
                           },
                           {
                             "type": "action",
-                            "call": "QueueAsyncTask"
+                            "call": "DelegateWork",
+                            "comment": "Delegate to product-manager via delegate_work MCP tool instead of creating tasks directly"
                           },
                           {
                             "type": "action",
@@ -287,7 +304,7 @@
                       }
                     }
                   },
-                  "defaultBranch": "general_chat",
+                  "defaultBranch": "task_request",
                   "confidenceThreshold": 0.6
                 },
                 {

package/templates/agents/chat/chat.md

@@ -9,7 +9,7 @@ model: inherit
 instanceCount: 1
 showInLiveView: true
 tools:
-  - AskUserQuestion
+  - question
   - mcp__agentloop__delegate_work
   - mcp__agentloop__list_tasks
   - mcp__agentloop__get_task
@@ -33,14 +33,30 @@ You are **AgentLoop** - the primary user-facing interface for the multi-agent de
 3. **Status Reporting**: Show task status, orchestrator health, and project progress
 4. **Orchestrator Control**: Start/stop the orchestrator when users request it
 
-## CRITICAL: Delegation Rules
+## CRITICAL: Delegation Rules - READ THIS FIRST
 
-You MUST use `delegate_work` for ALL development work requests.
-The product-manager will handle task breakdown, subproject creation, and dependency setup.
+**ABSOLUTE RULE: You MUST call `mcp__agentloop__delegate_work` for ANY request that involves creating, building, implementing, fixing, modifying, or changing code or files.**
 
-**You do NOT have access to `create_task`.** This is by design.
+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.
 
-### delegate_work Usage
+**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.
+
+The ONLY way to get code work done is to call `mcp__agentloop__delegate_work`.
+
+### When to call delegate_work
+
+Call `mcp__agentloop__delegate_work` when the user says ANY of these (or similar):
+- "Create a ..." / "Build a ..." / "Make a ..." / "Implement ..."
+- "Fix ..." / "Debug ..." / "Resolve ..."
+- "Add ..." / "Update ..." / "Change ..." / "Modify ..."
+- "Refactor ..." / "Optimize ..." / "Improve ..."
+- "Set up ..." / "Configure ..." / "Install ..."
+- "Write tests for ..." / "Add logging to ..."
+- "Remove ..." / "Delete ..." (code/file changes)
+- Any request that implies code, file, or configuration changes
+
+### How to call delegate_work
 
 Submit a HIGH-LEVEL work request. Call this ONCE per user request.
 
@@ -53,8 +69,6 @@ CORRECT - One high-level call:
 WRONG - Multiple specific calls (this is the PM's job, NOT yours):
   delegate_work(title: "Create auth database schema", ...)
   delegate_work(title: "Implement JWT token service", ...)
-  delegate_work(title: "Build login endpoint", ...)
-  delegate_work(title: "Build registration endpoint", ...)
 
 RULE: If you find yourself wanting to call delegate_work more than once,
 you are decomposing the work yourself. STOP. Combine everything into ONE call
@@ -63,18 +77,13 @@ and let the product-manager handle the decomposition.
 If the user asks for multiple unrelated things, make ONE call per distinct project/feature.
 Each call creates a subproject that the PM will break into tasks.
 
-## When to Delegate vs Respond Directly
-
-**Delegate to PM (use delegate_work):**
-- Feature implementation requests
-- Bug fixes that require code changes
-- Multi-step workflows needing coordination
+### When to respond directly (NO delegation)
 
-**Respond directly (no delegation needed):**
-- Questions, explanations, summaries
-- Writing requests (paragraphs, documentation drafts)
-- Analysis and discussion
+**Respond directly (no delegation needed) ONLY for:**
+- Questions about concepts, explanations, summaries
+- "What is ...?" / "How does ... work?" / "Explain ..."
 - Status queries (use list_tasks, get_task, get_orchestrator_status)
+- General conversation that does NOT request any code or file changes
 
 ## Communication Style