EchoLog
Background API payload logger for specific engineering domains.
As of June 2026, EchoLog has 4 users in the Developer Tools category.
Usersno change0%
4
4
Ratingno change0%
—
— reviews
Reviewsno change0%
—
Version
1.2
Manifest V3
90-day change · In the last 90 days this extension 1 version update, changed permissions.
History
2 snapshotsTracking since Jun 2, 2026.
Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
| Date | Users | Rating | Reviews | Version |
|---|---|---|---|---|
| Jun 2, 2026 | — | — | — | 1.0 |
| Jun 8, 2026 | — | — | — | 1.0 |
| Now | 4 | — | — | 1.2 |
Changelog
- Jun 8, 2026description
EchoLog started as a personal fix. As a product manager, I kept running into the same wall — a bug would surface during testing, and the first thing a developer would ask is "did you have DevTools open?" The answer was always no. Which meant reproducing everything from scratch, hoping the bug would show up again. So I built EchoLog to stop losing time to that one question. What it does: — Runs silently in the background, no DevTools needed — Captures all XHR/Fetch request payloads and responses automatically — Targets only your allowlisted internal or staging domains — When something breaks, click the icon and the full request history is already there If you've ever been on either side of that conversation — the PM/QA who forgot to open DevTools, or the developer waiting for a reproduction — this was built with that moment in mind.
EchoLog started as a personal fix. As a product manager, I kept running into the same wall — a bug would surface during testing, and the first thing a developer would ask is "did you have DevTools open?" The answer was always no. Which meant reproducing everything from scratch, hoping the bug would show up again. So I built EchoLog to stop losing time to that one question. What it does: — Runs silently in the background, no DevTools needed — Captures all XHR/Fetch request payloads and responses automatically — Targets only your allowlisted internal or staging domains — When something breaks, click the icon and the full request history is already there If you've ever been on either side of that conversation — the PM/QA who forgot to open DevTools, or the developer waiting for a reproduction — this was built with that moment in mind. v1.1 — Added support for multiple global tracking sessions and background payload extraction
- Jun 8, 2026host_permissions
(empty)
<all_urls>
Permissions & access
- Permissions
- debuggerstoragetabs
- Host access
- <all_urls>
Screenshots
About
EchoLog started as a personal fix. As a product manager, I kept running into the same wall — a bug would surface during testing, and the first thing a developer would ask is "did you have DevTools open?" The answer was always no. Which meant reproducing everything from scratch, hoping the bug would show up again. So I built EchoLog to stop losing time to that one question. What it does: — Runs silently in the background, no DevTools needed — Captures all XHR/Fetch request payloads and responses automatically — Targets only your allowlisted internal or staging domains — When something breaks, click the icon and the full request history is already there If you've ever been on either side of that conversation — the PM/QA who forgot to open DevTools, or the developer waiting for a reproduction — this was built with that moment in mind. v1.1 — Added support for multiple global tracking sessions and background payload extraction
Technical
- Version
- 1.2
- Manifest
- V3
- Size
- 4.47MiB
- Min Chrome
- 88
- Languages
- 1
- Featured
- No
Metadata
- ID
- mdanjdeopijidmdlaeghccoiempllpgd
- Developer ID
- u827328e19b7b00ade864cba661e01012
- Developer Email
- [email protected]
- Created
- Jun 1, 2026
- Last Updated (Store)
- Jun 4, 2026
- Last Scraped
- Jun 8, 2026
- Website
- —
- Support URL
- —
Data sourced from the Chrome Web Store · last verified Jun 8, 2026.