invoke posts one text to /rpc/receive on the conversation’s address and reads the reply back from the instance’s state stream. A run paused for an approval or canceled ends invoke with exit 1 and a line that says so; a run that produced no reply ends with run <id> completed without a reply on stderr and exit 0. None waits for a timeout. invoke carries no sender, so a fresh conversation’s memory profile is its own name, alice here; a conversation that was earlier given a from through rpc … receive keeps that sender as its profile.
Anything else that speaks the wire can do the same, the POST …/rpc/receive call on the address or the AgentClient. The RPC Methods is where the call lands in the managed harness.