Chat is an append-only chat.jsonl paged by sequence number: the welcome carries the latest 50 messages and GET /rigshare/api/chat pages further back. The panel loads older pages as you scroll up, keeps your place, and adds date dividers. ComfyUI reuses one slot element between custom sidebar tabs, so each tab now replaces the slot's content instead of appending to it.
ComfyUI RigShare
One ComfyUI rig, a whole team: accounts, live co-editing of every workflow, chat and a GPU monitor
A custom node that turns a single ComfyUI server into a shared workspace. Everyone signs in, opens any workflow, and edits it together in real time while seeing each other's cursors. Fork of daxcay/ComfyUI-Nexus, rewritten for the current ComfyUI frontend.
What it does
- asks everyone to sign in before ComfyUI loads, and creates the admin account on first run
- shares every workflow: people who open the same saved file edit it together, and unsaved tabs join as soon as you edit them
- lets you switch tabs freely, because only the tab on screen syncs
- shows who is online and which workflow they are on, plus live cursors and selections
- lets you follow someone, jumping to their tab and view
- keeps a chat with an unread badge, a blinking icon and a sound
- keeps per-workflow history: snapshots every few minutes, named snapshots, one-click restore
- gives each account permissions to edit, queue, use ComfyUI Manager or administer, enforced by the server and not just hidden in the UI
- lets you restrict a workflow to chosen people, each able to view or edit
- keeps simultaneous edits apart: two people adding or connecting nodes at the same moment both keep their work
- issues personal API keys, so scripts and other apps can call ComfyUI with their owner's permissions
- shows CPU, RAM, and for each GPU the load, VRAM, temperature and power, plus the queue, in a panel tab or a floating widget
- sends execution progress and previews to everyone, not only whoever queued
What this fork adds over Nexus:
- Built for the new frontend. It lives in a sidebar tab and works with workflow tabs and subgraphs. It needs no legacy menu and no litegraph patching.
- Real accounts. A login page, hashed passwords, JWT sessions and API keys replace the shared
/login account passwordchat command and the plaintextadmins.json. - The server is in charge. It checks permissions and identity on every message, so a browser cannot impersonate someone or edit without the right to.
- Every workflow is shared, not a single canvas that everybody fights over.
Screenshots
![]() Shared workflows and history |
![]() Who is online, and on which workflow |
![]() Chat |
![]() Server monitor |
![]() Account and API keys |
![]() Accounts and server settings |
![]() Who can open a folder |
Getting started
Clone into ComfyUI/custom_nodes and restart ComfyUI:
cd ComfyUI/custom_nodes
git clone https://github.com/xiaodoudou/ComfyUI-RigShare.git
Open ComfyUI in a browser. There are no accounts yet, so the login page asks you to create the administrator. Sign in, open the RigShare tab in the sidebar and add your team under Admin → Accounts. That is the whole setup.
Everyone then signs in at the same address. To use the API from a script, create a key under your avatar → API keys:
curl -H "Authorization: Bearer rs_yourkey" http://your-server:8188/api/queue
Behind a reverse proxy, turn on WebSocket support, or nothing will be live. See Reverse proxy.
Documentation
| Installing | Custom node, Docker/compose, first-run setup, upgrading from Nexus |
| Sharing workflows | Live workflows by folder, folder access, snapshots, follow |
| Accounts and permissions | Edit, Queue, Admin, renaming, what viewers can do |
| API access | API keys, websockets, trusted IPs, other apps such as Open WebUI |
| Settings | Panel settings, ComfyUI settings, every key in config.json |
| Reverse proxy | Nginx Proxy Manager, plain nginx, HTTPS |
| Security | How passwords, sessions and keys are protected |
| Development | Running the tests, code layout |
| Changelog | What changed, and when |
Why this exists
I run one ComfyUI box for several people. ComfyUI-Nexus had the right idea, but it was written for the old UI:
- it hid menus with CSS and monkeypatched litegraph internals that no longer exist
- anyone could become admin with a shared password typed into chat
- everybody worked on one canvas, and opening ComfyUI wiped your own workflow
TODO
- Login page, JWT sessions, first-run admin setup
- Per-user API keys
- Every workflow shared, per-workflow snapshots
- Cursors, selections, follow mode
- Chat with badge, blink and sound
- Server monitor with floating widget
- Conflict-free node ids when two people add nodes at the same instant
- Folder access lists (share with specific people)
- Publish to the Comfy registry








