about
LogAct: Enabling agentic reliability via shared logs (arxiv.org)
2 points by pramodbiligiri 162 days ago | hide | past | pdf | discuss on HN

In plain words: Every action an agent plans is written to a shared log before it happens, so outside checkers can block it and the system can replay after a crash. On a test set it blocked all harmful actions while losing just 3% of normal usefulness.

Abstract · LogAct: Enabling Agentic Reliability via Shared Logs

Agents are LLM-driven components that can mutate environments in powerful, arbitrary ways. Extracting guarantees for the execution of agents in production environments can be challenging due to asynchrony and failures. In this paper, we propose a new abstraction called LogAct, where each agent is a deconstructed state machine playing a shared log. In LogAct, agentic actions are visible in the shared log before they are executed; can be stopped prior to execution by pluggable, decoupled voters; and recovered consistently in the case of agent or environment failure. LogAct enables agentic introspection, allowing the agent to analyze its own execution history using LLM inference, which in turn enables semantic variants of recovery, health check, and optimization. In our evaluation, LogAct agents recover efficiently and correctly from failures; debug their own performance; optimize token usage in swarms; and stop all unwanted actions for a target model on a representative benchmark with just a 3% drop in benign utility.

Mahesh Balakrishnan, Ashwin Bharambe, Davide Testuggine, David Geraghty, David Mao, Vidhya Venkat, Ilya Mironov, Rithesh Baradi, Gayathri Aiyer, Victoria Dudin
arXiv:2604.07988 · cs.DC, cs.AI · submitted Apr 9, 2026
abstract · pdf · html

add comment on HN