Skip to content
AI News HubLIVE
Original source2 min read

Agent Harness Awareness: Turning Verified Telemetry into Operational Control for Tool-Using Agents

Summary

An arXiv paper introduces Agent Harness Awareness, a trust-separated design that provides verified tool-health state snapshots to agents before consequential actions, closing the "operational blindness" gap. Experiments show a 96.9% reduction in policy regret and an increase in single-dispatch completion from 69.4% to 95.8%.

SourcearXiv AIAuthor: Manu Agrawal, Shrey Nagpal
Agent Harness Awareness: Turning Verified Telemetry into Operational Control for Tool-Using Agents
Report an error

The correction channel is not available yet. You can copy the article reference below for later.

Correction instructions
Read article

[Submitted on 13 Sep 2026]

Title:Agent Harness Awareness: Turning Verified Telemetry into Operational Control for Tool-Using Agents

View a PDF of the paper titled Agent Harness Awareness: Turning Verified Telemetry into Operational Control for Tool-Using Agents, by Manu Agrawal and Shrey Nagpal

View PDF HTML (experimental)

Abstract:Tool descriptions tell an agent what an action can do, but they do not necessarily reveal whether that action is healthy or suitable at the moment of use. Execution harnesses often possess this information through monitors, traces, and recent failures while the model choosing the next action does not. We call this gap operational blindness. We introduce Agent Harness Awareness, a trust-separated design in which the host supplies a small, fresh, verified state snapshot before a consequential action while retaining measurement, enforcement, evaluation, and final dispatch authority. We test its tools-and-network instance with ToolRoute, a controlled isolation benchmark that holds the task and candidate semantics constant and varies the operational information available to the model. In a 216-decision ablation across GPT-5.6 Sol, Claude Sonnet 5, and Gemini 3.7 Flash, verified tool-health state reduced mean observable policy regret by 96.9% against a same-shape neutral control (4,252 ms to 131 ms) and raised single-dispatch completion from 69.4% to 95.8%. In a separate 27-decision end-to-end replication with live local TCP/HTTP execution, OpenTelemetry client spans, and Toxiproxy-injected faults, verified state reduced mean regret from 8,956 ms to 0 ms (zero excess observable operational cost) and completed the live action in 9/9 model-by-fault cases versus 5/9 for the neutral control. These studies establish the tools-and-network instance of Agent Harness Awareness: selected host telemetry materially improves pre-dispatch operational choice. Runtime state, hardware pressure, economics, retry-aware recovery, and heterogeneous selection remain open empirical extensions of the same architecture.

Comments: 9 pages, 3 figures

Subjects:

Artificial Intelligence (cs.AI); Computation and Language (cs.CL)

Cite as: arXiv:2611.05391 [cs.AI]

(or arXiv:2611.05391v1 [cs.AI] for this version)

https://doi.org/10.48550/arXiv.2611.05391

arXiv-issued DOI via DataCite

Submission history

From: Manu Agrawal [view email] [v1] Sun, 13 Sep 2026 15:01:55 UTC (94 KB)

Full-text links:

Access Paper:

View a PDF of the paper titled Agent Harness Awareness: Turning Verified Telemetry into Operational Control for Tool-Using Agents, by Manu Agrawal and Shrey Nagpal

View PDF

HTML (experimental)

TeX Source

view license

Additional Features

Audio Summary

Current browse context:

cs.AI

new | recent | 2026-11

Change to browse by:

cs cs.CL

References & Citations

SciX

Google Scholar

Semantic Scholar

Loading...

Data provided by:

Bibliographic Tools

Bibliographic and Citation Tools

Bibliographic Explorer Toggle

Bibliographic Explorer (What is the Explorer?)

Connected Papers Toggle

Connected Papers (What is Connected Papers?)

Litmaps Toggle

Litmaps (What is Litmaps?)

scite.ai Toggle

scite Smart Citations (What are Smart Citations?)

Code, Data, Media

Code, Data and Media Associated with this Article

alphaXiv Toggle

alphaXiv (What is alphaXiv?)

Links to Code Toggle

CatalyzeX Code Finder for Papers (What is CatalyzeX?)

DagsHub Toggle

DagsHub (What is DagsHub?)

GotitPub Toggle

Gotit.pub (What is GotitPub?)

Huggingface Toggle

Hugging Face (What is Huggingface?)

ScienceCast Toggle

ScienceCast (What is ScienceCast?)

Demos

Demos

Replicate Toggle

Replicate (What is Replicate?)

Spaces Toggle

Hugging Face Spaces (What is Spaces?)

Spaces Toggle

TXYZ.AI (What is TXYZ.AI?)

Related Papers

Recommenders and Search Tools

Link to Influence Flower

Influence Flower (What are Influence Flowers?)

Core recommender toggle

CORE Recommender (What is CORE?)

Author

Venue

Institution

Topic

About arXivLabs

arXivLabs: experimental projects with community collaborators

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

Which authors of this paper are endorsers? | Disable MathJax (What is MathJax?)

Key points and analysis

Article intelligence

EngineersAdvanced

Key points

  • Introduces "operational blindness": agents lack tool-health state that execution harnesses possess.
  • Trust-separated architecture keeps measurement and dispatch authority with the host.
  • In a 216-decision ablation, verified state reduced mean policy regret by 96.9% and boosted completion to 95.8%.
  • End-to-end fault-injection tests show verified state achieves zero excess operational cost and 9/9 success.

Highlights and analysis are generated automatically and may contain errors. Check the original source.