ACP - Rename Await Feature

[pilartomas]

In ACP, the agent may pause a run, enter a state awaiting with await description that contains information how to resume the run. The client then later uses resume endpoint to continue the run with await payload.

The feature can be in essence described as

Agent pauses a run and waits for additional data/confirmation from the client (agent/human/...)

The name await is a keyword in many programming languages making it difficult to work with. It can also be confusing for LLMs for similar reasons. We'd like to choose a better name for this feature and payloads.

[JanPokorny]

My suggestion is handback. Like "handoff", which is already understood in the context of LLM agents as handing over the control to a sub-agent, but reverse -- handing the control back to the caller, hence "handback". It's not a common word (although it does have a wiktionary entry) but should be easily understood.

[pilartomas]

I think that's a good contender considering LLM is likely to be prompted with this as a tool name.

[matoushavlena]

Llamastack uses awaiting_input, which is very close to the original await proposal.

[pilartomas]

So the state would remain awaiting. The description field in the run object would change to awaiting_input and resume payload field to awaiting_output? Integration as LLM tool would likely use await name in such case, which might be problematic.

[pilartomas]

We've decided to keep await as the overarching name and use derived names only. Meaning code will work with awaiting, await_request and await_resume names.