explaingit

edem-ai/agentchord

15PythonAudience · researcherComplexity · 5/5ActiveSetup · hard

TLDR

Code release for an RSS 2026 paper that uses LLM agents to plan robot manipulation tasks with recovery branches baked in for predicted failures.

Mindmap

mindmap
  root((AgentChord))
    Inputs
      Task instruction
      Camera frames
      Gym config
    Outputs
      Task graph JSON
      Recovery spec
      Robot motions
    Use Cases
      Robot manipulation
      Failure recovery
      Sim rollouts
    Tech Stack
      Python
      LangChain
      CUDA
      Docker
      EmbodiChain
    Agents
      Task Structuring
      Recovery Orchestration
      Execution Compilation

Things people build with this

USE CASE 1

Reproduce the RSS 2026 paper experiments in simulation

USE CASE 2

Extend the recovery agent with new failure types and monitors

USE CASE 3

Generate cached task graphs for new SinglePour-style robot tasks

USE CASE 4

Adapt the framework to a CobotMagic real robot arm

Tech stack

PythonLangChainCUDADockerPyTorch

Getting it running

Difficulty · hard Time to first run · 1day+

Needs Ubuntu 20.04+, NVIDIA GPU with compute 7.0+, CUDA 12.8 Docker image, and an OpenAI-compatible LLM endpoint.

In plain English

AgentChord is the code release for an academic paper called 'From Reaction to Anticipation: Proactive Failure Recovery through Agentic Task Graph for Robotic Manipulation,' accepted at Robotics: Science and Systems 2026. It is a system for controlling robot arms that tries to handle things going wrong while a task is in progress, like an object slipping out of place or falling over. Instead of waiting for the robot to notice failure and react, it tries to predict where the plan can break and bake recovery steps in from the start. The project is built on top of a separate codebase called EmbodiChain. Inside AgentChord, three roles are played by language-model agents. A Task Structuring Agent reads the instruction and what the cameras see, then writes a directed graph of steps for the robot. A Recovery Orchestration Agent looks at that graph, predicts how it might go wrong, defines online checks that detect those failures, and adds branches that move forward into recovery instead of aborting. An Execution Compilation Agent turns the resulting graph into robot motions with monitors that can interrupt motion when something looks wrong. AgentChord can run in a GPU simulation or on a real robot called CobotMagic. The README focuses on the simulation. It needs Ubuntu 20.04 or newer with an NVIDIA GPU at compute capability 7.0 or higher, and Python 3.10 or 3.11. Install is a git clone plus pip install with an extra package index, and a Docker image based on Ubuntu 22.04 and CUDA 12.8 ships the full simulation stack. The agents call any OpenAI-compatible endpoint via LangChain, with gpt-5 as the default model name. A simulation rollout is started with a python command that points to gym and agent config files and a task name like SinglePourWater. While it runs you can press f in the terminal to inject a failure such as a misplaced or fallen object, and the system tries to recover. The generated task graph, recovery spec, and compiled graph are cached as JSON files under embodichain/database/agent_generated_content/sim/, and the cache is reused unless you pass --regenerate. The repository has 14 stars and is written in Python.

Copy-paste prompts

Prompt 1
Show me the minimum Ubuntu plus CUDA setup needed to run AgentChord in simulation
Prompt 2
Explain how the three agents in AgentChord pass data to each other for one rollout
Prompt 3
How do I add a new task to AgentChord and regenerate the task graph cache
Prompt 4
What happens when I press f mid-rollout and which monitor triggers recovery
Prompt 5
Swap the default gpt-5 endpoint for a self-hosted vLLM server in AgentChord
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.