hub-run

Topics in the source

• /hub-run — One-Shot Lifecycle
• Usage
• Parameters
• What It Does
• Step 1: Initialize
• Step 2: Capture Baseline
• Step 3: Spawn Agents
• Step 4: Wait and Monitor

Run the full AgentHub lifecycle in one command: initialize, capture baseline, spawn agents, evaluate results, and merge the winner. | Parameter | Required | Description | |-----------|----------|-------------| | --task | Yes | Task description for agents | | --agents | No | Number of parallel agents (default: 3) | | --eval | No | Eval command to measure results (skip for LLM judge mode) | | --metric | No | Metric name to extract from eval output (required if --eval given) | | --direction | No | lower or higher — which direction is better (required if --metric given) | | --template | No | Agent template: optimizer, refactorer, test-writer, bug-fixer | Execute these steps sequentially: Run /hub-init with the provided arguments: Display the session ID to the user. If --eval was provided: 1. Run the eval command in the current working directory 2. Extract the metric value from stdout 3. Display: Baseline captured: {metric} = {value} 4. Append baseline: {value} to .agenthub/sessions/{session-id}/config.yaml If no --eval was provided, skip this step. Run /agenthub:spawn with the session ID. If --template was provided, use the template dispatch prompt from ../agenthub/references/agent-tem

This is an excerpt. Refer to the complete source and its current requirements.