Open Source AI Native Games

This collection keeps each game’s original GitHub project visible while its VifuHub integration makes it a first-class project in the VifuHub release flow and Agent Runtime. The collection includes games and starters.

git clone --recurse-submodules https://github.com/vifudotdev/awesome-open-source-ai-native-games
cd awesome-open-source-ai-native-games

Games

AIventure

• Original project: bebechien/AIventure
• VifuHub integration: brings AIventure into the VifuHub release flow and Agent Runtime. VifuHub establishes its Agent Runtime-compatible game surface for AI agents and tools, game state, resources, worlds, and approved runtime capabilities. AIventure uses it for model-driven NPC play without embedding provider credentials or host plumbing in the game.

cd games/aiventure
vf deploy

Starters

Hello Web

starters/hello-web is a first-party static browser starter for the smallest VifuHub release shape.

cd starters/hello-web
vf deploy

Collection

Path	Source and VifuHub integration
games/aiventure	Original GitHub project; a VifuHub release flow and Agent Runtime interface for AI-driven play and host capabilities.
starters/hello-web	First-party static browser starter.

Adding A Game

A useful collection entry should:

• link to its original GitHub project and preserve upstream licensing
• integrate the project with the VifuHub release flow and Agent Runtime while preserving its game identity and core play loop
• use vf deploy from the project folder
• use VifuHub as the runtime interface for AI, state, resources, and other capabilities the game needs
• avoid remote executable code in the deployed build

VifuHub Integration

When preparing an open-source game for VifuHub:

1. Keep upstream history visible, usually as a submodule or fork.
2. Confirm a static browser build output.
3. Make the project an Agent Runtime-compatible VifuHub release without replacing its core experience.
4. Use hub.* as the game-to-runtime interface for AI, state, resources, and runtime capabilities.
5. Remove unused local/remote AI providers from the deployed bundle.
6. Run vf deploy.

See Deploy Policy for why remote JavaScript imports are blocked.