Skip to content

The fastest, cheapest, most efficient open-source agent harness. Run more than 500 agents on a $10 VPS.

docs(agent): clarify stop gate race window in resume comment

Steven Enamakel2f681c892d07
diff --git a/crates/openhuman-core/src/agent/orchestration/background_completions/parent_lifecycle.rs b/crates/openhuman-core/src/agent/orchestration/background_completions/parent_lifecycle.rs
index d7f195653e..0e560395ac 100644
--- a/crates/openhuman-core/src/agent/orchestration/background_completions/parent_lifecycle.rs
+++ b/crates/openhuman-core/src/agent/orchestration/background_completions/parent_lifecycle.rs
@@ -114,8 +114,8 @@ pub(crate) fn finish_stop_for_thread(ctx: &DispatchCtx, thread_id: &str, task_id
/// Reopen a thread's completion gate for a newly accepted user turn.
///
/// The Stop gate deliberately outlives registry cancellation, because a detached
-/// child may be between `tokio::spawn` and `running_subagents::register` when
-/// Stop is pressed. New task ids remain distinct from the stopped generation.
+/// child may be between driver admission and durable owner-row persistence
+/// when Stop is pressed. New task ids remain distinct from the stopped generation.
/// Only a thread this process stopped or cancelled pays for the durable resume
/// marker, so an ordinary chat message writes nothing.
pub(crate) fn resume_stopped_thread(ctx: &DispatchCtx, thread_id: &str) {