myxelium/Toju
1
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects 2 Releases 25 Wiki Activity

fix: recurriing network issue
All checks were successful
Queue Release Build / prepare (push) Successful in 18s
Details
Deploy Web Apps / deploy (push) Successful in 6m32s
Details
Queue Release Build / build-windows (push) Successful in 26m8s
Details
Queue Release Build / build-linux (push) Successful in 40m18s
Details
Queue Release Build / finalize (push) Successful in 42s
Details

Browse Source
This commit is contained in:
SocksOnHead
2026-04-30 04:04:34 +02:00
parent b1fe286be8
commit a49e18b9f0
16 changed files with 522 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs-site/docs/developer/llm-plugin-builder-guide.md
View File

@@ -54,12 +54,12 @@ There are three communication boundaries a plugin author must understand:
1. Signaling plane
Angular renderer <-> WebSocket signaling server
Used for identity, joining servers, presence, typing, plugin requirements,
server-relayed plugin events, WebRTC offers, answers, and ICE candidates.
server-relayed plugin events, WebRTC offers, answers, and ICE candidates.
2. Peer plane
Angular renderer <-> WebRTC peer connections <-> other clients
Used for media and data-channel events: chat messages, message sync,
attachments, voice state, screen/camera state, and plugin message bus data.
Used for media and data-channel events: chat messages, message sync,
attachments, voice state, screen/camera state, and plugin message bus data.
3. Desktop/local plane
Angular renderer <-> Electron preload bridge <-> Electron main process