flight505-marketplace

Generate and open the harness run dashboard. Reads .harness/*.json state files, builds a self-contained HTML file, and opens it in the browser. Use when the user asks to see the dashboard, check run status, or view experiment history. For live monitoring during a run, suggest /loop 30s /harness:dashboard.

Analyze the current project for autoresearch optimization opportunities. Scans the project, identifies candidates matching the keep/revert loop pattern (single mutable artifact, scalar metric, fixed time budget, repeatable execution), and presents ready-to-run suggestions with workflow.yaml snippets. Use when the user asks what they can optimize, what to autoresearch, or how to apply the optimization loop to their project.

Approve or reject a pending approval gate in a harness workflow. Used when a conductor run pauses at a type: approval phase.

Interactive workflow builder — helps create workflow.yaml files for the harness orchestrator. The ONE interactive entry point. Use when user wants to build a harness workflow, create a pipeline, or compose subsystems together.

Match a task description to the best default workflow, collect the required values interactively, write .harness/workflow.yaml with everything filled in, and hand off to /harness:run. Full path from description to ready-to-run — no manual file copying or placeholder editing.

Signal that an ultraplan phase's plan has been saved and the conductor can resume. Used after the user reviews and teleports a plan from Claude Code on the web.

Configure harness optimize-subsystem hardware targets — Apple Silicon (MLX), NVIDIA server (CUDA), or RunPod cloud GPU. One-time setup stored persistently. Use when user mentions hardware setup, SSH targets, GPU configuration, or says 'configure optimization targets'.