NodeLume — Understand What Happened in Your App

Analyze pages, user flows, and network activity locally, then export clear troubleshooting context for AI.

NodeLume helps you troubleshoot web applications by turning the behavior of a user-selected browser tab into a local visual timeline. Use it to investigate a reported problem, run a general page check, or record a complete user flow. NodeLume connects page structure, trusted user actions, navigation changes, visible errors, requests, responses, and timing signals so you can see what happened before an issue. Key features: • Analyze recent interactions around a reported problem. • Create a visual map of pages, actions, requests, responses, and services. • Record a complete flow in one user-selected browser tab. • Review request, response, payload, header, status, and timing details. • Surface deterministic signals such as slow requests, repeated calls, possible N+1 patterns, silent failures, cycles, and external dependencies. • Keep analyses, recordings, screenshots, and history in local extension storage. • Generate a privacy-reviewed HAR file or a structured troubleshooting message for manual sharing with an AI tool. Nothing is sent automatically. • Manage saved domains and delete individual captures or all history for a domain. • Use the interface in German, English, Spanish, French, Brazilian Portuguese, or Japanese. Privacy and site access: Application captures are processed and stored locally in the browser. They are not uploaded to NodeLume. NodeLume's API is used only for installation registration, authentication, account access, subscription verification, checkout session creation, and account management. Domain observation is enabled only after the user approves access to that origin. A full recording may locally store full URLs and query strings, screenshots, request and response headers, cookies or authentication tokens present in those headers, request bodies, and textual or JSON response previews. Full recording requests optional access to all sites because one selected tab can call APIs on multiple domains. Recording logic processes only the selected tab, and the broad permission is removed when the recording ends normally or is stopped for inactivity. Exports are created only after a user action. The recommended export mode masks recognized sensitive values and omits request bodies by default. The user reviews the options before downloading and decides whether to share the resulting file outside NodeLume. Account and purchases: NodeLume requires sign-in and an active NodeLume subscription. Current plans, trial availability, billing terms, and cancellation options are shown on the NodeLume website. Checkout and subscription management open on the NodeLume website, and Paddle handles payment information as Merchant of Record. ```