tracekitby labsolute.devDownload for Chrome
CHROME EXTENSION · V1.2.0

Reproduce it.
Resolve it.

Capture the steps, errors, failed requests, and screenshot behind a browser bug—then hand developers a report they can act on.

Version 1.2.0 · Manifest V3 · Team API keys

✓ Local-first✓ No account✓ Upload only when shared
INTERACTIVE DEMOUses sample data only
SESSION READY

Checkout flow · Chrome

02:34
shop.acme.dev/checkout
ACME

YOUR CART

Almost there.
alex@example.com
•••• •••• •••• 4242
Payment failed. Please try again.
1
!
Payment request failedPOST /api/checkout · 500
3
Click “Pay $48.00”button.checkout-submit
LOCAL Your evidence stays in ChromeSAFE Typed values are not recordedFAST Export a report in seconds
HOW IT WORKS

From “it broke” to
here’s exactly why.

No account, project setup, or SDK required.

1

Install

Download the ZIP, open chrome://extensions, and choose Load unpacked.

2

Reproduce

Start Tracekit on the page under test, then follow the steps that trigger the bug.

3

Share

Review Expected and Actual results, then copy Markdown or download the evidence.

PRODUCT WALKTHROUGH

Evidence builds itself
while you test.

Tracekit turns browser activity into a readable timeline, connects errors to the step that caused them, and prepares a structured handoff.

  • Start from any website
  • Mark the exact failure moment
  • Export one clean report
Tracekit · Recording
01Click “Confirm order”button.checkout-submit
02Request failed · POST/api/checkout · HTTP 500
03Issue marked by testerScreenshot captured locally
REPORT READYPayment fails after submitting checkout4 steps · 1 error · 1 screenshot
WHAT IT CAPTURES

The useful context.
None of the noise.

01

Action timeline

Records clicks, page changes, and form interactions in the order they happened.

02

JavaScript evidence

Captures console errors, uncaught exceptions, and rejected promises.

03

Failed requests

Adds HTTP 4xx/5xx responses and network failures without storing request secrets.

04

Visible screenshots

Takes a screenshot when you mark an issue or finish the session.

05

Local-first storage

Session evidence stays in Chrome unless you explicitly choose to share it.

06

30-day share links

Creates an unlisted cloud report with evidence and screenshot, then deletes it automatically.

PRIVACY BY DESIGN

Your test data
stays yours.

Recording stays in Chrome by default. A report is uploaded only after you review it and confirm sharing; the unlisted report is deleted automatically after 30 days.

Read the privacy policy →
PERMISSIONWHY TRACEKIT NEEDS IT
Read page interactions

Builds the reproduction timeline. Text field values are excluded.

Observe failed requests

Records status, method, and redacted URL for failed network calls.

Capture visible tab

Takes a screenshot only when you mark an issue or stop recording.

Store locally

Keeps the active and latest session in your own Chrome profile.

Share on request

Uploads the reviewed report and screenshot only when you confirm Share report.

COMPATIBILITY

Built for desktop Chrome

Designed for the current stable release of Google Chrome on macOS, Windows, and Linux.

  • Regular HTTP and HTTPS pages
  • Chrome Manifest V3
  • Developer mode installation
LIMITATIONS

Clear about the edges

Version 1.2.0 does not record Chrome internal pages, full video, successful network traffic, or direct Jira/GitHub integrations.

Request a feature →
CHANGELOG

Version 1.2.0

Added team-scoped API keys, configurable key expiry, protected Admin management, and branded team report URLs.

Contact support →
FAQ

Questions,
answered plainly.

Does Tracekit upload my test data?+

Only when you review the report and press Share for 30 days. Recording remains local by default, and shared reports expire automatically.

Does it record passwords or form values?+

No. Tracekit records that a field changed, but does not store the value typed into text, email, phone, number, or password fields.

Which pages can it record?+

It records regular http:// and https:// pages. Chrome internal pages such as chrome://settings cannot be accessed by extensions.

Can I send reports to Jira or GitHub?+

You can paste the team-scoped shared report link or attach the exported files anywhere. Direct integrations are not included in version 1.2.0.

How do I update the extension?+

Download the newest ZIP, replace the unpacked folder, then select Reload on the Tracekit card at chrome://extensions.

Tracekit logo
READY TO TRACE THE BUG?

Less back-and-forth.
More fixes.

Download for Chrome