Launching today
Viberia
Command AI agents like you're playing Civilization
212 followers
Command AI agents like you're playing Civilization
212 followers
Do you like your Claude/Codex pet but wish you had a zoo? Viberia is a spatial command center for your AI agents. Your whole AI org lives on an isometric map, status icons show who’s blocked, who’s asking, who’s done. Zoom in to chat with anyone, pick any model, bring your own keys. Agents collaborate, build their own little teams, and pick up new skills as they go. Docs, terminals, browsers built in.
Viberia
Hey Product Hunt!
I’m Emre, Viberia’s solo builder.
I spent the last year drowning in terminal and IDE windows trying to keep up with my own agents. MCPs, subagents, skills, hooks, modes and more.
I tried Conductor, Claude Squad, Gas Town and others. They all felt the same after a while, just a long list of things waiting on my attention.
So, I went the other way.
What if managing your agents felt like playing a game of Civilization or SimCity? You zoom out and see your whole AI org on an isometric map, with status icons telling you who’s blocked, who’s asking a question, who’s done. You zoom in and chat with anyone. The agents collaborate, hand work off to each other, and over time they build their own little teams and pick up new skills.
A few things worth knowing:
- The harness is built around teams/buildings, these are agents that work together (and/or in a sequence) to deliver what you need (e.g., write PRD first, write code later, and then review). I saw my own productivity and output increase significantly when I started using agents in a sequence, and this is one of the core differentiators of Viberia.
- It’s free and will stay free; you just need to bring your own subscription and/or API keys. It works with Claude, GPT and Gemini.
- Docs, terminals, browsers are all built in. No app-switching.
- It’s a Tauri app. Roughly 8x less energy than the closest competitor I benchmarked, so you can actually use it at a coffee shop on battery.
The product is still in early alpha. There will be bugs and missing features. Please tell me about them. I read every comment, and I’ll personally chase every bug and feature request. My goal is to make Viberia the most efficient, capable, and fun agent harness out there.
Cheers,
Emre
Congrats on the launch, Emre! I am really curious about the architecture under the hood. As these agents collaborate, hand off work, and pick up new skills, is there a knowledge graph getting formed on the backend from each LLM to manage their shared context and relationships?
Viberia
@sammy_rawat Thanks Sameer!
There is no default knowledge graph that tracks their collaboration/relationships, but you can add yours in Viberia! There is an internal text-based memory system, and the agents decide when to use it. In my experience they keep track of their relationships, but you could give them more specific guidance on this through the system prompt.
If you want to plug in your own knowledge graph, drop any memory/KG MCP server into the agents and tell them to use that whenever they collaborate with each other. You can set this per-agent, per-team, or per-project. I didn't want to bet the architecture on one memory paradigm, so I left the choice to you.
Thanks for the question! I honestly hadn't seen this as a gap, but you're making me reconsider. Maybe I should build collaboration tracking deeper into Viberia.
@emre_barut great, you have really thought deep on the architecture and kept it modular, nice to see that.
Viberia
@sammy_rawat Thanks! @Obsidian was a huge inspiration here.
I'm going for "you can bring anything in, we are not locking you in or out, you can export everything if you really want to, but you won't because this will be the best way to do things".
This is a great initiative, just wanted to know if you thought of adding an additional feature where different agents remember your codebase and you don’t have to give the context again and again. So my main thought is if we are working on a project so you can divide these agents into teams say frontend, backend team and all the agents works in accordance to each other. If changes are made then all the teams are informed so that every agents works accordingly and there are less coding conflicts. This feature can also save you credits usage.
Viberia
@partha_gautam Thanks for the great comments and the feedback!
That's exactly how I've been using Viberia to build Viberia. I keep docs, CLAUDE.md (+ AGENTS.md) and README.md files for different parts of the codebase, and when agents start working on a section they read these to get the full context. Saves a TON on tokens, as you said.
I haven't added this as an explicit feature yet (and I probably should), but the best way to set it up today is to spin up a documentation team and literally give them this task. Then, agents/teams can use that info properly.
For parallel work I use git worktrees. There's a building in Viberia called "Worktree Forge" that sets these up for you. It takes two clicks to spin one up, or you can ask an agent to do it (which is how I usually do it). Each team works in a different branch, and the Merger agent in the Forge handles the merging while staying aware of the docs and potential conflicts.
If you want to take this one step further, use the Linear building (assuming you track issues in Linear; you can use a different provider, just set up your own custom building with the right MCPs). Ask the agents there to come up with 6-7 tasks you can tackle in parallel. The Issue Resolver agent will set up the worktrees, brief each team on what they need to do, and tell them what conflicts they might hit with other ongoing tracks. The worktree agents get back to you when they have a plan or an implementation, and then you OK it or ask for improvements. Makes for a really fun iterative development loop. I work with 6-10 branches in parallel using this setup (see the screenshot below of a section of my git commit graph).
pretty cool concept@emre_barut!
Curious what are your thoughts regarding visualization/ui/ux for the management of tasks and projects rather than teams and agents? I feel like grooming tasks of different stages (e.g. developing prototypes to get more clarity, or, when enough clarity has been reached, making sure the architecture/plan is good) is a place where bottlenecks are moving into (besides the actual pipeline of how a team of agents handles work)
also...pretty fun to see the Lion as the chief/mayor in the pictures, got a bit of zootopia vibes which I thought was lovely
Viberia
@luis_hernandez23 Thanks Luis!
The way I've been using Viberia, the building is the task. Buildings don't have to be permanent teams. Half the time, mine are task-specific: I spin up a building for a feature or component, fill it with the agent roles that make sense for the flow (planner, developer, reviewer, etc.), and tear it down when the work is done. Each agent inside ends up handling a specific section of that flow, so an agent's identity is really "doing X (the agent role) for component Y (the building name)".
So if you want lifecycle stages, you can literally model them as buildings: a "Prototyping Lab" for exploration, an "Architecture Council" once you have enough clarity, a "Build Team" for execution. You can wire them up so work flows between them, with the Linear building plugged in for the formal ticket layer if that's how you track things.
That being said, you're right that there's no first-class "task overlay" on the map today. The task identity is implicit in the building, not something you can see and move around independently. There is probably a way to use the spatial layout to surface that better, definitely something I should think more about.
On the Zootopia vibes, that's probably been subconsciously drilled into my brain by someone at home who won't stop talking about it, especially since the second one came out..
really cool idea-feels very different from usual list based tools? Also I am excited to know how you manage it when there are a lot of agents, doesn't it get messy?
Viberia
@yati_kumawat Thank you!
It really doesn't get messy. It just gets fun.
Spatial placement + status icons helps you contextualize what's going on in different parts of your project. You're not reading 20 chat threads, you're scanning a map (e.g., "ok, 5 agents blocked in the frontend, let me focus there first").
Sometimes I kick off 8-10 agents at once. Instead of feeling overwhelmed I'm just smashing buttons to feed them their next orders. Because it feels like a game, it doesn't drain you the way prompting usually does.
And if you really do get lost, just ask your Chief of Staff ("I'm stuck, I have 10 agents who need responses from me, help" is something I might have said before). With that agent, you don't have to type, you just pick among the options it presents. You become the decision maker, not the prompter.
I've run close to 20 agents concurrently and never hit vibecoding burnout. Just looking around to see who needs help.
Give it a try. If something feels off, please tell me (or your Chief of Staff) so we can figure out how you can happily rule your army of AI agents.
Ahah seems so fun, but how do you connect them ? All by one on Claude ? Or another one ?
Viberia
@thithilacastagne 😀 it is fun!
You can mix and match, you pick the model for each agent. There are also default settings for the type of an agent, so you can go "I want gpt-5.5 for developers and gemini for designers". Under the hood each agent gets MCP tools that allow them to interact with the interface ("let me open a md file and show it to the user") and with each other ("let me message folks in my team"). In that sense Viberia's backend connects whatever model you are running for each agent.
Agents are model agnostic too. They retain their settings (memories, skills etc.) when you change models (or providers) so you don't have to stick with a single model for the lifetime of an agent.
@emre_barut great, really !
Thx for your answer :)
Cosmic
Congrats on the launch! The UX metaphor is doing a lot of work hereL 'commanding agents like units' is intuitive in a way that most orchestration UIs completely miss. The real test is whether it scales to non-technical operators who need to run complex workflows without understanding what's happening underneath. Rooting for this.
Viberia
@tonyspiro Thank you!
Word.
IMHO, they need to be able to peek under the hood and ask an agent to explain what's happening, just like you can sit down with an employee and grill them on the details. Viberia gives you the backend and the interface for this. Getting the UI/UX to a point where users naturally do that is my next focus.
Cosmic
@emre_barut That 'explain yourself' interaction is exactly the right design target. The agents that win long term are the ones that can show their work, not just do the work. Most orchestration UIs treat the reasoning as an implementation detail. You're right that it needs to be a first-class UI primitive. The non-technical operator needs to feel like they're managing a team, not operating a black box. Following the build closely.