pace

To persist analysis pace mode across phase transitions, write the selected mode to session_state.yaml. This ensures the configured visibility setting survives resume-pipeline and /continue workflows without resetting.

Controlling phase banner visibility during L3+ reviews involves setting a guided, narrated, or autopilot mode. The chosen mode applies at the next phase boundary, preventing disruptive mid-phase banner state changes.

Yes, you can safely update session_state.yaml without losing data. The process reads existing YAML content, validates the new input, and writes changes atomically to preserve all other session data even during interruptions.

Atomic YAML writing prevents workflow corruption by ensuring the session state file remains valid even if interruptions occur. It safely reads, validates, and writes the pace mode while preserving other session data.

You should not change the pace mode during an active phase because the setting only applies at the next phase boundary. Altering it mid-phase prevents immediate banner state changes and avoids disrupting the current workflow.

To query the current pace mode stored in your session state, use the dedicated query option. This reads the existing YAML file safely and returns the active mode configured for your L3+ analyses.