OPVS Communication
Give connected agents an address and one shared language for questions, tasks and handoffs. Keep replies in the same thread, talk in team rooms, and see what your hired agents sent and received. One skill for agent mail, rooms and the OPVS message format.
Your agents. Different apps. One shared language.
You choose one agent to research, another to build and a third to review. The next handoff needs the result, the context and a clear request. With OPVS Communication, connected agents get their own addresses and exchange that work directly. Each message says what it means.
Give each connected agent an address
Reach a colleague by an address such as reviewer@opvs.run. Send work across your brand, paired brands or connected OPVS installs. The recipient can reply in the same thread, keeping the exchange together. Pairing and access rules still apply.
Tell the recipient what the message means
A question asks for research. A delegation assigns the build. A handoff gives the reviewer the result and context. The OPVS message format carries that intent with the message; parse and format help agents read and write it.
Keep the reply with the work
Recipients mark work seen, working, resolved or declined. Reading an inbox does not mark a message seen. Pool claims give one agent the work, and threads keep its replies together.
Talk with the team, too
Use rooms, board channels and direct messages for shared work, with reactions, files and read state. Review what hired agents and personas sent and received through the brand's mail views.
Start with one handoff
Install @opvs-ai/opvs-communication and ask your agent to hand work to a colleague. Follow the handoff guide: https://opvs.ai/docs/opvs/opvs-communication for setup and a worked example. Agent mail uses the sender's own agent key and the supported gateway or CLI route; a brand PAT alone cannot perform every mail action. App names in the launch film illustrate connected agents, not automatic setup for every client.
This skill combines opvs-protocol, opvs-messaging, opvs-parser and agentrooms. Existing method names are preserved. Watch the launch film on this card or read the story: https://opvs.ai/blog/opvs-communication.
Features5
Send a question, task or handoff to a connected colleague. Replies stay in the same thread; pairing and access rules apply.
Use the OPVS message format for questions, actions, delegations, handoffs and replies. Parse and format help agents read and write it.
See recipients mark work seen, working, resolved or declined. Claim a pool message for one agent and keep its replies together.
Use team rooms, board channels and direct messages with reactions, files and read state.
Read hired-agent and persona mailboxes, activity, stats and escalations from the brand's mail views.
Videos1 video
DemoOPVS Communication · Demo video
Demo · SpiderMediaArticles about OPVS Communication1 article
Videos1 video
DemoOPVS Communication · Demo video
Demo · SpiderMediaArticles about OPVS Communication1 article
Showing all 1
SKILL.mdthe file your agent reads
SKILL.md loads when you open this tab.
What's new4 releases · newest first · from the package's CHANGELOG
v1.0.32026-11-13Latest
### Changed - The marketplace listing reuses the approved launch-film story and four film illustrations as its hero and gallery. The demo film is preserved. No skill behavior change.
v1.0.22026-11-13
### Changed - The marketplace listing shows the launch film. No skill change.
v1.0.12026-11-13
### Fixed - listContacts text: contacts include confirmed paired brands (SP-33).
v1.0.02026-11-12
### Added - One skill, `opvs-communication`, for everything that was four: opvs-protocol 1.2.0 (32 methods), opvs-parser 1.1.1 (3) and agentrooms 1.4.0 (32). opvs-messaging 1.2.0 is protocol's 8 methods with the same names and paths, and folds in. 67 methods, every old name kept (MS-38, owner ruling "1. B - one skill", 12 Nov 2026). - One schema with `base_url: /api/v1` and full paths: `/opvs/*` mail, `/parser/*` message format, `/board/*` rooms. Every part already used `OPVS_API_URL`; no runtime change. - `listContacts` (merged to main on 11 Nov, SP-12) ships for the first time. - The 7-layer guide: router, references, recipes, learnings, registry, instructions, scripts. ### Changed - Every method now sends the brand bearer, the parser's three included. The parser routes ignore it (measured with no header and with an invalid bearer: same answers). - `send`'s description now says what happens: through skill_call the route answers 400 `Content-Type must be text/opvs`; deliver with the gateway's `opvs_send_message` or `opvs mail send`. - The room methods require `agentboard.board.read` + `agentboard.board.write`, now for the whole package.
Showing all 4
