revia-bridge
Standalone, MCP-free realtime bridge plugin for Revia.
It runs a background daemon that connects directly to Revia's raw WebSocket
(wss://revia.devshub.ai/api/v1/mcp/ws), handles real-time inbound events, and
answers bidirectional agent chat by shelling out to a configurable CLI command
(e.g. codesync ask "{message}" or claude -p "{message}").
The daemon lifecycle is managed automatically by plugin hooks: SessionStart
starts it, SessionEnd/Stop stop it.
Supersedes
revia-mcp. The old MCP-based client is deprecated in favor of this package, which has zero MCP dependencies, is installable in any coding agent (not just MCP-capable ones), and runs as a self-managed background daemon rather than a per-session MCP server process.
Install
From PyPI
pip install revia-bridge
revia-bridge init # interactive one-time setup
revia-bridge run --daemon
CodeSync
codesync plugin marketplace add /path/to/plugins/revia-bridge
codesync plugin install revia-bridge@revia --scope user
Claude Code
claude plugin marketplace add /path/to/plugins/revia-bridge
claude plugin install revia-bridge@revia
The marketplace is named
revia; the plugin is namedrevia-bridge. The install spec is thereforerevia-bridge@revia.
Configure
Run the interactive initializer:
revia-bridge init
It prompts for:
| Field | Default | Notes |
|---|---|---|
| Agent token | (required) | rvagent_... from Revia → Settings → Coding Agent |
| Reply command | codesync ask "{message}" |
{message} and {chat_id} are substituted |
| Agent name | Revia Bridge |
Shown in Revia's agents_list |
| WebSocket URL | wss://revia.devshub.ai/api/v1/mcp/ws |
This writes ~/.codesync/revia-bridge.json (override with
REVIA_BRIDGE_CONFIG). See SKILL.md for the full key reference.
Manual daemon control
revia-bridge run --daemon # start detached (PID + log under ~/.codesync)
revia-bridge status # running? last event time?
revia-bridge stop # SIGTERM via PID file
Development
cd plugins/revia-bridge
python -m pytest -q
The package is a plain Python project (pyproject.toml) with a
revia-bridge console-script entry point. It has zero MCP dependencies —
only websockets.
Metadata
Release files for revia-bridge 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| revia_bridge-0.1.0.tar.gz | 22.9 kB | Without provenance | Details for revia_bridge-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| revia_bridge-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for revia_bridge-0.1.0-py3-none-any.whl |
Total release size: 50.5 kB
Release files / revia_bridge-0.1.0.tar.gz
| Download URL | revia_bridge-0.1.0.tar.gz |
|---|---|
| Size | 22.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ece9da6a567e017392a671a265e432fce2fbfb4cc348d91dc4acbf21501611df
|
|
BLAKE2b-256 checksum How to use checksums |
9b679fae24dfe1e1ac722527b95fdc3f52a2cb210a149b9ee932fff94f051879
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / revia_bridge-0.1.0-py3-none-any.whl
| Download URL | revia_bridge-0.1.0-py3-none-any.whl |
|---|---|
| Size | 27.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2061e6b186d0e5e30e4c25cb63878185567be42f769d426c04ca6d35059eeb73
|
|
BLAKE2b-256 checksum How to use checksums |
308b1719772aab733ba35531ae27664dbfe51feab293b15b153a82430d1086d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for revia-bridge 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.