← Latest papers
🤖 machine learning

Building Interactive Real-Time Agents with Asynchronous I/O and Speculative Tool Calling

This paper proposes a framework combining Asynchronous I/O and Speculative Tool Calling to enable real-time, low-latency agentic interactions with complex multi-turn tool calling, achieving significant speedups for both cloud and edge-scale models while maintaining acceptable accuracy.

Original authors: Coleman Hooper, Minwoo Kang, Suhong Moon, Nicholas Lee, Eric Wen, John Wawrzynek, Michael W. Mahoney, Yakun Sophia Shao, Amir Gholami, Kurt Keutzer

Published 2026-05-14
📖 4 min read☕ Coffee break read

Original authors: Coleman Hooper, Minwoo Kang, Suhong Moon, Nicholas Lee, Eric Wen, John Wawrzynek, Michael W. Mahoney, Yakun Sophia Shao, Amir Gholami, Kurt Keutzer

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to give a complex set of instructions to a very smart, but slightly slow, assistant. In the old way of doing things (the "standard" method), you would have to wait until you finished speaking your entire sentence before the assistant could even start thinking about what to do. Then, if the assistant needed to look up a phone number or send a text, they would stop talking, go do that task, wait for the result, and then come back to tell you what happened. This back-and-forth creates a lot of silence and waiting, making the conversation feel clunky and unnatural.

This paper introduces a new way for AI agents to work that feels much more like a real-time human conversation. They call their method Asynchronous I/O and Speculative Tool Calling. Here is how it works using simple analogies:

1. The "Multitasking Chef" (Asynchronous I/O)

Think of a standard AI agent as a chef who can only do one thing at a time: they wait for you to finish ordering, then they chop vegetables, then they wait for the stove to heat up, then they cook.

The new method turns the AI into a multitasking chef.

  • While you are still talking: The chef starts chopping vegetables based on the first few words you say. They don't wait for you to finish the sentence.
  • While waiting for the stove: If the chef needs to wait for a tool (like a database lookup) to finish, they don't just stand there staring at the wall. They use that waiting time to start planning the next step or even start prepping the next ingredient.

In technical terms, this means the AI "decouples" its thinking from your speaking. It keeps working while waiting for information from you or from the outside world, rather than freezing in place.

2. The "Gambler with a Safety Net" (Speculative Tool Calling)

Sometimes, the AI has to make a guess. Imagine you say, "Call Joe..." and the AI knows it needs to call someone, but it doesn't know which Joe yet.

  • The Old Way: The AI would say, "Wait, which Joe?" and stop everything until you clarify.
  • The New Way: The AI makes a speculative move. It says, "Okay, I'm going to look up 'Joe Smith' just in case." It starts the process immediately.

The Safety Net:
The paper makes a crucial distinction between "safe" and "unsafe" guesses:

  • Safe Tools (Read-Only): If the AI is just looking up a phone number, it can do this immediately. If you later say, "Actually, I meant Joe Jones," the AI can just swap the number. Nothing bad happened.
  • Unsafe Tools (Write-Only): If the AI is about to send a text message or delete a file, it cannot just guess. It holds that action in a "pending" box. It prepares the message but waits for a final "green light" (confirmation that you are done speaking) before actually hitting "Send."

If the AI guesses wrong and you change your mind, it can simply cancel the pending action before it ever happens. This is like a chef starting to chop an onion but stopping immediately if you say, "Actually, I'm vegetarian today," before the knife touches the board.

3. The "Clock-Based Training"

To teach the AI to do this, the researchers didn't just tell it to "be faster." They built a special training gym with a clock.

  • In this gym, the AI is trained to expect that information (like your voice or a tool's answer) will arrive at specific, delayed moments.
  • The AI learns to keep working during those delays.
  • They also created fake "mistakes" in the training data where the AI guessed wrong early on, forcing it to learn how to fix those mistakes later without panicking.

The Results

The paper tested this on two types of AI:

  1. Big Cloud Models: When using powerful existing AI APIs (like OpenAI's), this method made them 1.3 to 1.7 times faster with only a tiny drop in accuracy.
  2. Small Edge Models: When they trained smaller AI models (like those that could run on a laptop) using their special "clock" method, these models became 1.6 to 2.2 times faster while maintaining high accuracy.

In summary: The paper shows how to stop AI agents from "pausing" while they think or wait. By letting them work while they wait, and letting them make safe guesses that can be corrected later, they can interact with humans in real-time, making voice assistants feel much more natural and responsive.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →