Record your first bug

You've installed the extension and signed in — time to capture a real bug. Tirs gives you two ways to do it today, and whichever one you pick, the full story travels with the capture: video, console logs, network requests, environment details, and, for recordings, reproduce steps written by AI from what actually happened in the session.

Pick the right action

Open the popup and choose a capture mode: Current Tab for most bugs, or Window / Screen when the problem spans more than one tab. Then pick your action:

• Start Recording — the bug hasn't happened yet. You're about to reproduce it, and you want Tirs rolling from the first click.
• Rewind — the bug already happened. On sites where you've enabled Rewind, your browser keeps a rolling buffer, so the last moments are already saved — the first click on a new site simply asks to turn it on. Click Rewind and Tirs packages them retroactively — no need to reproduce anything.
• Capture Screenshot (coming soon) — the bug doesn't move. A broken layout, a wrong label, a misaligned button. One frame is enough, and the context still comes attached.

Record and stop

1. Click Start Recording and walk through the bug the way a user would hit it.
2. When you're done, open the popup again and stop the recording.
3. Tirs uploads the session and shows a success card with a share link — click View The Session to open it in your workspace.

• Optional redaction runs before upload: turn on Redact Sensitive Data in the extension settings, and passwords, card numbers, tokens, and other sensitive values are masked in your logs before anything leaves your browser.

What gets captured automatically

Every capture — recording or Rewind — packages the same context. No setup, no copy-pasting:

• Screen recording — a video of exactly what happened.
• Console logs — every error and warning from the session.
• Network requests — method, status, and URL for each call.
• Environment — device, browser, OS, and viewport size.
• Reproduce steps — written by AI from the session itself for recordings, so the report arrives ready to read.

Find your session

Captures land in your workspace at app.tirs.dev. Open the session to watch the replay, check the logs and requests, and adjust the AI-drafted title, description, or steps before you share it.

Send it to a ticket

1. Open the session and choose where the ticket should go: Jira or Azure DevOps — with GitHub and Linear coming soon.
2. Review the pre-filled title and description — edit them if you like.
3. Create the ticket. The replay, logs, and environment details go with it, so developers get everything without asking you a single follow-up question.

Next steps

Connect your issue tracker so tickets land where your team already works — start with "Connect Jira".