Hi maintainers,
I came across AIGeeksGroup/EvoVLA and noticed that it focuses on “[ECCV 2026] EvoVLA: Self-Evolving Vision-Language-Action Model”. That is close to a problem we are working on with EVA-CLIENT, a unified framework for real-robot deployment, evaluation, and LeRobot data collection.
If this direction looks relevant, you can take a look at EVA-CLIENT here: https://github.com/Noietch/EVA-CLIENT
For AIGeeksGroup/EvoVLA, the policy could be exposed through an EVA backend and evaluated across prompts or checkpoints on compatible hardware. A small first experiment could be to wrap one checkpoint as a policy backend and run a small prompt/task sweep. We would be happy to prepare a minimal adapter or example around your current interfaces, rather than asking you to change the project architecture.
If this is useful, I would be glad to compare notes or help with a small integration. If it is not relevant, no worries—and we will not follow up.
Best,
EVA-CLIENT Team
Hi maintainers,
I came across AIGeeksGroup/EvoVLA and noticed that it focuses on “[ECCV 2026] EvoVLA: Self-Evolving Vision-Language-Action Model”. That is close to a problem we are working on with EVA-CLIENT, a unified framework for real-robot deployment, evaluation, and LeRobot data collection.
If this direction looks relevant, you can take a look at EVA-CLIENT here: https://github.com/Noietch/EVA-CLIENT
For AIGeeksGroup/EvoVLA, the policy could be exposed through an EVA backend and evaluated across prompts or checkpoints on compatible hardware. A small first experiment could be to wrap one checkpoint as a policy backend and run a small prompt/task sweep. We would be happy to prepare a minimal adapter or example around your current interfaces, rather than asking you to change the project architecture.
If this is useful, I would be glad to compare notes or help with a small integration. If it is not relevant, no worries—and we will not follow up.
Best,
EVA-CLIENT Team