OpenBot - Grok Bot alternative: free, local, open-source, multiplayer
by•
OpenBot is an open-source workspace for AI teammates.
Connect Claude, ChatGPT, Grok, OpenCode, or custom agents on Mac, Windows, and iOS.
Give agents clear roles, let them delegate work, and invite your team to collaborate live with the same agents.

p/nudgeforme
p/runevr
p/nexupira
p/producthunt
p/google-cloud-platform
p/many-displays
p/operum
p/murror
p/dino-kids
p/tabstack
p/any-video-to-text
p/rithub
p/seldon
p/jot-2-0
p/okapi-2
p/gatrends
p/kodlo
p/appxiom
Replies
Looks good, but what’s the solution for bigger teams to communicate with agents? For example, I have a 15-person team. I want to chat with my SEO agent, and my project manager wants to chat with the UX agent.
Hey, the product's great on both technical and non-technical aspects. I recently have a thing going on my mind which is to start an automation business (strict solo). I did some research on ICP and wedges. eventually I'll need a team to scale the business. How's this thing gonna hold up when we give it a real work rather than working with files? I don't wanna have some chat sessions with a random agent but instead, I wanna have a team with works alongside me. is it gonna take too much resource from my base M3 MacBook Air when I scale the work?? Appreciate your work!
An open source workspace where you can mix Claude, ChatGPT, Grok and custom agents, give them roles and let them delegate, covers a gap that single model tools leave open. Letting your team collaborate live with the same agents is a neat idea. Is the delegation between agents configurable or does it happen automatically based on the roles?
@karimbenkeroum You can assign roles and choose which agents join a channel. The lead agent then delegates tasks to the relevant teammates.
the multiplayer angle is the part that'd make me cautious before rolling this out to a team - if Claude, ChatGPT and Grok are all sitting in the same live workspace reading the same shared context, has anyone tested what happens when one agent's output contains something the next agent reading it would treat as an instruction? that's less of an edge case once you have multiple vendors with different safety tuning looking at the same shared board instead of isolated sessions
@galdayan Agents keep separate conversations, and shared channels let you choose which agents collaborate. This helps limit shared context, but it isn’t a hard security boundary or a complete safeguard against this kind of risk.
@kamil_cyrek makes sense, "soft boundary" is probably the honest way to describe it then. we ended up putting the actual guard at the output layer instead of trusting isolation - anything coming back from one agent gets treated as untrusted data before another agent sees it, same as we'd treat text pulled off a random webpage. slower to build than just letting them talk but it means the multiplayer feature doesn't have to also be a security feature