Recommend and Continue

Recommend and Continue is the official way to advance an existing Technical Session. Both actions use POST /v1/history/{session_id}/orchestrate and HistoryOrchestrateRequest.

Recommend first

curl --request POST \
  "$IVORLEAF_API_BASE_URL/v1/history/$SESSION_ID/orchestrate" \
  --header "Authorization: Bearer $IVORLEAF_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"intent":"recommend"}'

The response model guarantees session_id, mode, and orchestration. Source-derived orchestration fields include recommendations, recommended_action, recommended_title, reason, last_recommendation, warnings, and next_step. A recommendation is saved when available.

Continue second

curl --request POST \
  "$IVORLEAF_API_BASE_URL/v1/history/$SESSION_ID/orchestrate" \
  --header "Authorization: Bearer $IVORLEAF_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"intent":"continue"}'

intent: "continue" maps to execution mode and uses the saved or highest-ranked recommendation. Execution details can appear in orchestration.continuation, executed_actions, and chain.

Validation can stop continuation

If the workflow validation risk or experience memory requires human review, Continue can return an executed action with status: "skipped" and a warning instead of running the recommendation. Treat this as a control signal, not a transient error.

Advanced request fields—requested_action, execute, trigger, source, auto_chain, and max_chain_steps—are part of the current schema but intentionally outside the primary integration path.