For developers, product people and support staff who hit a bug while using the app.

Your setup

Say this to Certyn

On staging, after I apply coupon SAVE10 the cart total goes negative. Screenshot and HAR attached. Reproduce it and file it if it is real.

Reads your text and the attached files.
Searches for an existing issue (app.find). If one matches, it shows it instead of filing a second one.
Reproduces the bug. It can try the steps on the chat's Machine while you watch. For an issue with Certyn's own screenshots and steps, it starts a short run with your steps (app.run.create). It says the length and asks first.
The run files the bug as a Certyn issue with its evidence, after a duplicate check. To send it to Jira, Linear or GitHub, Certyn asks again (tracker.issue.create).

One issue with steps, expected and actual result, and the run's screenshots. Or the issue that already tracks it.
If it does not reproduce: what Certyn tried, so you can add the missing detail.

Early access, Chrome only. Request it on the extension page, then connect it at /app/extension.
It opens an Ask Certyn panel on Linear, Jira, GitHub, Sentry, GitLab, Notion, Slack and Figma, or on any page when you click its icon (Cmd+Shift+C on macOS, Ctrl+Shift+C elsewhere).
It sends your question and the page's address only. It does not take screenshots, read the page, or record console or network logs.
The panel shows text answers. Forms and approval prompts need the web chat.

Certyn cannot see your browser, only what you attach and write. Name the environment, the account type and the exact steps.
Your files help Certyn understand the bug. They are not added to the issue; the issue gets the run's own evidence.
Files: images up to 5 MB, a HAR or log up to 10 MB, 15 MB per message.
A bug that needs your account's data needs a test account with the same data (sign_in form).