decision-hold-lifecycle

Persist unresolved user decisions by recording them as durable hold items in an agent decisions file. This ensures open choices requiring user input remain available across context compaction and session restarts until they are resolved.

Persistent decision tracking captures user-dependent choices with stable keys and durable storage. You need it when agent workflows discover open choices that require user input before implementation or completion can proceed.

Record each unresolved choice as a durable hold with a stable key, title, reason, and project path in the agent decisions file. The hold remains open until the user's resolution is recorded, supporting idempotent updates and reliable follow-through.

Yes, durable holds persist unresolved decisions to the agent decisions file so they remain available across session restarts. Surfaced status checks and idempotent retry behavior ensure reliable session recovery and follow-through.

Yes, decision hold lifecycle supports idempotent updates by keeping holds open until the user's answer is recorded. This ensures repeated or retried user input resolves the decision reliably without duplicating workflow state.

Persistent holds require stable decision keys and durable storage in the agent decisions file. They apply only to genuine user-dependent choices discovered during task execution, not to autonomous agent decisions that do not require user input.