ワンクリックで
signalr-bridge
Instructions for operating and configuring the SignalR Bridge for TopstepX.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Instructions for operating and configuring the SignalR Bridge for TopstepX.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Reference for OS and Kernel parameter optimization on the QuanuX Edge.
Reference for using the QuanuX Control CLI (quanuxctl).
Official Figma Developer MCP integration for QuanuX. Allows agents to inspect designs, extract variables, and generate code from Figma files.
The authoritative "School of Architecture" for building QuanuX Extensions (Sidecars). Enforces the QXP protocol, Go runtime preference, and privacy-first security model.
Guidelines for adding functions to the AST translation map for QuanuX-Annex duckdb transpiler
Operating procedures and architecture for the QuanuX-Annex Data Ingestion Engine and NATS JetStream mesh.
| name | signalr-bridge |
| description | Instructions for operating and configuring the SignalR Bridge for TopstepX. |
The SignalR Bridge (quanux-bridge-signalr) is a specialized extension that maintains persistent WebSocket connections to TopstepX's SignalR Hubs. It bridges the gap between the proprietary SignalR protocol and QuanuX's internal messaging.
extensions/python/signalr_bridgeextensions/python/signalr_bridge/extension.yamlextensions/python/signalr_bridge/src/node (Preferred)extensions/python/signalr_bridge/src/flask (Legacy/Fallback)The bridge runs as a standalone process (supervised by QuanuX).
rtc.topstepx.com (User/Market Hubs).This bridge is pre-configured for TopstepX logic but is technically generic.
Key Environment Variables (Managed via quanuxctl topstepx env):
QUANUX_SIGNALR_USER_HUB: URL for the User Hub (Login, Orders, Fills).
https://rtc.topstepx.com/hubs/userQUANUX_SIGNALR_MARKET_HUB: URL for the Market Hub (Quotes, Level 2).
https://rtc.topstepx.com/hubs/marketThe bridge is usually started automatically by quanuxctl bridge or the main server.
To verify functionality manually:
# In extensions/python/signalr_bridge
python src/supervisor.py
The Node runtime exposes a health endpoint:
curl http://localhost:8077/health
Response should include "status": "ok" and "hubUrl".
QUANUX_SIGNALR_USER_HUB is set correctly.SIGNALR_ACCESS_TOKEN which is usually refreshed and injected by the main quanux-topstepx auth flow. If authentication fails, the bridge cannot connect.~/.quanux/logs/quanux-bridge-signalr.log.src/node/index.mjs. Uses @microsoft/signalr client.
npm install in src/node.on(...) listeners in index.mjs.