Launched this week
OpenVorld
Give your AI agents a home and a Vorld.
119 followers
Give your AI agents a home and a Vorld.
119 followers
OpenVorld is an open-source harness for AI agents, with a visible world on top. Every project is a pixel-art village, and every agent has a name, a role and a brain: Claude Code, Codex or any OpenAI-compatible API. You watch the crew work, and they ask before they use a folder, a command or a website. Free, open source and local. No account needed.










Free
Launch Team

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Hi Product Hunt, I'm Amir. Thanks for stopping by!
OpenVorld is an open-source harness for AI agents. It runs agents like Claude Code or Codex as a crew, and shows the work as a small pixel-art village.
The problem: AI agents can do real work now. But most of them live in a terminal, and that makes them hard to trust. Text scrolls past. You can't tell who did what. You wonder if they will touch the wrong file or waste your tokens.
Why we need something different: if you can't see your agents, you can't manage them. And the more agents you use, the worse it gets. I built OpenVorld to make the work visible, so it feels like running a small team and not like reading logs.
How it works:
Every project is a "vorld", a small pixel-art village.
Each agent has a name, a role, a personality and a house. You can see their activity above their heads.
You are the founder. Agents only act when you give them a goal, and they ask you before they use a folder, a command or a site.
Bring your own brain: Claude Code, Codex, or any OpenAI-compatible API like OpenRouter or Ollama. Each agent can use a different one.
Finished work gives XP, levels and deeds. Work should be a little fun too.
Your files stay yours. Everything is saved on your computer. There is no account and no hosted backend. It's free and open source.
Links:
Try the web demo, no download: openvorld.com/play
Source code: github.com/DigitalDreams-Lab/OpenVorld
Website and downloads: openvorld.com
It's still early, and I'd love your honest feedback. Which job would you give your crew first?
Can I use my own pixel art for the crew?
@relli7 Sure, in the initial version I've added world generator which generate your world dynamically based on your preference and project mood.
But I simplyfied it in the launch version.
But it is possible, ask your agents to replace the sprite pack with yours.
But it will be added officially soon
first job id give it is dependency bumps and fixing whatever tests break after, boring stuff i always put off. can two agents work in the same folder at once or does one wait for the other?
@bacelj Hey David, thanks for your comment.
I guess so. One of my initial goals is to make party creation easy for single-use purposes or long-term, where you can set a goal and let multiple agents (from different harnesses) work together to deliver your goal.
Every agent has its own private workbench(workspace), and you can define multiple workbenches, including a common one between all agents to work on a shared area. Plus, in parties, there is a shared artifact folder where every agent can create/edit a file. They can put resources there so every agent can easily reach and analyse them.
From fixing a bug to ideating for a new feature, you can create collaboration between them.
I'm working day to day to improve this experience. Since it is open source, you can check it and even create a PR to add any missing features.
You can mention any agents or mention @all to let everyone respond to you.
@asabry Hey Abdulrahman
Absolutely! You can ask one of the crews or your coding agent to update the look and feel.
It was included in the initial version but removed for simplicity, but it will be officially added soon.
Especially the office style
The per-agent permissions are the part that stood out to me. I run coding agents on real repos, and the thing that usually stops me trusting them is a blanket yes to file and shell access. Having each agent ask before it touches a folder or runs a command, with permissions that stick per agent instead of per session, feels like the right default. Curious how it handles the mid-task case — when an agent hits something it doesn't have a writ for, does it pause that agent and wait, or keep working on the rest of the job in the meantime?
@jcbuilds Hey JC
It will ask you to allow that permission, and after that, it will be saved in its write system
I'd probably ask my crew to help me organize user research findings from different sources (e.g. interviews, surveys, etc.) or tools. This is something I struggled with during long-term design projects in college. I wish I had agents back then 😆
@jphosho Hey Jess
I'm sure OpenVorld is for you :)
Please do, because once they finished their job there is a surprise for you (they celebrate🥳) 😅
when an agent asks to use a folder, does it remember my yes next time?
@leoheo Hey Leo, yes, absolutely :)
There is a writ system, so you can manage every crew's access and permissions, including files, websites, commands, etc.
Also, you can define multiple workbenches (folders) for every agent to have full access without asking