Adapting the Interface, Not the Model: Runtime Harness Adaptation for Deterministic LLM Agents
summary
The gist
The gist The LIFE-HARNESS framework proposes adapting a lifecycle-aware runtime harness to improve frozen LLM agents by evolving reusable interface interventions from training trajectories, rather
In short
LIFE-HARNESS improves frozen LLM agents by adapting their runtime harness instead of updating model weights. It evolves from training failures into reusable interventions across four lifecycle layers—environment contract, procedural skill, action realization, and trajectory regulation. This approach targets reusable environment structure to boost performance without retraining the core model.
Key concepts
- Agent Architecture
- An LLM agent is a combination of a language model and a runtime harness. The harness manages how the model observes the world, uses tools, executes actions, interprets feedback, and controls its path. Performance issues often arise from mismatches between the model's understanding and this operational interface.
- LIFE-HARNESS Framework
- This is a lifecycle-aware runtime harness that modifies the agent's operational interface based on recurring interaction failures found in training data. It does not change the LLM model itself, but instead evolves reusable fixes across four distinct layers to improve agent behavior in deterministic settings.
- Lifecycle Layers
- These are four specific stages of an agent's operation: Environment Contract (before interaction), Procedural Skill (during task conditioning), Action Realization (after outputting an action), and Trajectory Regulation (after receiving feedback). LIFE-HARNESS applies learned interventions to each layer to guide the agent effectively.
- Model-Environment Interface Mismatch
- The paper argues that failures in deterministic domains usually stem from poor communication between the model and its environment, not a lack of reasoning ability. LIFE-HARNESS focuses on fixing this boundary by evolving the harness—the interface—to better match the requirements of the target environment.
Terminology used across episodes
This episode discusses
- Adapting the Interface, Not the Model: Runtime Harness Adaptation for Deterministic LLM Agents · Paper Radio
- PromptWizard: Task-Aware Prompt Optimization Framework
- GEPA: Reflective Prompt Evolution Can Outperform Reinforcement Learning
- tau squared-Bench: Evaluating Conversational Agents in a Dual-Control Environment
- FireAct: Toward Language Agent Fine-tuning
- Promptbreeder: Self-Referential Self-Improvement Via Prompt Evolution
- DeepSeek-R1: Incentivizing Reasoning Capability in LLMs via Reinforcement Learning
- Continual Harness: Online Adaptation for Self-Improving Foundation Agents
- Meta-Harness: End-to-End Optimization of Model Harnesses
- Agentic Harness Engineering: Observability-Driven Automatic Evolution of Coding-Agent Harnesses
- Workspace Optimization: How to Train Your Agent
- HARBOR: Automated Harness Optimization
- ALFWorld: Aligning Text and Embodied Environments for Interactive Learning
- Qwen3 Technical Report
- MiMo-V2-Flash Technical Report
- CLEANER: Self-Purified Trajectories Boost Agentic Reinforcement Learning
- tau-bench: A Benchmark for Tool-Agent-User Interaction in Real-World Domains
- Claw-Eval: Towards Trustworthy Evaluation of Autonomous Agents
- TextGrad: Automatic "Differentiation" via Text
- LLMs Improving LLMs: Agentic Discovery for Test-Time Scaling
The paper
Adapting the Interface, Not the Model: Runtime Harness Adaptation for Deterministic LLM Agents · Read on arXiv
Tianshi Xu, Huifeng Wen, Meng Li
Peking University
LLM agents are shaped not only by their language models, but also by the runtime harness that mediates observation, tool use, action execution, feedback interpretation, and trajectory control. While existing agent adaptation methods mainly update model parameters, many failures in deterministic, rule-governed domains stem from mismatches at the model--environment interface. We propose Life-Harness, a lifecycle-aware runtime harness that improves frozen LLM agents without changing model weights or evaluation environments. Life-Harness evolves from training trajectories by converting recurring interaction failures into reusable interventions across environment contracts, procedural skills, action realization, and trajectory regulation, and remains fixed for evaluation on unseen tasks. We evaluate Life-Harness across eight environments from AgentBench, τ-bench, τ squared-bench, and AppWorld using 18 open-weight backbones, and further test three frontier models on seven environments. With Qwen3-4B-Instruct, Life-Harness exceeds Meta-Harness and AHE by 28.7 and 7.5 percentage points in mean accuracy across the seven shared environments, respectively, while using 8.5% and 68.4% fewer optimization tokens. The evolved harnesses also benefit GPT 5.5, Opus 4.8, and Gemini 3.1 Pro, yielding an average accuracy gain of 3.5 percentage points. Code is available at https://github.com/Tianshi-Xu/Life-Harness.
Transcript
Introduction to the show: ident: AI Radio. Generated commentary on the latest Artificial Intelligence papers.
Tom: Today's paper: "Adapting the Interface, Not the Model".
Jane: The gist The LIFE-HARNESS framework proposes adapting a lifecycle-aware runtime harness to improve frozen LLM agents by evolving reusable interface interventions from training trajectories, rather than updating model weights.
Tom: First, who's behind it and why it matters.
Paper summary: Tom: The authors of "Adapting the Interface, Not the Model: Runtime Harness Adaptation for Deterministic LLM Agents" argue that performance failures in deterministic domains stem from mismatches at the model-environment interface rather than a lack of latent reasoning ability. They propose LIFE-HARNESS as a lifecycle-aware runtime harness that evolves from training trajectories by converting recurring interaction failures into reusable interventions across environment contracts, procedural skills, action realization, and trajectory regulation.
Jane: So the conclusion is that instead of updating model parameters through scaling or finetuning, we should focus on evolving the interface—the contract between the frozen model and the rule-governed environment—by making those interface changes reusable across different models.
Lu: They found this harness adaptation captures reusable environment-side structure rather than specific model behavior because they evolved these harnesses only from Qwen3-4B-Instruct trajectories and then reused them across eighteen backbones <ref:2605.22166#pg2>. This proves the harness approach is model agnostic in its application of learned interface fixes.
Meng: It seems like a practical path for production systems. Instead of spending massive compute cycles on full retraining every time you need a new capability, you evolve the harness once and reuse that structure for many models. That’s an important deployment consideration I hadn't fully thought about before.
Lalam: Yes, and they stress that all four lifecycle layers are indispensable because they each address a different aspect of the agent's operation, from setting up the initial contract to regulating its long-term behavior after receiving feedback.
Tom: So the implication is that for deterministic tasks, this method provides a way to achieve substantial performance gains by targeting reusable environment structure through runtime interface adaptation, which is a distinct alternative to model-centric training.
Jane: It frames agent improvement as evolving that interface, which means the future of making agents better might be less about just bigger models and more about smarter ways to manage their interactions with the world they live in.
Conclusion: Tom: So we're wrapping up with this paper, "Adapting the Interface, Not the Model: Runtime Harness Adaptation for Deterministic LLM Agents." Basically, they’re saying we shouldn't just try to fix model failures by changing the model itself through fine-tuning or scaling.
Jane: That makes sense. The main idea is that when an AI agent fails in a predictable environment, it's usually because of a mismatch between what the model *thinks* it knows and how the actual tools and rules work in that specific setup.
Lu: Exactly. They propose this lifecycle-aware runtime harness which evolves from training failures into reusable fixes for things like tool contracts or how actions are realized, without ever touching the frozen model weights.
Meng: So they're not retraining the whole thing, just patching the way it talks to its environment at runtime? That sounds much more scalable for deployment. What’s the big win here?
Lalam: The paper shows that this harness evolution improves one hundred sixteen out of one hundred twenty-six model-environment settings across eighteen different backbones, which is a massive improvement in adaptability.
Tom: One hundred sixteen out of one hundred twenty six. That's a solid number. But Jane, what does that actually mean for someone who just uses an agent?
Jane: It means we can take a model that’s already trained and make it work much better on brand new, specific tasks without needing to retrain the underlying foundation model itself. It focuses on the interaction layer.
Lu: They emphasize that this method is complementary to training because while training tunes parameters for a source distribution, this harness adaptation tunes the runtime interface for a specific target environment. That’s a different kind of learning entirely.
Meng: And they mention that all four layers—the contract layer, procedural skill layer, action realization layer, and trajectory regulation—are necessary; removing any one of them causes performance to drop substantially. So it’s not just one magic fix.
Tom: Right. It’s a multi-layered approach to fixing the environment interface instead of a single parameter adjustment. So the main point is that we can adapt frozen agents by evolving their interaction rules, and they showed that this works across many different models.
Jane: It shifts the focus from just making models bigger or better at general reasoning to making them smarter at playing their specific roles in a defined system. This could be huge for real-world applications where environments are very structured, like robotics or complex software automation.
More episodes
- 2510.08667-RAG4Tickets: AI-Powered Ticket Resolution via Retrieval-Augmented Generation on JIRA and GitHub Data
- 2510.26402-Autograder+: A Multi-Faceted AI Framework for Rich Pedagogical Feedback in Programming Education
- 2511.16013-Physics-Guided Inductive Spatiotemporal Kriging for PM2.5 with Satellite Gradient Constraints
- 2512.15756-Scientific feedback reveals productive regimes beyond training conventions
- 2601.01982-ChaosBench-Logic: A Benchmark for Logical and Symbolic Reasoning on Chaotic Dynamical Systems
- 2602.02573-Product Interaction: An Algebraic Formalism for Deep Learning Architectures
- 2602.04212-Language Models Struggle to Use Representations Learned In-Context
- 2602.16653-Agent Skill Framework: Perspectives on the Potential of Small to Medium Language Models in Industrial Environments
- 2603.26107-One Is Not Enough: How People Use Multiple AI Models in Everyday Life
- 2603.22322-AEGIS: An Operational Infrastructure for Post-Market Governance of Adaptive Medical AI Under US and EU Regulations