DriveVLA-M0: Failure-Aware Memory Augmentation for Autonomous Driving
Zebin Xing*, Yupeng Zheng*, Qiang Chen, Linbo Wang, Yichen Zhang, Pengxuan Yang, Junli Wang, Deheng Qian, Xiaoqing Ye, Junyu Han, Yifeng Pan, Qichao Zhang, Dongbin Zhao
ACM Multimedia, 2026
This repository packages the NAVSIM 1.1 deployment code for DriveVLA-M0, including the Base Model and the structurally grounded Retrieve Model used for map and agent retrieval experiments.
DriveVLA-M0 augments a VLA-based autonomous driving planner with failure-aware latent memory. The full framework stores past failure cases, retrieves structurally similar scenarios through decoupled map and agent embeddings, and injects retrieved knowledge through lightweight test-time adaptation. This release focuses on the NAVSIM 1.1 Base Model and Retrieve Model code paths that are needed for deployment and checkpoint verification.
- 12 Aug, 2026: Released the cleaned NAVSIM 1.1 DriveVLA-M0 deployment package with Base Model and Retrieve Model checkpoints verified on A800.
- 10 Jul, 2026: DriveVLA-M0 is prepared as a failure-aware memory augmentation framework for autonomous driving.
- Base Model deployment. The Base Model is exposed through the compatibility target
EpisodeDriveAgentand can be evaluated directly with NAVSIM PDMS scripts. - Retrieve Model deployment. The Retrieve Model decouples static road structure and dynamic agent interaction cues for map/agent retrieval visualization.
- Checkpoint-compatible naming. Public documentation uses DriveVLA-M0. The current NAVSIM Python target keeps
EpisodeDriveAgentas a compatibility entry point so that verified checkpoints load without changing the module state-dict layout.
DriveVLA-M0 contains two major stages:
- Offline memory generation. Failure-prone scenes are identified by oracle simulation metrics, and their intermediate scene representations, trajectory clusters, and expert signals are written into a latent memory pool.
- Online inference with retrieval and TTT. The Retrieve Model extracts map and agent keys for the current scene, retrieves structurally similar historical cases, and enables scenario-specific correction through decoupled LoRA-based test-time training.
In this release, the deployable components are:
| Component | NAVSIM target | Purpose | Weights |
|---|---|---|---|
| Base Model | navsim.agents.EpisodeDrive.episodedrive_agent.EpisodeDriveAgent |
Planning / PDMS evaluation | Hugging Face / ModelScope |
| Retrieve Model | navsim.agents.EpisodeDrive.retrieve_model.retrieve_agent.RetrieveModelAgent |
Map and agent retrieval verification | Hugging Face / ModelScope |
Both checkpoint groups are available from the Hugging Face and ModelScope mirrors above.
Hydra configs:
agent=episode_drive
agent=episode_drive_retrieveMain paper NAVSIMv1 result reported for DriveVLA-M0:
DriveVLA-M0/
|-- navsim/
| `-- agents/
| `-- EpisodeDrive/
| |-- episodedrive_agent.py
| |-- drivevla_base_agent.py
| |-- action_decoder.py
| |-- retrieve_model/
| |-- score_module/
| `-- layers/
|-- configs/
| |-- base_model_navtest.yaml
| `-- retrieve_model_vehicle_only_multiview_agentw5.yaml
|-- scripts/
| |-- run_base_pdms.sh
| `-- run_retrieve_visualization.sh
|-- tools/
| `-- verify_retrieve_model.py
|-- requirements.txt
|-- requirements-episode-drive.txt
`-- environment.yml
If you find DriveVLA-M0 useful, please consider citing:
@inproceedings{xing2026drivevlam0,
title={DriveVLA-M0: Failure-Aware Memory Augmentation for Autonomous Driving},
author={Xing, Zebin and Zheng, Yupeng and Chen, Qiang and Wang, Linbo and Zhang, Yichen and Yang, Pengxuan and Wang, Junli and Qian, Deheng and Ye, Xiaoqing and Han, Junyu and Pan, Yifeng and Zhang, Qichao and Zhao, Dongbin},
booktitle={Proceedings of the 34th ACM International Conference on Multimedia},
year={2026}
}This repository is built on top of NAVSIM, nuPlan, and OpenScene data tooling. The README layout follows the clean research-project style used by GoalFlow. We also thank the open-source autonomous driving community for prior work on VLA planning, retrieval, and memory-augmented agents.
For questions, please open an issue or contact the authors listed in the paper.


