Lightstreamer Workbench από imom39a

Lightstreamer Workbench adds a developer-tools panel for applications using the official Lightstreamer Web Client.

Inspect clients, Sessions, Subscriptions, listeners, Item Updates, snapshots, COMMAND key lifecycles, and outbound Client Messages. Select Runtime Scope, read Ordered Evidence, and inspect complete Context. Find, Filter, Capture, Coverage, and Live/Frozen investigation work independently.

Create protected Local Injection Drafts from captured updates or live COMMAND targets. Edit and validate raw JSON, then deliver an Item Update locally through the application's normal listeners. Compose ordered Scenarios with Steps and Checkpoints. Local Injection does not contact Lightstreamer Server; application listeners may still cause effects.

Review Server Injection Client Messages and every send argument before one deliberate call through the page-owned client's current Session. This does not create an inbound Server Update. Processed describes the message outcome, not a downstream business effect. Unknown outcomes are never retried automatically.

Optionally connect the local npm MCP companion, lightstreamer-workbench-agent 0.1.8. One companion serves Chrome and Firefox panels. Agents can inspect retained Evidence, query COMMAND/stream state, prepare Local Injection Scenarios, and prepare Server Injection. Each agent Server Injection requires a person's approval of the exact message and send arguments in the panel before one send. Repeated requests retrieve the receipt. No arbitrary page evaluation or history clearing is exposed through MCP.

Each Panel Session owns a temporary rolling Event History: up to 100,000 records or 256 MiB in IndexedDB, or 25,000 records or 128 MiB in memory fallback. Retention removes the oldest accepted prefix while Capture continues. Controlled Close attempts erasure; abnormal termination may leave residual data until a safe cleanup. A new panel starts empty. JSON and offline HTML exports are deliberate local downloads.

Firefox requires installation consent for sharing captured application data with the local companion and configured MCP client/model provider. Arbitrary application fields may contain sensitive information. Agent access starts On for a new panel and can be turned Off. Local authentication is off; use a trusted development computer.

Usage analytics starts Off. It sends fixed Workbench feature names, engagement time, coarse outcomes, version, event time, and a random installation identifier to Google Analytics only after both optional Firefox permission and the Workbench setting allow it. Captured Evidence, inspected URLs, and typed text are excluded. Cancel or Deny leaves analytics Off and Workbench usable. Opt-out or native permission removal stops collection and erases analytics identifiers.

Desktop Firefox 140+ only; private browsing is disabled. No advertising, account sign-in, remote executable code, or maintainer collection server. Read the privacy policy before sharing application data.