TL;DR
Synapse-Control is a lightweight runtime for LLM agents that makes experience reuse efficient by replacing expensive generative failure diagnosis with a fast 1.7B parameter classifier. By using "micro-contracts" to provide actionable guidance and a stateful "Prompt Value Table" to manage delivery, it improves task success by nearly 30% over unassisted agents while cutting auxiliary inference time in half compared to previous state-of-the-art systems.
What Problem Does This Paper Address?
Large Language Model (LLM) agents often struggle with complex, tool-based tasks where they must navigate APIs or web interfaces. To improve reliability, researchers have developed "experience reuse" systems that allow agents to learn from past failures.
However, existing systems like Sentry introduce a significant "computational tax." Before an agent can receive a helpful lesson, a large model must first examine the execution trajectory and generate a text-based diagnosis. As shown in Figure 2, this auxiliary work can add over 20% overhead to the total request time. The authors identify a gap: we need a way to connect agents with relevant experience without the high cost and latency of generative diagnosis.
Methods
The core innovation of Synapse-Control is exploiting computational asymmetry: it is much cheaper to judge the suitability of a pre-retrieved suggestion than it is to generate a diagnosis from scratch.
The architecture (detailed in Figure 3) consists of three main components:
- Micro-contracts: Instead of storing entire task programs, the system uses "micro-contracts"—short, actionable statements of local constraints (e.g., "This API call requires a 'red' option to be selected"). This gives the agent concrete facts while leaving high-level planning to the actor.
- Lightweight Classifier: The system replaces the large generative "detector" with a fine-tuned 1.7B parameter classifier (Qwen-1.7B). It scores up to five candidate suggestions as Helpful, Irrelevant, or Harmful based on the current execution state.
- Prompt Value Table (PVT): This stateful component manages the "delivery" of hints. It tracks which suggestions were sent, monitors feedback (did the agent succeed after the hint?), and enforces token budgets and "cooldown" periods to prevent the system from nagging the agent with redundant advice.
Datasets
The authors evaluated Synapse-Control on two primary benchmarks:
- AppWorld: A complex environment for stateful API programming involving 168 distinct tasks.
- WebShop: A web-based shopping benchmark where agents must search, inspect, and purchase products.
To train the 1.7B classifier, they used a 32B teacher model to label state-suggestion pairs collected from both unassisted and recovery-assisted trajectories (Figure 4).
Key Insights and Ideas
- Classification > Generation: You don't need a massive model to diagnose a failure if you can simply have a small model verify if a known "fix" applies to the current state. This shift from generation to assessment is the primary driver of efficiency.
- Actionable Facts over General Principles: Figure 5 illustrates that providing a "micro-contract" (concrete interface facts) is far more effective than a "short principle" (general instructions). Agents perform better when told what constraint to satisfy rather than how to think.
- Governance is Essential: Without the PVT, an experience reuse system might repeatedly send the same hint even if the agent is ignoring it. The PVT acts as a "control plane," ensuring that guidance is timely, non-redundant, and stays within a token budget.
Key Results
Synapse-Control demonstrated that "less is more" when it comes to the control plane:
- Higher Success: Across 1,308 attempts, it achieved 270 successes—a 29.8% improvement over the base agent and outperforming Sentry (256 successes).
- Massive Speedup: It reduced auxiliary control time by 50.2% in AppWorld and 51.0% in WebShop compared to Sentry.
- Efficiency: The system replaced 4,987 expensive generative diagnosis calls with lightweight classifier passes.
- Token Savings: It achieved a 27.5% reduction in total tokens used per successful completion relative to the base agent.
Limitations and Future Work
- Domain Onboarding: While the authors estimate only a few person-hours are needed to define templates for a new domain, it still requires manual effort. Future work could involve using LLMs to automatically extract micro-contracts from OpenAPI/Swagger documentation.
- Teacher Dependency: The system relies on a larger (32B) teacher model for initial data labeling, which might be a bottleneck for some researchers.
- Complex Planning: In AppWorld, some tasks failed because the agent hit a hard action limit (60 steps). While Synapse-Control helps with local interface errors, it doesn't solve the problem of agents getting lost in extremely long, multi-step workflows.
Summary updated