websocket-devtools-extension

Debug WebSocket connections in Chrome and Edge with message simulation, blocking, and monitoring.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill websocket-devtools-extension-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: websocket-devtools-extension
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/websocket-devtools-extension
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill websocket-devtools-extension-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging WebSocket traffic in the browser is difficult because native DevTools offers limited visibility into frames, no way to simulate server or client messages, and no ability to block traffic for testing error handling. This Skill guides you through using the WebSocket DevTools extension to monitor, simulate, and block WebSocket messages directly inside Chrome or Edge DevTools. ## Core Features & Use Cases - Real-Time Monitoring: Automatically captures all WebSocket connections and messages in the background, even when DevTools is closed, with JSON pretty-printing and filtering. - Bidirectional Message Simulation: Send custom messages as if they came from the client or the server to test handlers without modifying application code. - Traffic Blocking: Intercept and block messages by content, type, or URL pattern to test reconnection logic, retry mechanisms, and error handling. - Use Case: You are testing a trading dashboard's reconnection logic. Block all incoming price_update messages to simulate a network failure, verify the exponential backoff reconnection behavior, then remove the block and confirm recovery. ## Quick Start Install the WebSocket DevTools extension from the Chrome Web Store, open DevTools on a page with WebSocket connections, and use the WebSocket DevTools tab to monitor and simulate messages.

Frequently Asked Questions about websocket-devtools-extension

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor WebSocket traffic in Chrome DevTools?▼

Install the WebSocket DevTools extension, open DevTools with F12, and navigate to the WebSocket DevTools tab. It captures all connections and messages in the background automatically, even if DevTools was opened after the connection was established.

How to simulate WebSocket messages for testing?▼

Use the Simulate tab in the WebSocket DevTools panel to send custom messages in either direction. Choose Client-to-Server or Server-to-Client, enter valid JSON matching your protocol, and the application receives it as if it came from the real endpoint.

Can I block WebSocket messages to test error handling?▼

Yes, the Block tab lets you define rules to intercept messages by exact match, contains match, or regex on content, type, or URL. This is useful for testing reconnection logic, retry mechanisms, and fallback behavior when messages stop arriving.

Does WebSocket DevTools work with Socket.IO connections?▼

Yes, Socket.IO uses WebSocket as its transport, so all protocol messages appear in the panel, including event payloads and heartbeat ping/pong frames. You can simulate Socket.IO events by sending messages in the proper protocol format.

Why is the WebSocket DevTools tab not showing in DevTools?▼

Verify the extension is enabled in chrome://extensions, refresh the page after enabling it, and confirm the extension has permissions for the current site. Also check the browser console for extension errors and try opening DevTools before navigating to the page.

Why are simulated WebSocket messages not received by my application?▼

Check that the JSON is valid, the message structure matches your protocol including all required fields, and the direction is set correctly. Also confirm the WebSocket connection is still open, since messages cannot be delivered to a closed socket.