0.9.6

dagent 0.9.6 simplifies execution bounds around one Agent-owned max_steps setting and adds cooperative steering for active tool-agent runs.

Added

• Added await Runner.steer(run_id, input) with FIFO guidance delivery for active root ToolAgent runs and AutoAgent runs routed to the tool-agent path.
• Added typed steer.queued, steer.applied, and steer.discarded stream events.

Changed

• ToolAgent, AutoAgent, and DagAgent now share one max_steps field with a default of 888.
• Removed Runner-level execution-limit parameters and the duplicate max_cycles agent configuration.
• Agent DAG nodes use the registered child ToolAgent.max_steps as their execution bound.
• Static DAG plans reject max_steps; Map and Loop structural bounds remain unchanged.
• Checkpoint writes now use V6 execution metadata and tighten V4/V5 migration validation.
• API and Web preset defaults now align with the Agent-owned 888-step default.

Compatibility and migration

• Replace DagAgent(max_cycles=n) and AutoAgent(max_cycles=n) with max_steps=n.
• Move former Runner execution limits to the relevant Agent configuration.
• Legacy V4/V5 checkpoints retain explicit historical ToolAgent bounds. To resume a checkpoint created with the old implicit child-agent default, register that child with ToolAgent(max_steps=8).
• Persisted Agent-node invocation max_steps values are ignored with a deprecation warning because bounds are now owned by registered agents.

Known limitations

• Steering is intentionally available only for active root tool-agent execution. DAG execution, validation, review, completed runs, and unknown runs reject steering.
• Steering queues are ephemeral and are not persisted in checkpoints.

Verification

• Python suite: 1072 passed, 3 skipped.
• Web suite: 125 passed.
• Web production build completed.
• Wheel and source distribution built successfully and passed Twine metadata checks.

See the English and Simplified Chinese migration guides for detailed upgrade instructions.