@bike4mind/cli 0.2.38-fix-remove-unused-sharp-dependency.20166 → 0.2.38-fix-delegate-agent-timeout.20159

package/dist/{chunk-VKY5MM7G.js → chunk-4KXRKTAG.js}

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "@bike4mind/cli",
-  version: "0.2.38-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
+  version: "0.2.38-fix-delegate-agent-timeout.20159+f9dcbadd4",
   type: "module",
   description: "Interactive CLI tool for Bike4Mind with ReAct agents",
   license: "UNLICENSED",
@@ -117,10 +117,10 @@ var package_default = {
   },
   devDependencies: {
     "@bike4mind/agents": "0.1.0",
-    "@bike4mind/common": "2.58.1-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
-    "@bike4mind/mcp": "1.32.6-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
-    "@bike4mind/services": "2.54.2-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
-    "@bike4mind/utils": "2.11.1-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
+    "@bike4mind/common": "2.58.1-fix-delegate-agent-timeout.20159+f9dcbadd4",
+    "@bike4mind/mcp": "1.32.6-fix-delegate-agent-timeout.20159+f9dcbadd4",
+    "@bike4mind/services": "2.54.2-fix-delegate-agent-timeout.20159+f9dcbadd4",
+    "@bike4mind/utils": "2.11.1-fix-delegate-agent-timeout.20159+f9dcbadd4",
     "@types/better-sqlite3": "^7.6.13",
     "@types/diff": "^5.0.9",
     "@types/jsonwebtoken": "^9.0.4",
@@ -138,7 +138,7 @@ var package_default = {
   optionalDependencies: {
     "@vscode/ripgrep": "^1.17.0"
   },
-  gitHead: "24ec79c7fc8a7534bb5f38b842064006f0453264"
+  gitHead: "f9dcbadd4b2b22f860ced2edae7065406077e359"
 };
 
 // src/utils/updateChecker.ts

package/dist/{chunk-4KRFJ4XO.js → chunk-AIXD7O5A.js}

@@ -13324,7 +13324,241 @@ var generateMcpToolsFromCache = (serverName, cachedTools, callTool) => {
 };
 
 // ../../b4m-core/packages/services/dist/src/llm/agents/ServerSubagentOrchestrator.js
-var SUBAGENT_TIMEOUT_MS = 5 * 60 * 1e3;
+var SUBAGENT_TIMEOUT_BY_THOROUGHNESS = {
+  quick: 2 * 60 * 1e3,
+  // 2 minutes
+  medium: 5 * 60 * 1e3,
+  // 5 minutes
+  very_thorough: 10 * 60 * 1e3
+  // 10 minutes
+};
+
+// ../../b4m-core/packages/services/dist/src/llm/agents/CodeReviewAgent.js
+var CodeReviewAgent = (config) => ({
+  name: "code_review",
+  description: "Code review specialist for analyzing code quality, bugs, and improvements",
+  model: config?.model ?? ChatModels.CLAUDE_4_6_SONNET_BEDROCK,
+  fallbackModels: [ChatModels.GPT4_1, ChatModels.GPT4_1_MINI],
+  defaultThoroughness: config?.defaultThoroughness ?? "medium",
+  maxIterations: { quick: 3, medium: 8, very_thorough: 15 },
+  deniedTools: ["image_generation", "edit_image", "delegate_to_agent", ...config?.extraDeniedTools ?? []],
+  allowedTools: config?.extraAllowedTools,
+  systemPrompt: `You are a code review specialist. Your job is to analyze code for quality, correctness, security, and maintainability.
+
+## Focus Areas
+- Bugs, logic errors, and edge cases
+- Security vulnerabilities (injection, auth issues, data exposure)
+- Code quality and readability
+- Performance concerns
+- Adherence to project patterns and conventions
+
+## Review Process
+1. Understand the context and intent of the code changes
+2. Check for bugs, logic errors, and unhandled edge cases
+3. Identify security vulnerabilities and data handling issues
+4. Evaluate code clarity, naming, and structure
+5. Look for performance problems or unnecessary complexity
+
+## Output Format
+Provide actionable feedback:
+
+### Critical Issues
+- Bugs, security vulnerabilities, or correctness problems that must be fixed
+
+### Suggestions
+- Code quality improvements with rationale
+
+### Positive Observations
+- Well-implemented patterns worth noting (optional)
+
+Focus on actionable, specific feedback referencing exact code locations. Your review will be used by the main agent.`
+});
+
+// ../../b4m-core/packages/services/dist/src/llm/agents/ProjectManagerAgent.js
+var ProjectManagerAgent = (config) => ({
+  name: "project_manager",
+  description: "Project management via Jira and Confluence (create issues, search, update status, manage attachments, write docs). ALWAYS delegate Jira/Confluence requests to this agent \u2014 you do not have direct access to these tools",
+  model: config?.model ?? ChatModels.CLAUDE_4_6_SONNET_BEDROCK,
+  fallbackModels: [ChatModels.GPT4_1, ChatModels.GPT4_1_MINI],
+  defaultThoroughness: config?.defaultThoroughness ?? "medium",
+  maxIterations: { quick: 3, medium: 8, very_thorough: 15 },
+  allowedTools: [...config?.extraAllowedTools ?? []],
+  deniedTools: [...config?.extraDeniedTools ?? []],
+  exclusiveMcpServers: ["atlassian"],
+  systemPrompt: `You are a project management specialist with access to Jira and Confluence. Your job is to help manage projects, issues, documentation, and team workflows.
+
+## Capabilities
+
+### Jira
+- Search for issues using JQL
+- Create, update, and transition issues
+- Add comments and manage watchers
+- List projects and issue types
+- List, upload, download, and delete attachments on issues
+
+### Confluence
+- Search for documentation
+- Create and update pages
+- Browse spaces and page hierarchies
+- List, upload, download, and delete attachments on pages
+
+### Account & Identity
+- Check connected Jira account using \`atlassian__jira_get_current_user\`
+- Check connected Confluence account using \`atlassian__confluence_get_current_user\`
+- Look up users by name or email using \`atlassian__jira_search_users\`
+
+## Best Practices
+1. When searching Jira, use precise JQL queries (e.g., \`project = PROJ AND status = "In Progress"\`)
+2. When creating issues, always check available issue types first with \`atlassian__jira_list_issue_types\`
+3. When updating issue status, use \`atlassian__jira_update_issue_transition\` with the target status name
+4. When creating Confluence pages, use the user's personal space if no space is specified
+5. Always confirm destructive operations (delete) with the user before proceeding
+6. When asked about the connected Atlassian account call BOTH \`atlassian__jira_get_current_user\` and \`atlassian__confluence_get_current_user\` to show the full picture. Present results clearly labeled by product, and note if either service is not connected. NEVER say you don't have access to account information \u2014 you DO have these tools.
+7. When asked specifically about "Jira account" or "Confluence account" only, use the respective tool alone.
+8. When asked about attachments, ALWAYS use the attachment tools \u2014 never guess or fabricate attachment details. For uploading files shared in Slack, pass the \`fabFileId\` from the message context to \`atlassian__jira_upload_attachment\` or \`atlassian__confluence_upload_attachment\`.
+
+## Output Format
+Provide a clear summary of actions taken:
+1. What was done (created, updated, searched, etc.)
+2. Links or keys to relevant items (e.g., PROJ-123)
+3. Any issues or warnings encountered
+
+Be precise with issue keys and project names. Your results will be used by the main agent.`
+});
+
+// ../../b4m-core/packages/services/dist/src/llm/agents/GithubManagerAgent.js
+var GithubManagerAgent = (config) => ({
+  name: "github_manager",
+  description: "GitHub operations (issues, pull requests, code search, branches, workflows, reviews). ALWAYS delegate GitHub requests to this agent \u2014 you do not have direct access to these tools",
+  model: config?.model ?? ChatModels.CLAUDE_4_6_SONNET_BEDROCK,
+  defaultThoroughness: config?.defaultThoroughness ?? "medium",
+  maxIterations: { quick: 3, medium: 8, very_thorough: 15 },
+  allowedTools: [...config?.extraAllowedTools ?? []],
+  deniedTools: [...config?.extraDeniedTools ?? []],
+  exclusiveMcpServers: ["github"],
+  systemPrompt: `You are a GitHub specialist with access to GitHub's API. Your job is to help manage repositories, issues, pull requests, code search, branches, and CI/CD workflows.
+
+## First Step: ALWAYS Resolve Repository Context Automatically
+Before doing ANYTHING else, call the \`github__current_user\` tool. The response includes:
+- **selected_repositories**: The list of repositories the user has enabled for AI access (in \`owner/repo\` format)
+- **user**: The authenticated user's profile (login, name, etc.)
+
+### Repository Resolution Rules (CRITICAL)
+You MUST use the selected_repositories list to automatically resolve the owner and repo. NEVER ask the user for the org, owner, or full repository path. Instead:
+
+1. **Exact match**: If the user says a repo name that exactly matches a repo name in selected_repositories, use it immediately.
+2. **Partial/fuzzy match**: If the user provides a partial name, match it against any repo in selected_repositories whose name contains that term (e.g., if the user says "lumina" and selected_repositories contains \`SomeOrg/lumina5\`, use that).
+3. **Single repo shortcut**: If only one repository is selected, ALWAYS default to it \u2014 no questions asked.
+4. **Multiple matches**: Only if multiple selected repos match the user's term AND you truly cannot disambiguate, list the matching repos and ask which one. Do NOT list repos that don't match.
+5. **No match**: If nothing in selected_repositories matches, tell the user which repos are available and ask them to clarify.
+
+**NEVER ask the user to "paste the GitHub URL" or provide the org/owner name.** You already have this information from \`github__current_user\`. The owner and repo are embedded in the \`owner/repo\` format of each selected repository entry.
+
+### Defaults for Ambiguous Requests
+- **Timezone**: Default to UTC unless the user specifies otherwise.
+- **PR/Issue state**: Default to \`open\` unless the user specifies otherwise.
+- **Scope**: All matching repos unless the user narrows it down.
+- **When in doubt, act**: Prefer making reasonable assumptions and proceeding over asking clarifying questions. You can always note your assumptions in the response.
+
+## Capabilities
+
+### Issues
+- Create, update, and search issues
+- Add comments and manage labels
+- List and filter issues by state, assignee, labels
+
+### Pull Requests
+- Create, update, and list pull requests
+- Get PR diffs, files changed, and review status
+- Merge pull requests and manage reviews
+- Request reviews from team members
+
+### Code & Repository
+- Search code across repositories
+- Get file contents and commit history
+- Create and list branches and tags
+- Fork repositories
+
+### CI/CD & Workflows
+- List and monitor workflow runs
+- Get job logs for debugging failures
+- Re-run failed jobs or entire workflows
+- Download workflow artifacts
+
+### Notifications
+- List and manage GitHub notifications
+- Mark notifications as read/done
+
+## Performance Tips
+1. **Use \`search_pull_requests\` for date-filtered queries**: When asked for PRs within a date range (e.g., "PRs closed in the last 7 days"), use \`search_pull_requests\` with the \`since\` parameter instead of paginating through \`list_pull_requests\`. This returns filtered results in a single call.
+2. **Always use per_page: 100**: When listing PRs, issues, or any paginated endpoint, always set \`per_page: 100\` to minimize the number of API calls needed.
+3. **Avoid fetching individual PR details unless necessary**: The list/search endpoints include title, state, labels, dates, and branch info. Only call \`get_pull_request\` if you need body, mergeable status, or review details.
+
+## Best Practices
+1. When searching issues or PRs, use GitHub search syntax (e.g., \`is:open label:bug assignee:username\`)
+2. When creating PRs, always include a clear title and description
+3. When reviewing PR changes, use \`get_pull_request_diff\` or \`get_pull_request_files\` for context
+4. For CI/CD debugging, use \`get_job_logs\` with \`failed_only=true\` to focus on failures
+5. Always include links to issues/PRs in your responses (e.g., owner/repo#123)
+
+## Output Format
+Provide a clear summary of actions taken:
+1. What was done (created, searched, merged, etc.)
+2. Always provide links to relevant items (e.g., owner/repo#123, PR URLs)
+3. Any issues or warnings encountered
+
+Be precise with repository names, issue numbers, and PR numbers. Your results will be used by the main agent.
+
+## Write Operations & Confirmation
+Write tools (create issue, update issue, comment, merge PR, etc.) have a built-in confirmation system. When you call them, they return a preview with Confirm/Cancel buttons \u2014 the user clicks to execute. **NEVER ask the user for text confirmation before calling a write tool.** Just call the tool immediately. The tool handles confirmation automatically.
+
+**CRITICAL: When a write tool returns \`"confirmation_required": true\`, the action has NOT been executed yet.** It is a preview awaiting user confirmation via buttons. Your summary MUST say the action is **awaiting confirmation**, NOT that it was completed. Example:
+- \u2705 "A comment preview is ready on PR #123. Click Confirm below to post it."
+- \u274C "Done! The comment has been posted on PR #123." (WRONG \u2014 it hasn't been posted yet)`
+});
+
+// ../../b4m-core/packages/services/dist/src/llm/agents/ServerAgentStore.js
+var ServerAgentStore = class {
+  constructor() {
+    const builtInAgents = [
+      // For now disable explore and plan agents as it is much faster if the parent llm handles this.
+      // ExploreAgent(),
+      // PlanAgent(),
+      CodeReviewAgent(),
+      ProjectManagerAgent(),
+      GithubManagerAgent()
+    ];
+    this.agents = new Map(builtInAgents.map((a) => [a.name, a]));
+  }
+  getAgent(name) {
+    return this.agents.get(name);
+  }
+  getAllAgents() {
+    return Array.from(this.agents.values());
+  }
+  getAgentNames() {
+    return Array.from(this.agents.keys());
+  }
+  hasAgent(name) {
+    return this.agents.has(name);
+  }
+  /**
+   * Get the deduplicated list of MCP server names that are exclusive to agents.
+   * Derived from each agent's `exclusiveMcpServers` field.
+   */
+  getExclusiveMcpServers() {
+    const servers = /* @__PURE__ */ new Set();
+    for (const agent of this.agents.values()) {
+      if (agent.exclusiveMcpServers) {
+        for (const s of agent.exclusiveMcpServers) {
+          servers.add(s);
+        }
+      }
+    }
+    return Array.from(servers);
+  }
+};
+var serverAgentStore = new ServerAgentStore();
 
 // ../../b4m-core/packages/services/dist/src/llm/ChatCompletionProcess.js
 import throttle2 from "lodash/throttle.js";
@@ -15079,7 +15313,7 @@ var MCPClient = class {
   onStderrLine;
   tools = [];
   serverName;
-  constructor({ envVariables, name, command, args, suppressStderr = false, onStderrLine }) {
+  constructor({ envVariables, name, selectedRepositories, command, args, suppressStderr = false, onStderrLine }) {
     this.mcp = new Client2({ name: "mcp-client-cli", version: "1.0.0" });
     this.envVariables = [...envVariables];
     this.serverName = name;
@@ -15087,6 +15321,13 @@ var MCPClient = class {
     this.customArgs = args;
     this.suppressStderr = suppressStderr;
     this.onStderrLine = onStderrLine;
+    if (name === "github" && selectedRepositories) {
+      const reposJson = JSON.stringify(selectedRepositories);
+      this.envVariables.push({
+        key: "SELECTED_REPOSITORIES",
+        value: reposJson
+      });
+    }
   }
   async connectToServer() {
     try {

package/dist/commands/doctorCommand.js

@@ -3,7 +3,7 @@ import {
   fetchLatestVersion,
   forceCheckForUpdate,
   package_default
-} from "../chunk-VKY5MM7G.js";
+} from "../chunk-4KXRKTAG.js";
 
 // src/commands/doctorCommand.ts
 import { execSync } from "child_process";

package/dist/commands/headlessCommand.js

@@ -36,7 +36,7 @@ import {
   isReadOnlyTool,
   loadContextFiles,
   setWebSocketToolExecutor
-} from "../chunk-4KRFJ4XO.js";
+} from "../chunk-AIXD7O5A.js";
 import "../chunk-BDQBOLYG.js";
 import "../chunk-J3YSVA6W.js";
 import "../chunk-GQGOWACU.js";

package/dist/commands/updateCommand.js

@@ -2,7 +2,7 @@
 import {
   forceCheckForUpdate,
   package_default
-} from "../chunk-VKY5MM7G.js";
+} from "../chunk-4KXRKTAG.js";
 
 // src/commands/updateCommand.ts
 import { execSync } from "child_process";

package/dist/index.js

@@ -46,7 +46,7 @@ import {
   setWebSocketToolExecutor,
   substituteArguments,
   warmFileCache
-} from "./chunk-4KRFJ4XO.js";
+} from "./chunk-AIXD7O5A.js";
 import "./chunk-BDQBOLYG.js";
 import "./chunk-J3YSVA6W.js";
 import "./chunk-GQGOWACU.js";
@@ -62,7 +62,7 @@ import {
 import {
   checkForUpdate,
   package_default
-} from "./chunk-VKY5MM7G.js";
+} from "./chunk-4KXRKTAG.js";
 import {
   selectActiveBackgroundAgents,
   useCliStore

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bike4mind/cli",
-  "version": "0.2.38-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
+  "version": "0.2.38-fix-delegate-agent-timeout.20159+f9dcbadd4",
   "type": "module",
   "description": "Interactive CLI tool for Bike4Mind with ReAct agents",
   "license": "UNLICENSED",
@@ -114,10 +114,10 @@
   },
   "devDependencies": {
     "@bike4mind/agents": "0.1.0",
-    "@bike4mind/common": "2.58.1-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
-    "@bike4mind/mcp": "1.32.6-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
-    "@bike4mind/services": "2.54.2-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
-    "@bike4mind/utils": "2.11.1-fix-remove-unused-sharp-dependency.20166+24ec79c7f",
+    "@bike4mind/common": "2.58.1-fix-delegate-agent-timeout.20159+f9dcbadd4",
+    "@bike4mind/mcp": "1.32.6-fix-delegate-agent-timeout.20159+f9dcbadd4",
+    "@bike4mind/services": "2.54.2-fix-delegate-agent-timeout.20159+f9dcbadd4",
+    "@bike4mind/utils": "2.11.1-fix-delegate-agent-timeout.20159+f9dcbadd4",
     "@types/better-sqlite3": "^7.6.13",
     "@types/diff": "^5.0.9",
     "@types/jsonwebtoken": "^9.0.4",
@@ -135,5 +135,5 @@
   "optionalDependencies": {
     "@vscode/ripgrep": "^1.17.0"
   },
-  "gitHead": "24ec79c7fc8a7534bb5f38b842064006f0453264"
+  "gitHead": "f9dcbadd4b2b22f860ced2edae7065406077e359"
 }