Skip to content

CordisBench: Can Language Models Reason About Component Lifecycles in Dynamic Agent Harnesses?

Sep 2026 · 1 citation · 20 references
Computer Science

TL;DR

CrisBench, a 1,200-question benchmark of lifecycle reasoning that combines a controlled formal setting with programs executed against Cordis, a runtime that manages component dependencies and cleanup, and asks models to identify affected components, predict state after a specified teardown order, and determine which conditions hold under all or some orders.

Abstract

Dynamic agent harnesses let language models change the software that shapes their own execution. This flexibility brings a new reasoning burden: a local plugin change can propagate through dependencies and cleanup. We introduce CordisBench, a 1,200-question benchmark of this lifecycle reasoning. It combines a controlled formal setting with programs executed against Cordis, a runtime that manages component dependencies and cleanup, and asks models to identify affected components, predict state after a specified teardown order, determine which conditions hold under all or some orders, and choose reconfigurations that succeed when executed. Across these tasks, we evaluate three efficiency-oriented models at low reasoning effort with 2, 4, 8, 16, 24, or 32 relevant interactions, using deterministic task-specific scoring. Models usually handle small systems well but grow less reliable as more interactions become relevant, especially when predicting final state and when reasoning across teardown orders. Additional inference effort recovers marked gains for some models. The cost is nontrivial: on our 16-interaction subset, GPT-5.6 Luna uses nearly 3,000 reasoning tokens per question at medium effort. For these controlled instances, that cost is avoidable: an independent finite reference semantics agrees with Cordis execution on every observation and action outcome used for scoring across all 528 executable questions.

View source

Similar papers

#artificial intelligence Preprint Sep 2026

FIRE: Failure-Informed Runtime Engineering for Reliable Language-Model Agents

Language-model agents often reach a working solution and then fail to consistently deliver it. We study runtime policies: targeted natural-language instructions and action denials applied by the agent harness at states that preceded observed failures, without changing model weights or the user prompt. With this, keepin...

Nikita Agarwal, Nivedit Jain · 0 citations
Preprint Aug 2026

Formal Verification of Agentic Systems over Operational Data

It is shown that LLM-driven agents can violate this condition and introduced a canonical deployment wrapper that guarantees it for arbitrary base agents while preserving already-equivariant behaviour, and it is proved that computing canonical representations required by this construction is graph-isomorphism-hard.

Alejandro J. Mercado, A. Lomuscio · 0 citations
#artificial intelligence Preprint Sep 2026

PetriBench: Benchmarking LLM Reasoning over Dynamic State Spaces

PetriBench is introduced, a compact, fully self-contained, and scalable benchmark for evaluating LLM reasoning over dynamic state spaces using Petri nets, a mature formalism for modeling real-world concurrent and distributed systems.

Pyrros Koussios, Benjamin Jäger, John Hua Yao et al. · 0 citations
Preprint Aug 2026

From Prompt to Harness: Coderlet from Scratch

This paper studies a compact harness design by following a single request through context formation, model decision, environmental action, observation return, and state continuation, showing the harness's core role: turning model generations into environmental actions, carrying runtime feedback into later decisions, an...

Meng-Fan Li · 0 citations
Preprint Sep 2026

CaMeLoT: CaMeL orchestrated with Temporal logic for static verification and liveness

LLM-based agents generate and execute multi-step plans that invoke external tools which can access private data or execute commands. In this setting, security is a property of the entire execution that a plan creates, not just any single step. The plan itself is a critical artefact that captures the tool calls, control...

Elia Nikolaou, M. Eckhoff, Robert Flood et al. · 1 citation

Related blog posts

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.