Native connection
Jira Cloud
Create a bug with the recorded steps, expected and actual behavior, and a link to the replay.
SAMELOGIC / INTEGRATIONSKeep the context.
Keep the context.
Keep your tools.
Bring the steps behind a bug into the tools your team already uses. Create an issue, share element details, or give your coding assistant evidence to work with.
Free extension for desktop Chrome. Try it before signing up.FROM THE RECORDINGSample data
Renewal quote mismatch4 recorded steps · 00:12
BUG REPORT
Renewal quote doesn’t match the seat count
- 01 Open seat renewal
- 02 Add two seats, then calculate renewal
Expected3 seats · $65/year
Actual2 seats · $47/year
Recording attachedReplay the steps. Inspect the affected element.
01
Record what happened. Capture the path to the bug.
02
Review the evidence. Add the context that matters.
03
Move the work forward. Use the right connection.
BUILT AROUND YOUR WORKFLOW
Find your team’s tools.
Explore what you can use today, how each connection works, and the integrations you can request next.
Available today
Native connections, exports, and developer access.
Native connection
Linear
Turn a reviewed recording into a Linear issue, with the context your team needs to begin investigating.
Native connection
Slack
Share an inspected element, its screenshot, and selected details in a channel or thread.
Native connection
GitHub Actions
Run replay validation through a configured GitHub workflow and review the run status alongside the recording.
Test export
Playwright
Use the recorded actions as the starting point for a Playwright test draft your engineer can review.
MCP connection
Claude Code
Give Claude access to authorized recordings, steps, and element evidence while you investigate a bug.
MCP connection
OpenAI Codex
Bring the recording and its supporting evidence into your Codex investigation through Samelogic’s MCP connection.
Manual MCP setup
Cursor
Connect a compatible Cursor MCP client to the recording evidence your Samelogic token is allowed to read.
Manual MCP setup
VS Code / Copilot
Make authorized recording context available to your coding assistant through VS Code’s MCP configuration.
Selector snippets
Cypress
Copy an inspected element’s selector into a Cypress snippet and use it in a test you maintain.
Selector snippetsSelenium
Use inspected CSS or XPath selectors in Selenium locator snippets for your existing browser tests.
API access
Samelogic API
Build a custom workflow around element data and replay metadata when your team needs a different connection.
What would you connect next?
These integrations are not yet supported. Explore an idea and tell us what you need.
Not yet supported
GitHub Issues
A proposed way to create a repository issue with the report, recording, and eventual fixing pull request.
Not yet supported
Sentry
Connect the steps someone took with a selected application error in Sentry.
Not yet supported
Microsoft Teams
Bring a concise bug summary and recording link into the channel where your team discusses the work.
Not yet supported
Azure DevOps
Carry a recording into an Azure Boards bug, alongside the build and test result that matter.
Not yet supported
GitLab
Keep bug evidence beside the GitLab issue, merge request, and verification result.
Not yet supported
Zendesk
Keep the customer’s support ticket connected to the recording and engineering investigation.
Not yet supported
Intercom
Move a customer-reported bug into engineering while keeping the original conversation in view.
Not yet supported
BrowserStack
Investigate whether a reported failure also appears in another browser or test environment.
Not yet supported
TestRail
Bring recording evidence into the test runs where your QA team tracks failures and retests.
Not yet supported
Figma
Place the intended design next to the behavior someone actually recorded.
Not yet supportedXray for Jira
Associate the recording with a Jira test execution and its linked defect.
Not yet supported
Datadog
Give engineering the selected error or diagnostic link that helps explain a recorded failure.
Not yet supportedQase
Link the evidence behind a failed check to its test result, defect, and eventual retest.
Not yet supported
PostHog
Place a reported bug beside selected product events or recordings already in PostHog.
Not yet supportedLaunchDarkly
Explain a difference in behavior with the feature-flag values the application used at the time.
Not yet supported
Confluence
Keep the bug’s evidence in a release review, incident write-up, or team knowledge base.
Not yet supported
Notion
Add the bug’s story to the product notes, QA plans, or incident documents your team maintains.
Not yet supportedSauce Labs
Bring a reviewed browser test into your existing cloud test environment and link back to its result.
Not yet supported
Vercel
Identify the preview or deployed version where a bug occurred and where the fix can be checked.
Not yet supported
ClickUp
Give a product or QA task the recording and report details behind the work.
Not yet supported
Zapier
Route a report to another tool when your workflow needs a connection beyond the native options.
Your workflow belongs here, too.
Request an integrationTell us the tool and the task you want to connect.
BEFORE YOU CONNECTA little clarity.
A little clarity.
A better handoff.
Choose the connection that fits the work, and review what travels with it.
Privacy & access controlsWhat’s the difference between a connection and an export?
A native connection lets you take an action in another tool from Samelogic, such as creating a Jira issue. An export gives you a draft or snippet to use in your own tools. MCP gives a compatible coding assistant read-only access to authorized evidence. Each listing identifies the available workflow.
Do I need a Samelogic account?
You can try the Chrome extension before signing up. Connecting a project to Jira, Linear, Slack, or GitHub Actions requires a Samelogic account and the relevant permissions in the destination tool. AI connections require an account and a scoped token. Availability may vary by plan.
Who can see the context I share?
The recording keeps its own access controls. Text or screenshots you copy into a ticket or channel follow that destination’s permissions. Review the recording and the selected content before sharing; input values are masked by default, but other page content can still appear.
Will a generated test or an AI connection fix the bug?
They give your engineer a starting point. A Playwright export needs review, setup, assertions, and execution. An AI connection supplies recorded evidence; your engineer still reviews the proposed code change and checks that it resolves the issue.
Can I request a tool that isn’t supported yet?
Yes. Tell us what you want to connect and the task you need it to do. The proposed workflows in this directory help that conversation; they are not committed release plans.
THE HANDOFF STARTS HEREYour tools. Your team.
Your tools. Your team.
A clearer bug story.
Record the next browser bug. Give the person picking it up a place to begin.