Beyond Global Replanning: Hierarchical Recovery for Cross-Device Agent Systems

· Source: Computation and Language · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Robotics & Autonomous Systems, Software Development & Engineering · Depth: Advanced, quick

Summary

H-RePlan is a hierarchical replanning framework designed for multi-device agent systems that operate across diverse applications and devices, addressing dynamic runtime failures. Existing systems often rely on coarse-grained recovery, retrying strategies or revising global plans without modeling device-local strategy space. H-RePlan overcomes this by equipping each device with interchangeable execution strategies and separating device-local strategy recovery from orchestrator-level global replanning via a compact cross-layer failure abstraction. Evaluated using HeraBench, a fault-injected benchmark for Linux and Android workflows, H-RePlan significantly outperforms single-strategy and coarse-grained baselines. It achieves higher completion, instruction adherence, and perfect-pass rates, while also reducing the token cost for reliable end-to-end success, demonstrating the necessity of scope-aware hierarchical recovery.

Key takeaway

For AI Engineers building or deploying multi-device agent systems, recognize that current coarse-grained recovery methods are insufficient for dynamic real-world environments. You should integrate hierarchical recovery frameworks like H-RePlan, which separate device-local strategy handling from global replanning. This approach will significantly improve your system's robustness, completion rates, and resource efficiency, reducing token costs for reliable task execution across heterogeneous devices.

Key insights

Hierarchical, scope-aware recovery is crucial for robust multi-device agent systems operating under dynamic runtime failures.

Principles

Method

H-RePlan equips each device with interchangeable execution strategies and separates device-local strategy recovery from orchestrator-level global replanning using a compact cross-layer failure abstraction to manage failures.

In practice

Topics

Best for: Research Scientist, AI Architect, AI Scientist, AI Engineer, Software Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Computation and Language.