Microverse Social Sandbox
A Godot 4 sandbox for simulating remembered conversations, tasks, and social behavior among virtual characters.
- Source repo
- KsanaDock/Microverse
- Stars
- ★ 2.5k
- Last updated
- 7mo ago
- License
- MIT
- Primary language
- GDScript
- FA score
- 39/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformOpenAI API · Claude API
- Cost
- Free software; you pay for model usage
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A Godot 4 developer studying autonomous multi-character interaction can use the office scene to observe dialogue and behavior across eight preset characters.
- Not a fit if
- Players wanting a ready-to-run game without API keys or Godot setup
- Those expecting the full Steam release rather than the June 2025 demo
- Source review
- 39/100 · Major gaps
What does this agent do, and when should you use it?
Microverse is a Godot 4 god-simulation sandbox built as a multi-agent social simulation. Its office scene includes eight preset characters with distinct personalities, backstories, and behavior patterns. The project combines natural-language dialogue, long-term memory, environmental awareness, and autonomous task management, using REST API calls to connect AI services. Game data and memories are stored locally as JSON, while the interface uses Godot’s built-in UI system. It is intended for developers and players exploring interactive social simulations on Windows, macOS, Linux, or Android, rather than as a standalone chat product or hosted cloud service.
After the project is opened and run in Godot, the player can select the office map, move with WASD or arrow keys, start a conversation with T, end it with L, and open API settings with ESC. APIManager handles REST API calls; DialogManager manages multi-turn dialogue and dialogue history; MemoryManager formats, stores, and retrieves long-term memories; CharacterManager manages character state; and TaskManager creates, assigns, tracks, and monitors tasks. Characters move and interact in the scene, responding to environmental and social conditions; dialogue appears in dynamic speech bubbles. The console also exposes memory viewing and task-management actions.
- A Godot 4 developer studying autonomous multi-character interaction can use the office scene to observe dialogue and behavior across eight preset characters.
- A prototyping team evaluating multiple text-generation integrations can configure OpenAI, Claude, Gemini, DeepSeek, Doubao, Kimi, or Ollama from the settings interface.
- A researcher testing how stored history affects later social exchanges can use the long-term-memory, retrieval, and dialogue-history features.
- An indie developer building workplace social-simulation mechanics can examine the documented character-state, emotion, task-collaboration, and competition concepts.
- A player who wants direct interaction with virtual characters can navigate the scene, initiate conversations, and save or load game state.
How do you install or deploy this agent?
You need Godot 4.3 or later and a valid AI-service API key for dialogue features. Run:
git clone https://github.com/KsanaDock/Microverse.git
cd microverseThen start the Godot editor, choose Import, select project.godot in the project root, and choose Import & Edit. Run the game, press ESC, then select an AI provider and enter its API key in API settings.
How do you use this agent?
Run the game and select a map; the documented map is the office scene. Use WASD or arrow keys to move, Space to sit, T to start a conversation, L to end one, ESC for settings, F1 to save or load, and the backtick key for the console. Before dialogue works, configure a supported provider with a valid API key in settings. The console can be used to inspect character memories and assign or manage tasks.
What are this agent's strengths and limitations?
- Combines dialogue, persistent memory, environmental awareness, and task management inside one Godot sandbox instead of limiting interaction to one-off chat.
- Includes eight preset characters with personalities, backstories, and behavioral patterns, making multi-character interaction immediately explorable.
- Documents paths for OpenAI, Claude, Gemini, DeepSeek, Doubao, Kimi, and Ollama rather than a single provider.
- Uses local JSON for memories and game data, with dialogue history and replay functionality described.
- Dialogue depends on network access and a valid API key from an AI service provider.
- Running or developing the project requires Godot 4.3 or later; Android needs additional platform-specific configuration.
- The quick-start documentation identifies the office as the current map, but does not document the available content, setup, or maturity of additional maps.
- The repository is described as an initial June 2025 demo; features and optimizations planned for the full Steam release are not promised in this repository.
How does this agent compare with similar options?
The project describes its sandbox AI society as similar to Stanford AI Town, highlighting autonomous life and interaction in an open world rather than claiming feature equivalence.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Microverse Social Sandbox This agent | 39 · Major gaps | Desktop appFree + model costs | ★ 2.5k | 7mo ago | GDScript | OpenAI API · Claude API |
| The Delegation | 45 · Major gaps | Web appFree + model costs | ★ 729 | 7mo ago | TypeScript | — |
| WorldX AI World Builder | 52 · Major gaps | Web appFree + model costs | ★ 1.6k | 25d ago | TypeScript | OpenAI API |
| BotSharp Agent Console | 48 · Major gaps | Web app | ★ 159 | 4d ago | Svelte | — |
How does FollowAgents rate this agent?
Why each dimension lost points
The README says an AI service API key is required, lists hosted providers and local Ollama, and mentions local JSON storage. It does not explain key storage, what data is sent, permission limits, call confirmation, deletion or recovery, or dependency security, so those criteria receive 1. The README credits asset and service sources and the Godot team, while the license identifies a copyright holder; source attribution has some support and receives 2.
The README specifies Godot 4.3+ and gives usage steps, but its project structure example is named office, and capabilities such as multiple maps and persistent memory are not corroborated by included code. Self consistency and dependency availability receive 1 for thin documentation. No failure handling or error messages are described, so failure_messages receives 0.
The README addresses developers and enthusiasts and describes an office scenario, character interactions, and several AI services, giving audience and scenarios some definition and a score of 2. It does not clearly bound autonomous behavior or define its triggers, so those criteria receive 1. Godot version, platforms, hardware, and network needs are documented, earning environment_fit 2.
The README has sections for features, stack, quick start, controls, and project structure, and its import and setup steps are reasonably usable; information architecture and install notes receive 2. Naming and structure examples have limited support; basic controls are included but there is no FAQ, so examples_and_faq receives 1. It states that the current scene is an office, Android needs extra configuration, and dialogue requires an API key, documenting some limitations and receiving 2. The MIT license text is complete and receives 3. It mentions a June 2025 demo but has no changelog or version policy, earning 1. A website and issue channel are provided, but a responsible maintainer and update path are not clear, earning 1.
The documentation describes controls, characters, dialogue, and tasks, but no implementation evidence or reusable Agent output format is included; output_usability receives 1. Multi-agent social simulation and memory could be valuable, but these remain README claims in the supplied evidence, so marginal_value receives 1. The product requires a valid API key and stable network, and gives no cost or resource-use guidance, so cost_benefit receives 1.
The README gives concrete Godot version, controls, providers, characters, and system requirements, but core capabilities lack supporting code in the packet; claim_traceability receives 1. Only README and LICENSE are supplied, with no code, tests, or other sources for corroboration, so cross_source_corroboration receives 0. The README distinguishes the open-source demo from a planned Steam release, but does not otherwise separate verified facts from product claims, so fact_inference_separation receives 1.
- This assessment uses only the supplied README and LICENSE. Unprovided code, tests, and other files are unknown, and core feature claims cannot be verified here.
- Before configuring an API key, confirm how it is stored and whether character memories, dialogue, or events are sent to the selected provider; the README does not describe these data flows.
- The README describes this open-source repository as a June 2025 initial demo and says a full version is planned for Steam; planned features are not verified by the supplied repository evidence.
Maintain this project? Add the FARS badge to your README
[](https://followagents.com/en/agents/microverse)<a href="https://followagents.com/en/agents/microverse"><img src="https://followagents.com/badge/microverse.svg" alt="FARS review"></a>FAQ
What credentials are required for dialogue?
Which AI services are listed?
Where are character memories stored?
Which platforms are documented?
Thanks — we use this to improve the page.