conductor

Autonomous research loops can be orchestrated by reading system state, evaluating ongoing experiments, and dispatching new cycles. It coordinates parallel in-flight runs up to max_concurrent, enforcing safety gates and error recovery.

Director, Hypothesis, and Coder agent workflows can be automated autonomously. The orchestration evaluates finished runs, triggers new cycles, updates budget constraints, and logs results automatically across all agents.

Parallel task scheduling and state persistence are handled by reading system state and evaluating ongoing experiments. It dispatches new research cycles, updates records, and manages PRs seamlessly.

Autonomous cycles for experiment management can be started by executing a heartbeat. Running /conductor or /loop 60m /conductor triggers an autonomous cycle to coordinate state checks and dispatch runs.

Workflow orchestration for autoresearch supports end-to-end Matrix notifications and PR management. It coordinates state persistence, dispatches research cycles, and handles logging across Director, Hypothesis, and Coder agents.

A heartbeat conductor for autonomous research loops should not be used without safety gates or error recovery mechanisms. It requires managing multiple in-flight experiments, budget constraints, and logging across agents.