Concurrency without Model Changes: Future-based Asynchronous Function Calling for LLMs

Guangyu Feng, Huanzhi Mao, Prabal Dutta, Joseph E. Gonzalez
5/14/2026
cs.CLcs.AIcs.LG

No confident code implementation found for this paper.

Abstract

Function calling, also known as tool use, is a core capability of modern LLM agents but is typically constrained by synchronous execution semantics. Under these semantics, LLM decoding is blocked until each function call completes, resulting in increasing end-to-end latency. In this work, we introduce AsyncFC, a pure execution-layer framework that decouples LLM decoding from function execution, enabling overlap between model decoding and function execution as well as inter-function parallelism when dependencies permit. AsyncFC layers over existing models and unmodified function implementations, requiring no fine-tuning or changes to the standard synchronous function-calling protocol. On coding tasks, AsyncFC achieves a $1.4\times$ end-to-end speedup while preserving task accuracy. Furthermore, these results reveal that LLMs possess a native capability to reason over symbolic futures that represent unresolved execution results, enabling an asynchronous paradigm for model-tool interaction.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{feng2026concurrency,
  title  = {Concurrency without Model Changes: Future-based Asynchronous Function Calling for LLMs},
  author = {Guangyu Feng and Huanzhi Mao and Prabal Dutta and Joseph E. Gonzalez},
  year   = {2026},
  eprint = {2605.15077},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2605.15077v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2605.15077.svg)](https://codeofpaper.com/paper/2605.15077)

Discussion