Mod the network

OpenVibe is open source end to end, and every product has an API. These are the ways to change how it works for you, for your community, or for everyone, today.

Extend it today

• Your own site on the networkSign-in with OpenVibe, the shared navbar and footer, and the home-page kit (hero, numbers, cards and rails, spotlight, FAQ, "Part of OpenVibe") that the network's own sites are built from.The home-page kit →
• A chat botA bot in its own room that always says it is a bot, from the chat-bot example, or Vibe and your own AI members in any room you run.chat-bot example →
• Alerts and work into a team roomA workspace room on OpenVibe.Chat takes signed hooks: a Watch firing, an OpenVibe event or a line of text arrives as a message from Vibe, and can queue a task for the team or for your own computer.Rooms →
• Watches that actFollow any page, feed or API, and when it changes: notify you, call a signed webhook, give an agent a task, start a job on your own machine, or open a coding task.OpenVibe.Watch →
• Agents of your ownPersonal agents on OpenVibe.Actor with your instructions and tools, run now or on a schedule, under your own allowance.Actor docs →
• Robots, devices and computersWrite a driver as a plugin for OpenVibe.Node, pair the machine, and drive it through Bot's one gate with roles, limits and an e-stop. Share a computer's screen into a room.Bot docs →
• Game worldsBuild a world in the OpenVibe.Games editor and publish it: anyone can join it, and it shows up in search.Worlds →
• React to the whole networkSubscribe to events (streams going live, posts, recordings, jobs) with durable cursors or signed webhooks, and build on them.event-subscriber example →
• Change OpenVibe itselfEvery service is open source. Propose a change on OpenVibe.Codes, where OpenVibe is built, or send a pull request to the repository it touches.OpenVibe.Codes →

Packaged mods

A packaged mod changes a product from the inside: a game's rules, an overlay on a stream. It is described by a mod manifest (mods.mod-manifest@1 in openvibe-contracts): its id, version, publisher, target runtime, the capabilities it asks for, its assets and its budget. Installing one gives it its own principal on OpenVibe.Network, granted only the capabilities that were approved, and revoking that grant stops it at once.

1. Start one from the template: npx --package=https://codeload.github.com/OpenVibers/OpenVibe.Examples/tar.gz/refs/tags/v0.3.0 create-openvibe-app my-mod --template mod
2. Check its manifest against the pinned contracts on the manifest validator, which also says which capabilities an install could grant.
3. Ask for it to be installed: open a proposal on OpenVibe.Codes.

What waits: today only staff install mods (with the approved capabilities), because how a mod release is signed and how it is reviewed are open decisions for the owner (ADR-013, amendment of 2026-09-24). Mods that run their own code also wait for sandboxed hosting. Until then a mod is data plus the scripting each game's own sandbox provides. This page will say when that changes.

Where to start

1. Create a project and add a sandbox app: its sandbox capabilities are approved at once.
2. Pick a card above, or start from an example: OpenVibe.Examples (MIT, each with a smoke test).
3. Read the platform reference and the SDK, generated from the same contracts the services enforce.