# Debug or profile a live web app from its console, network and traces (slim)

> Debug or profile a live web app from its console, network and traces: 2 companies fully do it, 8 with a limit, 30 carry the tag. Every listing in Browser automation with the reason and a source.

- Full: https://www.anchorterminal.com/niches/browser.debug-live-page/index.md (~1,800 tokens) · this version ~330 tokens · JSON https://www.anchorterminal.com/niches/browser.debug-live-page/index.json · canonical https://www.anchorterminal.com/niches/browser.debug-live-page/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Two or three companies' docs show a full fit. Full fit: 2 companies, with a limit: 8, tagged: 30. Weight 10, 7 accounts.

Done when: The agent names the failing request, console error or long task with its source location, from one trace or network capture, and the data lands in a file rather than the context when it is large.
yes: agent-browser (Vercel Inc.)
yes: chrome-devtools-mcp (Google LLC)
caveat: anchor-browser (Anchor Forge Inc.)
caveat: browserbase (Browserbase, Inc.)
caveat: browserless (browserless.io, Inc.)
caveat: bx-playwright (Ortus Solutions, Corp.)
caveat: kane-cli (TestMu AI (formerly LambdaTest))
caveat: playwright-mcp (Microsoft Corporation)
caveat: puppeteer (Google LLC)
caveat: selenium (Software Freedom Conservancy)
caveat: steel (Nen Labs, Inc.)

Data: https://www.anchorterminal.com/api/v1/use-cases/browser.debug-live-page.json
