Runtime parameter reference

This page is the entry-point and configuration reference for cycle, autoexec, and lifecycle. For startup, state interpretation, and recovery, see Resident operation and task queues.

Resident operation is for workflows with established scope, validation, and monitoring. Distinguish material-consuming cycles, the autoexec queue, and lifecycle management. They are not one loop switch.

Configure the execution entry point and task scope before enabling continuous operation.

Choose an execution shape

Entry	Purpose	Confirm first
`evolver cycle`	Consume material through a finite evolution run	Repository, target, material source, runner, and validation commands
`evolver cycle watch`	Watch material and process later cycles	Scope, state file, iteration limit, and stopping conditions
`evolver autoexec [home]`	Resident queue processing and background maintenance	allowedRoots, runner, timeout, and external activity
`evolver lifecycle`	Start, stop, inspect, or install background services	Service ownership, configuration path, and shutdown method

Inspect evolver cycle capabilities --json first. Built-in Claude, Codex, and Cursor execution is disabled; Gemini and the independent llm file executor are experimental. A runner appearing in help is not proof of accepted execution support.

Configure autoexec

Configuration lives in the selected home’s autoexec/config.json:

Field	Default	Meaning
`allowedRoots`	`[]`	Repository allowlist; an empty list blocks queued execution.
`pollMs`	`30000`	Base polling interval in milliseconds.
`timeoutMs`	`600000`	Execution timeout in milliseconds.
`runner`	`claude`	Runner selection; the experimental `gemini` and `llm` paths can consume the execution queue.
`workflowValidationProfiles`	`{}`	Named sets of workflow validation commands.

A healthy resident process does not mean code is being changed. The default allowlist is empty and the default runner’s execution queue is disabled. Inspect maintenance activity separately from execution results.

Decide whether Hub task acceptance is allowed before allowlisting a repository. EVOLVER_TASK_RECEIVER=0 blocks new claims; do not substitute off or false, because only the string 0 disables this switch. Otherwise the receiver enables when node, client, repository, and queue are available. Purchasing, auto-delivery, and task acceptance have separate controls. See Worker mode.

Idle cadence and exploration

Resident operation is idle-aware by default. EVOLVER_IDLE_AWARE=0 uses a fixed base cadence. Idle recommendations use thresholds of 300 and 1800 seconds; an unavailable idle reading keeps normal cadence. Single-flight prevents overlapping passes.

Exploration finds new verifiable leads; it does not expand authority. When no Gene matches, the proposed approach still needs a bounded objective and validation commands. Do not treat v1 tables of EVOLVER_EXPLORE_* or EVOLVE_MIN_INTERVAL as active configuration for this workflow.

Roll out, stop, and recover

Observe success, no-work, and failure paths in an isolated repository. Record cycle state, logs, and file changes before extending runtime. Inspect managed services with evolver lifecycle status; closing a foreground terminal alone is insufficient.

After stopping, reconcile unfinished cycles, queued work, and remote results. Use Change boundaries to verify recovery before retrying work that already caused side effects.