Skip to main content

bind_call_conversation

Function bind_call_conversation 

Source
pub fn bind_call_conversation(raw: &str, call: &HookCall)
Expand description

Answer as the conversation call came from, until the next bind. A payload’s conversation_id is the CURSOR_CONVERSATION_ID the runner stamps on that conversation’s shells, so the hook resolves the holder ljos sitting resolved there. The hook’s own environment may belong to another conversation and is not read for a non-empty id. A blank conversation_id names nothing of its own: the id is read from the environment in [session_actor]’s order. A non-empty conversation_id that is unusable names nobody, and the environment does not stand in for it. Only conversation_id names a call’s conversation here, never session_id. Another runner’s payload leaves the environment as the source, unless it carries a session key that names nobody, which the gate refuses. A payload whose id fields are all missing or blank, with a null transcript path and an environment that names no session, is unattributed.