
Code as Agent Harness
Xuying Ning
8 posts

@krystal_ning
UIUC CS PhD, Prev@Columbia&XJTU

Code as Agent Harness

🚀Code as Agent Harness: A survey work from UIUC, Stanford, and Meta. 📄arxiv.org/abs/2605.18747 Code is no longer just the output of AI. It is becoming the executable, inspectable, and stateful substrate through which AI agents reason, act, verify, remember, and self-correct over long horizons. In our new survey, we examine this shift through the lens of Code as Agent Harness, focusing on how code serves as: • 🧠 Harness Interface: coding for reasoning, acting, and environment modeling • ⚙️ Harness Mechanisms: planning, memory, tool use, feedback, and optimization • 🤝 Multi-Agent Harnesses: collaboration through shared code, tests, and execution traces We review applications spanning: 💻 Coding Agents 🖥️ GUI/OS Agents 🤖 Embodied Agents 🔬 Scientific Discovery 🏢 Enterprise Workflows If you find this survey helpful, feel free to explore our resource collection below. 🤗 Hugging Face Daily: huggingface.co/papers/2605.18… 💻 GitHub: github.com/YennNing/Aweso… 🌍 Website: code-as-harness.github.io/code-as-harnes… Feedback, suggestions, and community contributions are warmly welcome! #AI #Agents #LLM #Coding #AgenticAI #SoftwareEngineering

// Code as Agent Harness // 100+ page report on all things related to agent harnesses. (bookmark it) In particular, the survey summarizes methods and applications of code as agent harness. This paper makes a strong case that code-as-harness might be the key to moving us towards a broader science harness engineering. Is code all you need? Maybe. Regardless, the paper argues that future systems must have the following four properties: executable, inspectable, stateful, and governed. Paper: arxiv.org/abs/2605.18747 Learn to build effective AI agents in our academy: academy.dair.ai

// Code as Agent Harness // 100+ page report on all things related to agent harnesses. (bookmark it) In particular, the survey summarizes methods and applications of code as agent harness. This paper makes a strong case that code-as-harness might be the key to moving us towards a broader science harness engineering. Is code all you need? Maybe. Regardless, the paper argues that future systems must have the following four properties: executable, inspectable, stateful, and governed. Paper: arxiv.org/abs/2605.18747 Learn to build effective AI agents in our academy: academy.dair.ai










