Item logo image for TheOneX

TheOneX

ExtensionDeveloper Tools8 users
Item media 4 (screenshot) for TheOneX
Item media 1 (screenshot) for TheOneX
Item media 2 (screenshot) for TheOneX
Item media 3 (screenshot) for TheOneX
Item media 4 (screenshot) for TheOneX
Item media 1 (screenshot) for TheOneX
Item media 1 (screenshot) for TheOneX
Item media 2 (screenshot) for TheOneX
Item media 3 (screenshot) for TheOneX
Item media 4 (screenshot) for TheOneX

Overview

Record network traffic (HAR) and user actions together on one clock, then export HAR, Recorder JSON and AI-ready test context.

Record a test session once and get everything you need from it: the network traffic, the user actions, and how they connect. TheOneX captures two things at the same time on the tab you choose, using one shared clock: - Network traffic, saved as a standard HAR 1.2 file: every request and response with headers, cookies, post data, response bodies, timings and redirects. - User actions, saved in Chrome DevTools Recorder format: clicks, typed values, key presses and navigations, with several selectors per element (ARIA, CSS, XPath, text). Because both are recorded together, TheOneX links each API call to the action that triggered it. You can see which click called which endpoints and which route changes followed. BUILT FOR ACCURATE REPLAY - Typed values are captured even when the field never loses focus, such as search-as-you-type. - Clicks inside shadow DOM and inside iframes (same-site and cross-site) are recorded with the selectors and frame path DevTools Recorder needs to replay them. - Ambiguous selectors are dropped, so replay never clicks the wrong one of several identical buttons. - Polling and heartbeat requests are detected and kept apart from the actions you performed. - Traffic from cross-site iframes and web workers is included in the HAR. EXPORTS - HAR file: opens in Chrome DevTools, Charles, Fiddler and other HAR viewers. - Recorder JSON: imports into Chrome DevTools > Recorder. - Merged session file: one JSON with actions, requests and route changes already linked, plus a time-ordered timeline. Can be split back into the HAR and Recorder files. - Context JSON: a compact, structured summary of the flow for AI coding agents. - Flow document (Markdown): a plain-language description of what happened, for developers, testers and documentation. - Automation brief (Markdown): a framework-neutral brief with selectors, expected routes and API assertions, ready for an AI agent to turn into WebdriverIO, Playwright or other tests. HOW TO USE 1. Open the web application you are testing. 2. Click the extension icon and press Start session. Allow access to the site when Chrome asks. 3. Run your test flow. 4. Press Stop and save, then download the files you need, now or later. PRIVACY Recordings never leave your computer. There is no server, account, analytics or tracking. Cookies and authorization headers are redacted by default, and typed passwords are masked in both the recording and the HAR. Sessions stay in your browser until you delete them. GOOD TO KNOW - While recording, Chrome shows a bar saying the extension started debugging the browser. This is how Chrome lets extensions read network traffic. Closing the bar ends the session. - Records one tab at a time. Requires Chrome 125 or later.

Details

  • Version
    1.2.0
  • Updated
    October 11, 2026
  • Size
    40.02KiB
  • Languages
    English
  • Developer
    Email
    Gokulganapathy95@gmail.com
  • Non-trader
    This 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

Manage extensions and learn how they're being used in your organization

TheOneX 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.

TheOneX handles the following:

Authentication information
Web history
User activity
Website content

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
Google apps