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

fix: browser bug with plugins, and improve joining

Browse Source
This commit is contained in:
SocksOnHead
2026-05-04 23:35:40 +02:00
parent a49e18b9f0
commit 0f6cb3ee77
7 changed files with 264 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
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
@@ -1429,4 +1429,4 @@ export function deactivate(context) {
- Local REST API: Developer Guide -> Local REST API.
- Plugin manifest: Plugin Development -> Manifest Model.
- Capabilities: Plugin Development -> Capabilities.
- Focused plugin API examples: Plugin Development -> API Reference and its API subpages.
- Focused plugin API examples: Plugin Development -> API Reference and its API subpages.