@link-assistant/hive-mind 1.12.0 → 1.14.0

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # @link-assistant/hive-mind
 
+## 1.14.0
+
+### Minor Changes
+
+- 3a48254: Add configurable experiments/examples folder paths with ability to disable
+
+  New CLI options for both `solve` and `hive` commands:
+  - `--prompt-experiments-folder <path>`: Path to experiments folder used in system prompt. Set to empty string to disable experiments folder prompt. Default: `./experiments`
+  - `--prompt-examples-folder <path>`: Path to examples folder used in system prompt. Set to empty string to disable examples folder prompt. Default: `./examples`
+
+  Features:
+  - Backwards compatible: defaults to `./experiments` and `./examples` as before
+  - Custom paths: Specify custom folder paths for experiments and examples
+  - Disable functionality: Set to empty string (`''`) to disable the experiments/examples prompt section entirely
+  - Works with all AI tools: claude, opencode, codex, and agent
+
+## 1.13.0
+
+### Minor Changes
+
+- 03adcb6: Add --auto-merge and --auto-restart-until-mergable options for autonomous PR management
+
+  New CLI options:
+  - `--auto-merge`: Automatically merge the pull request when CI passes and PR is mergeable. Implies --auto-restart-until-mergable.
+  - `--auto-restart-until-mergable`: Auto-restart the AI agent until PR becomes mergeable (no iteration limit). Restarts on new comments from non-bot users, CI failures, merge conflicts, or uncommitted changes. Does NOT auto-merge.
+
+  Features:
+  - Non-bot comment detection with configurable bot patterns
+  - Automatic detection of CI/CD status and merge readiness
+  - Continuous monitoring loop with configurable check intervals
+  - Progress and status reporting throughout the process
+  - Graceful handling of API errors with exponential backoff
+  - Session data tracking for accurate pricing across iterations
+
 ## 1.12.0
 
 ### Minor Changes

package/README.md

@@ -106,7 +106,40 @@ bun install -g @link-assistant/hive-mind
 npm install -g @link-assistant/hive-mind
 ```
 
-### Docker Installation
+### Installing Docker
+
+If you don't have Docker installed yet, follow these steps to install Docker Engine on Ubuntu:
+
+```bash
+# Install prerequisites
+sudo apt update
+sudo apt install ca-certificates curl
+
+# Add Docker's official GPG key
+sudo install -m 0755 -d /etc/apt/keyrings
+sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
+sudo chmod a+r /etc/apt/keyrings/docker.asc
+
+# Add Docker repository
+sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
+Types: deb
+URIs: https://download.docker.com/linux/ubuntu
+Suites: $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}")
+Components: stable
+Signed-By: /etc/apt/keyrings/docker.asc
+EOF
+
+# Install Docker
+sudo apt update
+sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
+
+# Verify installation
+sudo docker run hello-world
+```
+
+**For other operating systems** or detailed instructions, see the [official Docker documentation](https://docs.docker.com/engine/install/).
+
+### Using Docker
 
 Run the Hive Mind using Docker for safer local installation - no manual setup required:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@link-assistant/hive-mind",
-  "version": "1.12.0",
+  "version": "1.14.0",
   "description": "AI-powered issue solver and hive mind for collaborative problem solving",
   "main": "src/hive.mjs",
   "type": "module",

package/src/agent.prompts.lib.mjs

@@ -4,6 +4,7 @@
  */
 
 import { getArchitectureCareSubPrompt } from './architecture-care.prompts.lib.mjs';
+import { getExperimentsExamplesSubPrompt } from './experiments-examples.prompts.lib.mjs';
 
 /**
  * Build the user prompt for Agent
@@ -137,9 +138,7 @@ ${workspaceInstructions}General guidelines.
    - When CI is failing, make sure you download the logs locally and carefully investigate them.
    - When a code or log file has more than 1500 lines, read it in chunks of 1500 lines.
    - When facing a complex problem, do as much tracing as possible and turn on all verbose modes.
-   - When you create debug, test, or example/experiment scripts for fixing, always keep them in an examples and/or experiments folders so you can reuse them later.
-   - When testing your assumptions, use the experiment scripts, and add it to experiments folder.
-   - When your experiments can show real world use case of the software, add it to examples folder.
+${getExperimentsExamplesSubPrompt(argv)}
    - When you face something extremely hard, use divide and conquer — it always helps.
 
 Initial research.

package/src/claude.prompts.lib.mjs

@@ -4,6 +4,7 @@
  */
 
 import { getArchitectureCareSubPrompt } from './architecture-care.prompts.lib.mjs';
+import { getExperimentsExamplesSubPrompt } from './experiments-examples.prompts.lib.mjs';
 
 /**
  * Build the user prompt for Claude
@@ -163,9 +164,7 @@ ${workspaceInstructions}General guidelines.
       Note: If user says "failing" but tools show "passing", this might indicate stale data - consider downloading fresh logs and checking timestamps to resolve the discrepancy.
    - When a code or log file has more than 1500 lines, read it in chunks of 1500 lines.
    - When facing a complex problem, do as much tracing as possible and turn on all verbose modes.
-   - When you create debug, test, or example/experiment scripts for fixing, always keep them in an examples and/or experiments folders so you can reuse them later.
-   - When testing your assumptions, use the experiment scripts, and add it to experiments folder.
-   - When your experiments can show real world use case of the software, add it to examples folder.
+${getExperimentsExamplesSubPrompt(argv)}
    - When you face something extremely hard, use divide and conquer — it always helps.
 
 Initial research.

package/src/codex.prompts.lib.mjs

@@ -4,6 +4,7 @@
  */
 
 import { getArchitectureCareSubPrompt } from './architecture-care.prompts.lib.mjs';
+import { getExperimentsExamplesSubPrompt } from './experiments-examples.prompts.lib.mjs';
 
 /**
  * Build the user prompt for Codex
@@ -144,9 +145,7 @@ ${workspaceInstructions}General guidelines.
       Note: If user says "failing" but tools show "passing", this might indicate stale data - consider downloading fresh logs and checking timestamps to resolve the discrepancy.
    - When a code or log file has more than 1500 lines, read it in chunks of 1500 lines.
    - When facing a complex problem, do as much tracing as possible and turn on all verbose modes.
-   - When you create debug, test, or example/experiment scripts for fixing, always keep them in an examples and/or experiments folders so you can reuse them later.
-   - When testing your assumptions, use the experiment scripts, and add it to experiments folder.
-   - When your experiments can show real world use case of the software, add it to examples folder.
+${getExperimentsExamplesSubPrompt(argv)}
    - When you face something extremely hard, use divide and conquer — it always helps.
 
 Initial research.

package/src/experiments-examples.prompts.lib.mjs

@@ -0,0 +1,48 @@
+/**
+ * Experiments and examples folder prompts module
+ * Handles building configurable prompts for experiments/examples folders
+ *
+ * @see https://github.com/link-assistant/hive-mind/issues/1199
+ */
+
+/**
+ * Build the experiments/examples sub-prompt based on configuration
+ * @param {Object} argv - Command line arguments
+ * @param {string} argv.promptExperimentsFolder - Path to experiments folder (empty string to disable)
+ * @param {string} argv.promptExamplesFolder - Path to examples folder (empty string to disable)
+ * @returns {string} The formatted sub-prompt for experiments/examples folders
+ */
+export const getExperimentsExamplesSubPrompt = argv => {
+  const experimentsFolder = argv?.promptExperimentsFolder ?? './experiments';
+  const examplesFolder = argv?.promptExamplesFolder ?? './examples';
+
+  // If both are disabled, return empty string
+  if (!experimentsFolder && !examplesFolder) {
+    return '';
+  }
+
+  const lines = [];
+
+  // Both folders are enabled (with their respective paths)
+  if (experimentsFolder && examplesFolder) {
+    lines.push(`   - When you create debug, test, or example/experiment scripts for fixing, always keep them in an ${examplesFolder} and/or ${experimentsFolder} folders so you can reuse them later.`);
+    lines.push(`   - When testing your assumptions, use the experiment scripts, and add it to ${experimentsFolder} folder.`);
+    lines.push(`   - When your experiments can show real world use case of the software, add it to ${examplesFolder} folder.`);
+  }
+  // Only experiments folder is enabled
+  else if (experimentsFolder) {
+    lines.push(`   - When you create debug or test scripts for fixing, always keep them in ${experimentsFolder} folder so you can reuse them later.`);
+    lines.push(`   - When testing your assumptions, use the experiment scripts, and add it to ${experimentsFolder} folder.`);
+  }
+  // Only examples folder is enabled
+  else if (examplesFolder) {
+    lines.push(`   - When you create example scripts that show real world use cases, keep them in ${examplesFolder} folder.`);
+    lines.push(`   - When your experiments can show real world use case of the software, add it to ${examplesFolder} folder.`);
+  }
+
+  return lines.join('\n');
+};
+
+export default {
+  getExperimentsExamplesSubPrompt,
+};

package/src/hive.config.lib.mjs

@@ -239,6 +239,16 @@ export const createYargsConfig = yargsInstance => {
       alias: 'w',
       default: false,
     })
+    .option('auto-merge', {
+      type: 'boolean',
+      description: 'Automatically merge the pull request when the working session is finished and all CI/CD statuses pass and PR is mergeable. Implies --auto-restart-until-mergable.',
+      default: false,
+    })
+    .option('auto-restart-until-mergable', {
+      type: 'boolean',
+      description: 'Auto-restart until PR becomes mergeable (no iteration limit). Restarts on new comments from non-bot users, CI failures, merge conflicts, or other issues. Does NOT auto-merge.',
+      default: false,
+    })
     .option('issue-order', {
       type: 'string',
       description: 'Order issues by publication date: "asc" (oldest first) or "desc" (newest first)',
@@ -291,6 +301,16 @@ export const createYargsConfig = yargsInstance => {
       description: 'Include prompt to check related/sibling pull requests when studying related work. Enabled by default, use --no-prompt-check-sibling-pull-requests to disable.',
       default: true,
     })
+    .option('prompt-experiments-folder', {
+      type: 'string',
+      description: 'Path to experiments folder used in system prompt. Set to empty string to disable experiments folder prompt. Default: ./experiments',
+      default: './experiments',
+    })
+    .option('prompt-examples-folder', {
+      type: 'string',
+      description: 'Path to examples folder used in system prompt. Set to empty string to disable examples folder prompt. Default: ./examples',
+      default: './examples',
+    })
     .option('prompt-architecture-care', {
       type: 'boolean',
       description: '[EXPERIMENTAL] Include guidance for managing REQUIREMENTS.md and ARCHITECTURE.md files. When enabled, agents will update these documentation files when changes affect requirements or architecture.',

package/src/hive.mjs

@@ -770,7 +770,11 @@ if (isDirectExecution) {
             if (argv.promptIssueReporting) args.push('--prompt-issue-reporting');
             if (argv.promptCaseStudies) args.push('--prompt-case-studies');
             if (argv.promptPlaywrightMcp !== undefined) args.push(argv.promptPlaywrightMcp ? '--prompt-playwright-mcp' : '--no-prompt-playwright-mcp');
+            if (argv.promptExperimentsFolder !== undefined) args.push('--prompt-experiments-folder', argv.promptExperimentsFolder);
+            if (argv.promptExamplesFolder !== undefined) args.push('--prompt-examples-folder', argv.promptExamplesFolder);
             if (argv.executeToolWithBun) args.push('--execute-tool-with-bun');
+            if (argv.autoMerge) args.push('--auto-merge');
+            if (argv.autoRestartUntilMergable) args.push('--auto-restart-until-mergable');
             // Log the actual command being executed so users can investigate/reproduce
             await log(`   📋 Command: ${solveCommand} ${args.join(' ')}`);
 

package/src/opencode.prompts.lib.mjs

@@ -4,6 +4,7 @@
  */
 
 import { getArchitectureCareSubPrompt } from './architecture-care.prompts.lib.mjs';
+import { getExperimentsExamplesSubPrompt } from './experiments-examples.prompts.lib.mjs';
 
 /**
  * Build the user prompt for OpenCode
@@ -139,9 +140,7 @@ General guidelines.
    - When CI is failing, make sure you download the logs locally and carefully investigate them.
    - When a code or log file has more than 1500 lines, read it in chunks of 1500 lines.
    - When facing a complex problem, do as much tracing as possible and turn on all verbose modes.
-   - When you create debug, test, or example/experiment scripts for fixing, always keep them in an examples and/or experiments folders so you can reuse them later.
-   - When testing your assumptions, use the experiment scripts, and add it to experiments folder.
-   - When your experiments can show real world use case of the software, add it to examples folder.
+${getExperimentsExamplesSubPrompt(argv)}
    - When you face something extremely hard, use divide and conquer — it always helps.
 ${workspaceInstructions}
 Initial research.