DevLogBus Browser Tap
Overview
Publishes Chrome tab debugging events to a local DevLogBus daemon.
DevLogBus Browser Tap is a local-first developer tool for sending browser-side debugging events into a locally running DevLogBus daemon. Attach it to the active tab when you want Chrome console calls, runtime exceptions, browser log entries, and network request or response events to appear beside backend service logs in DevLogBus. Detach it when you are done. The extension publishes only after you explicitly attach it to a tab. By default, it sends records to http://127.0.0.1:7423, the HTTP listener exposed by devlogbusd on your own machine. DevLogBus does not operate a cloud collection service for this extension. Capture controls let you turn console, runtime, browser log, or network capture on and off. Scope controls let you allow or deny specific hosts or URL patterns. Redaction controls remove common authorization headers, sensitive URL parameters, and cookie values before records are published. DevLogBus Browser Tap is intended for local development and debugging workflows, not production monitoring.
0 out of 5No ratings
Details
- Version1.2.0
- UpdatedJune 1, 2026
- Offered byDan Sherwin
- Size56.83KiB
- LanguagesEnglish (United States)
- Developer
Email
dan@dsherwin.net - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
DevLogBus Browser Tap has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
DevLogBus Browser Tap handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site