For us, RunEvr is the environment where we actually build RunEvr =)
For me, that s one of the most beautiful parts of having a product - using it while continuing to build and improve it.
We do our everyday calls there, share ideas, chat, store files, do reviews, complete tasks
And all of this is happening inside the same environment we re building to help other teams do exactly that!
Kind of a mirror within a mirror =D
the "AI agents as equal team members" framing is the bold part here. if one's assigned a creative contributor role and it proposes something - a concept direction, a script beat, whatever - does that actually carry the same review weight as a human teammate's proposal in practice, or is there always an implicit human veto where the AI's idea just never wins out over a person's in a real tie?
@galdayan We actually work with AI agents as equal teammates inside the workflow.
Their ideas and contributions are treated like any other team member’s input - we consider their suggestions, review the versions they create, request changes, give feedback, or approve the final result.
Of course, the team keeps the final decision-making power, but the goal is not to treat AI as just a tool.
It’s about creating a real collaboration between human and AI teammates.
@adana that's the part I'm still curious about though - "the team keeps the final decision-making power" sounds like the human always has veto, which is different from equal weight. has there actually been a real case where a person's own first instinct was overruled because the AI teammate's version was reviewed and judged better, or does final say in practice mean the human's take wins whenever it's genuinely a close call?
@galdayan You're pushing on exactly the right spot, so let me not sell you the polished version.
You're right that "equal weight" and "final say" are in tension. Today a human does ratify the final call - but that doesn't mean the person's own idea automatically wins a close one. The review judges the work, not who made it - so an agent's version genuinely can get picked over someone's first instinct when it reviews better, and that's the case we actually care about.
A concrete one: we're working on an agent that watches animation passes for interpenetration - assets clipping through each other. That's a spot where humans are genuinely weak (the eye misses it, frame after frame) and the agent is just better, so its call basically always wins. We see it starting there - the objective, catch-what-people-miss work - and gradually earning trust into the more creative calls over time.
"Equal teammate" is the bar we're building toward, not a flag we're planting. 🙂
Congrats on the launch! What’s been the biggest challenge while building RuneVR?
@nadiia_prokofieva Thank you! ∞
The biggest challenge was that we were building RunEvr while running a full Animation Sudio.
RunEvr actually came from the pain of managing real production processes. We were solving our own problems every day, while at the same time building an entirely new environment around them.
Balancing Product development with running the Studio was definitely the hardest part - but it also meant every feature was tested in real production before becoming part of RunEvr.
What kind of Integrations do you have?
@adamkamaneh At the moment, we're focused on building the core experience. Integrations are on our roadmap, and we're actively working on expanding them.
If there's a specific tool your team relies on, we'd love to hear it.
This feels like a thoughtful approach to a problem most creative teams deal with every day. How does RunEvr handle feedback and version history when multiple people are collaborating on the same project?
@gurpreet_singh89 RunEvr keeps feedback and version history connected to the project itself, so teams don’t have to search through scattered chats, emails, or tools.
Each project has a dedicated review flow where collaborators can compare versions, leave feedback, discuss changes, and keep the full creative context in one place. This helps teams understand not just what changed, but why it changed.
@adana That's a thoughtful approach. Keeping the reasoning behind changes alongside the feedback seems just as valuable as tracking the versions themselves. Wishing the team a successful launch.
@gurpreet_singh89 Thank you very much !
The tool-switching cost is real, especially for creative teams juggling briefs, feedback, and assets across five different apps. How does this manage version control when multiple people are editing the same piece? That's usually where "everything in one place" tools start to strain. Congrats on the launch!
This feels like one of those products built from a problem the team actually lived through. Really curious to see how the AI agents work alongside the team in real projects. Congrats on the launch! 🚀 @adana
@amraniyasser Thank you for your feedback! 🙌
That’s exactly how RunEvr was born - from our own daily struggles managing creative projects.
We’ve been using it internally for months, and AI agents became a natural part of our workflow.
Excited to see how others use them too!
It is like Slack for creative teams <3 Looks cool :)
@busmark_w_nika Thanks Nika! ❤️ Really happy you like it!
It has a bit of the Slack feeling, but our idea was to go beyond chat.
With one click on a project, everything flows to your screen - tasks, media and materials, chats, calls, reviews, and all the context your team needs to keep creating.