| name | openwebf-app-debugging-devtools |
| description | Debug WebF app runtime issues with Chrome DevTools (console/network/elements) and JS-side troubleshooting. Use when the user mentions DevTools console, network tab, stack traces, blank screen, layout measurement issues, or failing network requests. |
| allowed-tools | Read, Grep, Glob, Bash, Edit, Write, mcp__openwebf__docs_search, mcp__openwebf__docs_get_section, mcp__openwebf__docs_related |
OpenWebF App: Debugging with DevTools
Instructions
- Reproduce and capture signals first: console output, network tab, and any error stack.
- Use DevTools for:
- DOM/console debugging
- network request inspection
- performance profiling
- Apply minimal fixes; prefer targeted logging and small repro steps.
- Use MCP docs to confirm known issues and recommended debugging practices.
If the user’s question is specifically about WebF Go connection/log collection (e.g. devtools:// or WEBF_NATIVE_LOG), prefer openwebf-app-webf-go.
If the user’s issue is dev server reachability / LAN IP / HMR websocket problems, prefer openwebf-app-devserver-network.
More: