Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.samelogic.com/llms.txt

Use this file to discover all available pages before exploring further.

​
2026

​
April 26, 2026

This release upgrades the “Send to teammate” share path so a single action produces a ready-to-paste message that captures the replay context, the curated steps, and the link. What’s New
  • Formatted Teammate Share Message: The share menu’s “Send to teammate” action now generates a structured message that includes the replay title, start URL, duration, step count, access level (Team only vs. Anyone with the link), the curated written steps, and any expected/actual results captured during curation.
  • Mailto and Microsoft Teams Targets: The teammate share modal now produces a mailto: link with a populated subject and body, and a Microsoft Teams chat deep link that prefills the same message body, alongside the existing copy-to-clipboard option.
  • Inline Note Field: Senders can attach an optional note to the share message before sending. The note appears above the written steps so the recipient knows what to look at first.
Improvements
  • Trigger Steps Highlighted in the Message: When a step is marked as the likely trigger during curation, the share message tags it inline ([likely trigger]) so the recipient can jump to the suspected break point without opening the replay.
  • Step Truncation With Counter: The share message caps the visible step list (default 8 steps) and adds a ...N more steps in the replay line so the body stays scannable in chat clients.
Why This Matters
  • Sharing a replay over email or Teams no longer means writing a fresh summary by hand. The curated steps, access level, and expected/actual fields are formatted into the message body automatically, so the receiver gets the same context the curator just finished editing.

​
April 25, 2026

This release introduces a single canonical model for reproduction steps and gives users full curation control over how those steps read before sharing or exporting. What’s New
  • Canonical ReproStep Model: A shared model in packages/models now governs every generated and curated step across the extension preview, web replay detail, and exports. Each step carries a workflow kind (setup, navigate, interact, input, scroll, validate, error), a compact sentence for primary UI, and structured evidence (selectors, exact URLs, scroll anchors, viewport zone, screenshots, raw event ids) that stays out of the visible sentence but is preserved for JSON, Jira, Linear, Markdown, and Playwright exports.
  • Repro Step Curation: Users can now rename a step inline, hide it, merge it with the previous step, split it, mark it as the trigger (with an optional reason), and attach expected results or notes. Edits are stored as a curation overlay applied on top of regenerated defaults, so future regeneration never loses a manual fix.
  • Evidence Editor in the Hidden Events Tab: The replay event log now exposes an evidence editor for hidden steps so curators can adjust what a hidden step contributes to exports without un-hiding it. The hidden events tab label has been title-cased for consistency.
  • Setup Summary Chips With Icons: The setup section of the curated step list now renders chips with intent-specific icons (page, viewport, environment) so reviewers can scan the preconditions block at a glance.
  • Replay Share Access Chip: The replay preview now shows a chip indicating the link’s access level (Team only or Anyone with the link), hydrated from the synced replay record, so curators know what they are about to send before they send it.
Improvements
  • Curation Persists Across Local and Synced Replays: Curation state is saved to chrome.storage.local while the replay is local, then synced into the web app’s BugReplay.replaySummary.reproStepCuration field once the replay is uploaded. Web replay detail and downstream exports apply the same curation, so a step renamed in the extension reads identically in Linear or Jira.
  • Trigger Reason Cleared When Unmarked: Removing the trigger marker from a step now also clears any saved trigger reason at the model layer, preventing stale rationale from carrying forward.
  • Canonical Steps Power Sharing and Exports: The share menu, copy-to-clipboard, and Markdown/JSON/Playwright exports all consume the canonical step contract, so the prose teammates and agents see matches what the curator finalized.
  • Replay Navigation URLs Preserved: Web replay timeline now retains exact navigation URLs in evidence so the report can show the page label users recognize while keeping the full URL available for engineers.
  • Backfill Tolerance for Older Steps: Stored steps from earlier extension versions are normalized into the canonical model on read, with missing evidence, raw event ids, and trigger fields tolerated.
Why This Matters
  • Reproduction steps stop being a regenerated wall of text and become an editable artifact that stays consistent from extension preview through to Linear, Jira, and AI agent handoff. Curators can clean a replay once and trust every share surface uses the cleaned version.

​
April 24, 2026

This release reworks the launcher around saved captures, adds explicit access control to the copy-link share path, and tightens how the extension hydrates synced replays. What’s New
  • Promoted Saved Captures Launcher Item: The floating launcher now leads with a “Saved captures” entry that opens the activity sidebar directly, replacing the lower-emphasis link in the prior layout.
  • Copy Link Access Dialog: Copying a share link now opens an access dialog asking whether the link should be Team only or Anyone with the link. The selected access level is persisted on the replay and reflected in the new share access chip on the preview.
  • Replay Activity Sorting and Visibility Status: The web app’s replay APIs now accept activity sort parameters and return each replay’s visibility status, so saved sidebars and dashboards can order activity recency-first and show the link’s access level without a second round-trip.
  • Synced Replay Preview Hydration By Id: The extension can now reopen a synced replay’s preview directly from its replay id, so the preview pane after sync matches the canonical server record instead of the in-memory local copy.
Improvements
  • Launcher Widget Label Update: The launcher’s Create replay action is now labeled Reproduce user issues, framing the entry point around the workflow rather than the artifact.
  • Polished Launcher Menu Pills: Launcher menu pills have been tightened for consistent spacing, iconography, and hover treatment across actions.
  • Surfaced Local Replay Load Errors: When a local replay fails to load from storage, the extension now surfaces an inline error state instead of silently rendering an empty preview.
  • Background and Sidebar Sync Overhaul: The background service worker and saved elements sidebar now route replay save, sync, and reopen messages through a unified flow, reducing the chance that a freshly synced replay shows stale local-only metadata in the sidebar.
Why This Matters
  • Capture, sync, and share now share the same activity model, and copying a link is no longer ambiguous about who can open it. Teams using the extension on plans with both private and public sharing see the access decision before the link leaves the browser.

​
April 23, 2026

This release turns the step replay preview into a one-stop share surface. You can now hand a replay to a teammate, an AI agent, or an issue tracker directly from the preview, rename it inline, and skip the old “Name this replay” interstitial entirely. What’s New
  • Share Menu on the Replay Preview: A new Sync to cloud action and share menu live in the preview header. From a single click you can copy a share link, send the replay to a teammate, open it in Claude, create a Linear or Jira issue, or export the reproduction steps as Markdown, a Playwright test, or JSON.
  • Sync-and-Share From Local Replays: Share actions triggered on a locally saved replay now sync the recording to the cloud in the background while the preview stays on screen. Once sync finishes, the generated team link is handed off to whichever share target you picked.
  • Inline Title Editing: The recording title sits at the top of the preview header. Hovering reveals a “Click to edit title” hint; clicking puts the title into an inline edit mode. Enter saves, Escape cancels, and a toast confirms the update (same toast pattern used for the share actions).
  • Context-Aware Sign-In Prompts: When a share action needs authentication, the sign-in modal now explains why. Copying a share link, sending to a teammate, and the generic sync flow each get tailored title, body, and button copy so users know what happens after they sign in.
Improvements
  • Removed the “Name This Replay” Modal: The naming interstitial that used to appear between stopping a recording and viewing the preview is gone. Replays save immediately with a sensible default title; users rename inline from the preview instead.
  • Title-First Preview Header: The preview header now leads with the recording title on its own row, with the brand badge, an edit affordance, and the close button alongside it. Saved/Record/Sync-to-cloud controls and status chips move to a second row that wraps cleanly on narrow viewports.
  • Video-Camera Brand Icon: The purple brand badge in the preview header now uses a video-camera glyph (replacing the older checkmark), signalling “recording” rather than “task complete.”
  • Share Toast Redesign: The share-action confirmation toast has been restyled for higher contrast and clearer success/error tones, and is reused for title-save feedback.
  • Local Activity Sync for Share Auth: Auth state and synced-replay metadata (replay id, project id, URL, upload status) are now kept in sync across background and content scripts, so share actions don’t re-prompt for sign-in unnecessarily and always resolve to the freshest synced URL.
  • Saved Elements Sidebar & Launcher Widget Polish: Action rows in the saved elements sidebar and replay controls in the floating launcher have been tightened to match the new share surface.
  • Clearer Launcher Copy in the Popup: The extension popup now refers to the floating launcher as the Samelogic Launcher in its enable/disable toggle, labels, and error copy.
Why This Matters
  • Sharing a replay used to require stopping, naming, previewing, and then leaving the preview to copy a URL. This release collapses that into a single surface: stop → preview → share. Local-only replays participate in the share flow too, so teams capture on free plans and upgrade when they want to share — without re-recording.

​
April 20, 2026

This release tightens the step replay preview so reproduction steps read like a QA engineer wrote them, and gives the preview surface more room to show them. What’s New
  • QA / Literal Steps Toggle: The preview’s reproduction-steps panel now has a toggle between a plain-language QA narrative (default) and the raw event log. In narrative mode the triggering step is highlighted on error replays.
  • Detailed QA Step Narratives: Narrative steps now include the full URL on every navigation, the exact typed value on short text inputs, pixel dimensions on resizes, start→end page position on scrolls, and mouse coordinates for clicks that landed on unlabeled targets.
Improvements
  • Wider Preview Surface: The replay preview dock now occupies 90% of the viewport (up from ~67%) with a wider repro-steps column so long step descriptions read cleanly without aggressive wrapping.
  • Aspect-Ratio Preview Stage: The playback pane snaps to the recording’s original aspect ratio, removing the whitespace that previously appeared above and below the replay.
  • Internal Events Hidden: The extension’s own tracking events (samelogic-click-context and similar) no longer surface in the event log or reproduction steps.
Why This Matters
  • Engineers and QA can hand a replay to a teammate or AI agent and trust the steps read like a Linear-style repro, not a raw event dump. The wider preview makes steps and playback viewable side-by-side without scrolling.

​
April 18, 2026

This release overhauls the step replay save pipeline so stopping a recording feels instant, and keeps the host page smooth throughout a session — especially on long or interaction-heavy recordings. What’s New
  • Instant Stop-to-Save: Stopping a step replay no longer blocks on screenshot encoding, gzip compression, or service-worker merge work. The saved replay id is returned as soon as the payload is persisted locally, and the preview screenshot attaches as a follow-up write.
  • Background-Thread Encoding: Replay event payloads are now gzipped and base64-encoded off the recorded page’s main thread via a background service worker round-trip, with a same-thread fallback for environments where the service worker is unavailable.
  • Scoped Storage Reads: The recorder no longer fetches every key in chrome.storage.local on each stop. It now enumerates only the keys that belong to the active session, with a 48-hour cleanup pass on recording start so orphaned session data cannot accumulate. Improvements
  • Smoother Typing and Scrolling During Recording: input events are now throttled to a single trailing-edge capture per idle boundary, per target. Tabbing flushes the previous field’s capture. click, change, and submit remain immediate.
  • Fewer Layout Reads Per Interaction: captureElementContext now walks the ancestor chain once per interaction and shares the result with selector generation, actionable-ancestor detection, and accessible-name computation. Target text is read via textContent instead of innerText, eliminating forced layout on every click and keystroke.
  • Reused Element Snapshots Across Interactions: Repeated interactions with the same element reuse a cached snapshot (tag, role, accessible name, selector, ancestor) keyed by the recorder’s stable node id. The cache is invalidated automatically when the page changes that element.
  • Authoritative Live Event Buffer at Stop: When the background service worker’s in-memory event buffer is non-empty at stop time, the extension skips the storage re-merge, deduplicate, and re-sort pass. Storage-backed recovery is preserved for cold-start and eviction cases.
  • Native Base64 Where Available: Per-chunk encoding uses the browser’s native Uint8Array.prototype.toBase64() and fromBase64() when present, with a feature-detected fallback to the previous btoa/atob path.
What Changed
  • Async Encode by Default: The payload encoder is now promise-returning. A synchronous variant is retained exclusively for beforeunload / visibilitychange paths, where async work cannot complete.
  • Leaner Repro-Step Payload: The unused domPath field has been removed from the click-context event and the web-app schema. cssSelector is retained where enrichment and intent collapse consume it.
  • New Save-Path Instrumentation: [BugReplay:content:persist] and [BugReplay:stop-merge] now log chunk counts, payload sizes, and encode/merge durations so chunk sizing can be tuned empirically.
Why This Matters
  • Teams recording long or form-heavy sessions see less jank during capture and a near-instant stop click. Session storage no longer grows across recordings, and the save path has clear telemetry so future tuning is data-driven rather than guessed.

​
April 17, 2026

This release fixes a class of repro-step mislabeling bugs (for example, “clicked Images” rendering as “clicked Maps” after a Google Search navigation) by capturing element context at click time instead of reconstructing it from the post-mutation DOM. What’s New
  • Click-Time Captured Context Stream: The extension now records a lightweight element snapshot alongside the replay for every meaningful interaction (click, auxclick, mousedown, input, change, submit), capturing the element’s tag, role, accessible name, visible text, attributes, actionable ancestor, bounding rect, and CSS selector in the moment.
  • Captured Context as Source of Truth: Enrichment, intent collapse, step narrative, and the repro report now pair each playback annotation to its captured snapshot by interaction id (or timestamp window fallback) and use that snapshot to label steps, instead of walking the DOM after navigations or mutations have changed what the element looks like.
Improvements
  • Sharper Step Narratives: Step generation has been overhauled to group and label interactions using captured context, produce clearer trigger actions, and reduce ambiguity when repeated structures (list rows, icon buttons, nav items) appear across the page.
  • Tighter Intent Collapse: Micro-interaction collapse now uses the captured ancestor and accessible-name data to merge related events into a single step more reliably, so rapid typing, hover-then-click sequences, and multi-step form fills read more naturally.
  • Richer Replay Summary and Repro Report: Replay summaries and the generated repro report now pull preconditions, element labels, and error context from the captured snapshots, so exported Jira and Linear drafts carry the label the user actually saw when they clicked.
  • Step Replay Details Page Polish: The replay details page has been refreshed to surface captured context alongside the timeline for faster scanning during review.
Why This Matters
  • QA, support, and conversion rate optimization teams can trust that repro-step labels reflect what the user actually interacted with, not what the page became after the click. This is especially important for search, navigation, and single-page-app flows where the DOM changes the moment an interaction completes.

​
April 16, 2026

This release eliminates a main-thread performance bottleneck in the extension’s step replay recorder, making recordings on the host page noticeably smoother. Fixes
  • Recorder Main-Thread Jank: The extension’s step replay recorder no longer re-compresses the same replay events up to 22 times per flush on the recorded page’s main thread. Recordings on complex pages are smoother and the underlying event stream is no longer delayed by the buffering pipeline.
What Changed
  • O(N) Event Chunk Splitter: The sub-chunk splitter that keeps runtime messages under Chrome’s payload cap now sizes chunks using a single JSON.stringify length per event instead of synchronously gzipping the growing candidate array once per event. This removes an O(N²) synchronous gzip loop from the hot recording path.
  • Single-Encode Flush Pipeline: Each sub-chunk is now gzipped+base64-encoded exactly once and the same payload is reused for both chrome.storage.local persistence and the background service worker hand-off, cutting two redundant encodes per sub-chunk.
  • Safety Fallback Preserved: If a pathological single event would still exceed the per-message cap after encoding, the flush loop now requeues the sub-chunk as individual events so persistence and delivery still succeed.
Why This Matters
  • Step replay’s job is to capture the user’s page faithfully. Removing synchronous compression work from the recorded page’s main thread means less jank during recording, fewer dropped frames in the resulting replay, and a calmer experience on low-powered machines — especially on content-heavy pages where the recorder produces larger event batches.

​
April 15, 2026

This release redesigns step replay cards, adds preview screenshots to replays, enforces plan-aware recording duration limits in the extension, and introduces a recording countdown overlay so teams start capture more deliberately. What’s New
  • Recording Countdown Overlay: Starting a step replay now shows a full-page translucent 3-2-1 countdown before recording begins, giving you a clear moment to prepare before capture starts. The countdown is skipped when resuming a paused recording.
  • Replay Preview Screenshots: Step replays now capture a preview screenshot at the end of recording. The screenshot is uploaded alongside the replay so cards and lists can show a visual thumbnail without loading the full replay.
  • Redesigned Step Replay Cards: Replay cards across the web app have been redesigned with preview thumbnails, cleaner metadata layout, and more consistent visual treatment for faster scanning.
  • Extension Duration Enforcement: The extension now enforces plan-aware recording duration limits (30s Free, 2m Starter, 5m Pro, 10m Enterprise) with a live countdown timer, color-coded warnings as time runs low, and an inline upgrade prompt when the limit is reached.
Improvements
  • Duration Countdown Warnings: The recording overlay now shifts from normal to warning to critical visual states as remaining time decreases, so you always know how much recording time is left.
  • Smoother Recording Lifecycle: Duration state resets cleanly between recordings and after local saves, preventing stale limit copy from carrying over into new sessions.
Why This Matters
  • Teams can find and identify replays faster with preview thumbnails, start recordings more deliberately with the countdown, and record with clear plan-aware guardrails instead of unexplained cutoffs.

​
April 10, 2026

This release fixes a critical bug where step replay recordings spanning multiple pages only captured the last page visited, losing all earlier pages from the replay. Fixes
  • Multi-Page Replay Event Preservation: Replay recordings that span full-page navigations (e.g. Google Search to Google Images) now correctly retain events from all pages, not just the last one. Previously, sub-frame content scripts unloading during navigation would send a stale cancel signal that wiped the main frame’s persisted events from storage before the new page could resume recording.
What Changed
  • Sub-Frame Cancel Guard (Content Script): The extension’s page-unload cleanup now only sends a session cancel from the top-level frame. Iframe content scripts, which never own the recording session, no longer trigger event wipes during navigation.
  • Sub-Frame Cancel Guard (Background): The background service worker now rejects cancel requests originating from sub-frames as a defense-in-depth measure, ensuring that even if a sub-frame message reaches the background, it cannot clear persisted recording data.
Why This Matters
  • Teams recording multi-step workflows that cross page boundaries will now see the complete recording in the replay preview, not just the final page. This was the most common cause of “missing pages” in step replay.

​
April 9, 2026

This release fixes a core extension session gap so the popup, project lookup, screenshot upload, and share flows stay aligned with the Samelogic session already open in your browser. What’s New
  • Extension-Compatible Web Session Recovery: Extension API calls can now recover the active Samelogic session even when the request originates from the extension runtime instead of a normal web page request.
  • Multi-Domain Sign-In Detection: The extension now checks Samelogic auth cookies across supported Samelogic domains, which reduces false signed-out states when you are already logged in on the web.
Improvements
  • Fewer False Not signed in States: Project, member, share, and screenshot-related extension flows now stay authenticated more reliably instead of asking users to sign in again unnecessarily.
  • Cleaner Replay Target Control: The internal replay target card in the popup is now smaller and less wordy, making it easier to scan during capture work.
Why This Matters
  • Teams can move from capture to sync or share with less session friction, especially when they are already signed in to Samelogic in another browser tab.

​
April 8, 2026

This release hardens the Chrome extension runtime so replay recording, saved-capture review, and page-side capture controls recover more reliably on real-world apps with navigation changes, nested frames, and longer sessions. What’s New
  • Stronger Local Replay Recovery: Local step replays and replay previews now load more directly from extension storage, which makes interrupted or reopened sessions easier to recover.
  • Safer Replay Continuity Across Navigation: Replay state now flushes before navigation and resumes more safely after page transitions, reducing the chance of losing the session mid-recording.
  • More Stable Page Runtime Controllers: Launcher behavior, element capture, sidebar interactions, element detail windows, and background sync flows now run through dedicated controllers and managers for steadier behavior.
Improvements
  • Better Multi-Frame and Multi-Context Handling: Replay and selection flows now route content and frame messages more cleanly across changing page contexts.
  • Lower Regression Risk in Core Extension Flows: Replay, selection, sidebar, launcher, and element-window behavior now have much broader automated test coverage.
Why This Matters
  • Teams are less likely to lose evidence or hit dead-end extension states while recording, tagging, reopening, or syncing captures on complex pages.

​
April 3, 2026

This release expands the step replay foundation so recordings can scale better, support longer plan-aware durations, and prepare larger replays for faster, preview-first playback. What’s New
  • Plan-Aware Replay Duration Tiers: Step replay duration limits now expand by plan tier, from 30 seconds on Free to 2 minutes on Starter, 5 minutes on Pro, and 10 minutes on Enterprise.
  • Replay Blob Storage Foundation: Full replay payloads can now be stored with dedicated manifest metadata, checksums, and external blob-storage support instead of relying only on the primary database row.
  • Replay Summary Metadata on Ingest: Replay ingest now generates structured summary data and preview coverage metadata so replay pages can load with more context before the full payload is hydrated.
Improvements
  • Preview-First Replay Loading Path: Replay reads and the player now support a lighter metadata-first path ahead of full replay hydration, which is especially important for larger recordings.
  • Stronger Replay Storage and Read Fallbacks: Replay APIs now track payload size, duration, coverage, and storage presence more explicitly, improving recovery and fallback behavior as replay storage rolls out.
  • More Reliable Replay Event Preservation: Extension replay recording now handles multi-page and multi-context event aggregation more reliably, reducing gaps when sessions span navigation or multiple page contexts.
Rollout Notes
  • External replay blob reads and writes, preview-first playback, and expanded duration tiers are controlled by rollout flags while they are staged through production.
Why This Matters
  • Teams can capture longer or richer replays more safely, and Samelogic now has a stronger foundation for loading larger recordings without making the replay experience feel heavier.

​
March 22, 2026

This release overhauls replay-to-reporting so teams can turn a step replay into a cleaner, more complete bug report with less manual rewriting. What’s New
  • Structured Repro Reports: Step replays now generate a richer report with preconditions, narrative steps, expected vs. actual behavior, captured errors, and environment details such as browser, OS, viewport, and start URL.
  • Smarter Step Narratives Across Web and Extension: Replay steps now use more of the recorded context to identify what the user was trying to do, group repeated micro-actions into clearer steps, and call out trigger actions more clearly in both the web app and the extension repro modal.
  • Better Jira and Linear Drafts: Export drafts now carry forward cleaner reproduction steps, preconditions, and error context instead of relying on a flatter raw event list.
Improvements
  • Replay-Time Linking in Repro Steps: Generated steps now link back to their replay timestamps, which makes it easier to jump from a written step to the exact point in the recording.
  • Clearer Error Summaries: Error output now includes surrounding action context so teams can see what interaction preceded a failure without re-reading the full timeline.
  • Consistent UTC Replay Timestamps: Replay and CI views now format replay dates in UTC, reducing confusion when teams share recordings across time zones.
Why This Matters
  • Teams can move from replay evidence to Jira, Linear, or internal handoff faster, with less cleanup and fewer gaps in the report engineers receive.

​
March 21, 2026

This release hardens replay recording on high-churn pages so long or complex sessions are less likely to stall, bloat, or save unusable data. What’s New
  • Mutation Surge Guardrails: Step replay recording now detects pages changing too aggressively in the background and stops with a clearer limit state instead of continuing to capture a broken or misleading session.
  • Non-Blocking Replay Payload Encoding: Replay event payloads are now compressed asynchronously, which reduces the chance that recording or saving will freeze the page on larger sessions.
Improvements
  • More Stable Replay Recording and Playback: The recorder and preview now handle larger and more complex sessions more reliably, which reduces breakage when pages are especially dynamic.
  • Leaner Replay Sampling: Replay capture now samples scroll and input changes more selectively, helping keep recordings smaller and more reliable on modern client-rendered pages.
Why This Matters
  • Teams can keep using step replay on heavier apps without losing the session to runaway DOM churn or a sluggish save flow.

​
March 19, 2026

This release completes the annotated screenshot evidence flow and improves how the extension stays aligned with the active browser tab during live debugging. What’s New
  • Annotated Screenshot Uploads: Full-page screenshot evidence can now be uploaded through the extension with a tracked highlight overlay that stays attached to the selected element through scroll and layout shifts.
  • DevTools-Aware Launcher Behavior: The floating launcher now stays open and prewarmed when DevTools is active for a tab, so capture actions remain easier to reach during active inspection.
  • Tab-Level DevTools Session Tracking: DevTools connections are now tracked per tab, which keeps launcher state from drifting when panels open, close, or switch targets.
Improvements
  • More Reliable Screenshot Saves: The element save API now accepts larger payloads, reducing failures when teams attach richer screenshot evidence.
  • Cleaner Evidence Capture During Motion: Screenshot annotation rendering now syncs continuously during the capture window, so highlighted evidence lines up more accurately with the selected element.
Why This Matters
  • QA, support, and conversion rate optimization teams can attach clearer visual proof to a capture and avoid losing extension context while working side-by-side with DevTools.

​
March 18, 2026

This release improves replay sync accuracy and tightens the extension’s production release path so saved sessions are easier to trust from capture through upload. What’s New
  • Project-Accurate Replay Sync: Elements tagged during a local replay now sync into the replay’s destination project instead of ending up tied to the wrong project.
  • Stronger Replay Session Recovery: Replay save and upload flows now recover session details more reliably, which improves local replay continuity after recording stops.
  • Production Release Hardening for Extension 1.7.8: The extension package now ships with tighter production permissions and built-in validation checks before release packaging.
Improvements
  • More Reliable Replay Highlights: Tagged elements reopened from a replay now use cleaner saved context so highlights resolve more reliably in the web player.
  • Safer Release Packaging: Release tooling now checks version sync, icon coverage, and disallowed development origins before a package is considered valid.
Why This Matters
  • Teams spend less time fixing replay and project mismatches, and shipped extension builds are less likely to carry environment drift into production.

​
March 17, 2026

This release brings conversion rate optimization triage directly into capture and review workflows so the issue, urgency, and experiment state stay attached to evidence from the moment it is saved. What’s New
  • Capture-Time Conversion Rate Optimization Triage: The extension save flow now asks for the issue tag up front and adds quicker revenue-blocker selection plus optional impact and experiment-status fields before saving.
  • Replay Tagging Keeps Triage Metadata: Elements tagged during a replay now preserve conversion rate optimization urgency and experiment metadata as draft state, so that context survives local replay flows and sync.
  • Triage Visibility Across Review Surfaces: Element cards, element details, replay review, and saved activity now surface conversion rate optimization issue, impact, and experiment context more consistently.
Improvements
  • Shared Triage Metadata Across Web and Extension: Impact and experiment definitions are now centralized, which keeps labels, badges, and serialization consistent across product surfaces.
  • Higher Visibility for Revenue Blockers: Saved activity and review UI now make business-critical captures easier to spot during triage.
Why This Matters
  • Teams can prioritize the captures that matter most to revenue earlier, and they no longer lose business context between tagging an issue and reviewing it later.

​
March 16, 2026

This release introduces a lighter, faster floating launcher in the extension so teams can capture elements, record reproduction steps, and reopen saved evidence directly from the page. What’s New
  • Floating Page Launcher: Supported pages now show a compact on-page launcher with direct actions for Select Element, Record Steps, View Saved Captures, widget visibility, and settings.
  • Launcher Settings and Popup Controls: Teams can now hide or re-enable the widget from the page or the extension popup, and control whether hover tooltips appear from the launcher settings modal.
  • Saved Captures Shortcut: The launcher now links directly into the saved captures sidebar so recent evidence is reachable from the page without opening a separate extension flow first.
Improvements
  • Faster Select Element Activation: Element selection now starts immediately in the current frame, prewarms its UI before first use, activates on pointer down, and fans out to frames in parallel so the capture flow feels more instant.
  • Lighter Launcher Modal Performance: The widget settings modal now uses a less expensive rendering path with simpler overlay treatment, reduced animation cost, and smoother toggle behavior.
  • Cleaner Launcher Guidance: Action tooltips are now shorter, more task-focused, and can be turned off entirely, which keeps the launcher easier to scan during active review work.
Why This Matters
  • Conversion rate optimization teams can move from spotting friction to tagging the exact button, form, or message responsible, without breaking concentration or digging through the popup.
  • QA teams can record steps to reproduce, reopen saved captures, and isolate the exact UI under test faster, reducing ambiguity in bug handoff.
  • Both CRO and QA workflows benefit from page-level controls that keep evidence capture close to the live experience, which speeds up review, triage, and collaboration.

​
March 15, 2026

This release tightens the extension’s capture-to-replay workflow so teams can tag, save, review, and sync evidence with less friction. What’s New
  • Capture Settings Before Save: Saving an element now opens a focused capture settings step where you choose the issue tag first and decide whether to attach no screenshot, a cropped element screenshot, or an annotated full-page screenshot.
  • Replay Title Review Before Preview: Local step replays now prompt for a title before opening the preview, so recordings are easier to identify when you reopen or sync them later.
  • Replay Tagging Carries Forward to Sync: Elements tagged during a recording now stay attached to the replay and sync with it when it is uploaded.
Improvements
  • Smoother Replay Preview Performance: Replay preview rendering and the event log now load in scheduled chunks, which makes larger recordings feel more stable and easier to scrub.
  • Clearer Popup Recovery and Restricted-Tab Handling: The extension now checks that its page helper is ready, retries injection when needed, and shows clearer messages on pages where Chrome does not allow the extension to run.
Why This Matters
  • Teams can capture higher-signal evidence with less cleanup, name recordings before they get buried, and avoid dead-end extension states during active debugging.

​
March 7, 2026

This release separates workspace team management from project sharing so access is easier to understand, safer to change, and faster to audit. What’s New
  • Dedicated Workspace Team Surface: Each workspace now has its own team page for members, guests, pending invites, and recent audit activity.
  • Project Access Settings: Projects now have a dedicated access page for explicit collaborators, editor/viewer roles, inherited workspace access, and project visibility.
  • Clearer Invite Scope: Workspace invites and project-only invites now explain exactly what the recipient will gain before they accept.
Improvements
  • Workspace vs. Project Access Is No Longer Blended Together: Full workspace members, guests, and project-only collaborators are shown separately so it is clear who can discover a project and why.
  • Permission Rules Match the UI More Closely: Editor access is now required for save flows, reducing confusion around who can make changes from the extension or web app.
Why This Matters
  • Owners and admins can manage team access with less guesswork, and collaborators get fewer surprises when joining projects versus whole workspaces.

​
March 6, 2026

This release makes the Projects home workspace-first, giving teams a clearer place to create projects, track capacity, and move between workspaces. What’s New
  • Workspace-Aware Projects Home: The projects page now centers around the active workspace, with a switcher that keeps workspace projects separate from project-only shares.
  • Create Projects in the Right Workspace: New projects are created directly inside the selected workspace instead of relying on a legacy default flow.
  • In-Context Project Capacity Guidance: Project counts, remaining workspace capacity, and upgrade prompts now appear where teams manage projects.
Improvements
  • Better Active Workspace Memory: Samelogic now preserves the last active workspace context as you switch projects and return to the dashboard.
  • Safer Migration Visibility: Shared and migrating projects stay visible during workspace migration so teams do not lose track of active work.
Why This Matters
  • Teams can understand where a project belongs, how much room is left in a workspace, and what will happen when they invite or share before they run into limits.

​
March 5, 2026

Billing is now unified at the workspace level, giving teams a single, consistent place to manage their plan, seats, and usage. What’s New
  • Workspace-Scoped Billing: Your subscription, usage, and plan limits are now tied to your workspace rather than individual projects. All billing flows — checkout, invoices, and plan management — reflect workspace-level state.
  • Clearer Plan Limits: Project limits are now enforced per workspace based on your plan tier, with clear guidance when you approach or exceed your plan’s limits.
  • Workspace Role Controls: Billing management is now permission-controlled by workspace role, with safeguards to prevent accidental ownership transfers or loss of account access.

​
March 4, 2026

This release migrates element and replay tagging from the legacy QA status model to a conversion rate optimization-first taxonomy across web, API, database, and extension workflows. What’s New
  • Conversion Rate Optimization Issue Taxonomy Across Product Surfaces: Element Library, replay triage, timeline pills, and extension capture now use the ten-tag conversion rate optimization issue model (BROKEN_EXPERIENCE through NO_ISSUE).
  • Optional Conversion Rate Optimization Triage Dimensions: Teams can now store impact (REVENUE_BLOCKER, HIGH, MEDIUM, LOW) and experiment status (HYPOTHESIS, READY_TO_TEST, IN_TEST, WINNER, NO_LIFT) for each captured element.
  • Replay Tagging Upgrade: Replay tag parsing/formatting now supports conversion rate optimization labels and updated bracket-tag syntax while preserving legacy comment readability.
Compatibility Guarantees
  • Dual-write during rollout: Conversion rate optimization updates mirror legacy elementState to keep mixed client versions operational.
  • Read fallback order: APIs and UIs resolve taxonomy as croIssueTag first, then legacy elementState.
  • Backfill support: Existing records are mapped forward with automatic high-confidence conversions plus manual-review reporting for ambiguous cases.
Operational Notes
  • Existing elements are automatically mapped to the new taxonomy. Ambiguous cases are flagged for manual review.
  • The new taxonomy is rolling out gradually across web and extension clients.

​
March 3, 2026

This release brings reproduction-step generation directly into the extension replay preview, so teams can move from captured evidence to shareable bug reports faster. What’s New
  • Generate Repro Steps in Extension Replay Preview: You can now generate reproduction steps directly from a saved local replay in the extension, without switching to the web app first.
  • One-Click Export Path to Jira and Linear: The extension now includes direct export actions for Jira and Linear from the repro-steps modal, with a sync-first flow that saves the replay and opens the replay page ready for handoff.
  • Authentication-Aware Export Flow: Signed-out users now stay in the same guided advisory flow when trying to export, so they can sign in or create an account without losing context.
Improvements
  • Richer Repro Step Coverage: Generated repro steps now include the full meaningful action trail (not just a narrow subset), aligning extension and web replay behavior more closely with the timeline event stream.
  • Higher Signal in Generated Steps: Low-value UI changed entries are removed from repro output so exported steps stay clearer and more actionable.
  • Polished Replay Action UX: Repro actions are positioned more naturally in the overlay action row, export buttons now include Jira/Linear icons, and modal close controls are visually consistent with the rest of the extension.
Why This Matters
  • QA and Support teams can produce clearer, issue-ready reproduction steps with less manual rewriting.
  • Engineers get more complete, higher-signal bug context from replay handoffs, which reduces triage back-and-forth.
  • Conversion rate optimization specialists and agencies can turn replay evidence into Jira/Linear-ready implementation steps faster, reducing experiment setup time and client-developer handoff friction.
  • Product and Customer-facing teams can share reproducible evidence faster when coordinating fixes across functions.

​
February 26, 2026

This release hardens nested iframe selection and re-open behavior so teams can trust that the exact element they saved is the one they see again, inspect again, and share again. What’s New
  • Root-Level Details Window for Iframe Captures: The element details window now renders in the main/root page UI layer even when the selected element lives inside a child or deeply nested iframe. This keeps review controls in a consistent, predictable location.
  • Frame-Accurate Element Resolution: Re-open and highlight flows now honor the captured frame context first, so repeated structures across root and child documents (like multiple h1 tags) no longer resolve to the wrong page-level element.
  • Single Active Highlight State: Selecting one saved element after another now clears prior highlight artifacts before rendering the next target, preventing stacked multi-element highlights across nested frame boundaries.
  • Reliable Found/Not-Found Feedback: The “Element not found on this page” notice now only appears after frame-aware resolution is fully exhausted. Successful iframe matches no longer produce false negative messaging.
Improvements
  • Consistent Behavior Across Entry Points: The same frame-safe logic is now applied whether the element is selected live, reopened from saved elements, or launched from the element library view.
  • Cleaner Reproduction Workflow: Overlay state and element targeting now stay synchronized during rapid back-to-back inspections, reducing manual re-selection loops.
Why This Matters
  • Teams no longer lose time on the core “which element?” ambiguity when reporting or validating issues in embedded/iframe-heavy interfaces.
  • Bug and QA handoffs stay technically precise, reducing bounce-backs caused by incorrect element targeting or conflicting highlights.
  • Reproduction stays trustworthy for multi-surface products where critical UI lives inside nested embeds, widgets, or hosted app shells.

​
February 25, 2026

This release overhauls the replay rendering pipeline and introduces a unified activity model in the extension sidebar, making local captures and replays durable, syncable, and visible in a single feed. What’s New
  • Frame-Accurate Replay Rendering: The replay progress engine has been rewritten from setInterval polling to a requestAnimationFrame loop. Playhead position is now computed from elapsed high-resolution timestamps and applied via CSS transforms rather than layout-triggering style mutations. The result is visually smoother playback at the monitor’s native refresh rate with zero dropped frames during concurrent DOM observation.
  • Unified Saved Activity Feed: The extension sidebar now presents saved elements and local replays in a single recency-sorted stream. Each item carries its sync state (local-only, syncing, synced) and exposes per-item and bulk sync actions. The feed is backed by a merged query across chrome.storage.local captures and the workspace API, deduplicated by element fingerprint and replay session ID.
  • Local Replay Durability: Local replay recordings are now persisted with a 24-hour TTL and survive full page unloads. A beforeunload handler flushes any in-progress recording buffer to chrome.storage.local so that partially completed replays can be reviewed and synced from the sidebar after navigating away or closing the tab.
  • Sign-in-Aware Feed Gating: The activity feed renders a preview of the three most recent items for signed-out users, with deeper history gated behind authentication. Signing in triggers an automatic merge of any local-only items into the workspace without requiring manual sync.
Improvements
  • Replay Timeline Iconography: Event markers on the replay timeline now use distinct icons for click, hover, scroll, and keyboard events instead of generic dots, making it easier to scan a recording’s interaction pattern at a glance.
  • “Sync” Mental Model: All user-facing copy across the overlay, popup, and auth modal has been reframed from “save” to “sync” to accurately reflect that local recordings already exist and need to be uploaded — not created — on the server.
  • Overlay Control Refinement: The local-mode replay overlay now surfaces sync, discard, and re-record actions in a persistent control bar rather than requiring the user to open the sidebar, reducing the number of clicks to resolve a local recording.

​
February 23, 2026

This release significantly expands the reliability of our TruthBundle element re-identification engine, addressing six distinct failure categories that previously caused elements to be unfindable after saving. What’s New
  • Virtual Scroll Positioning: The extension now captures the scroll state of every scrollable ancestor at save time (scrollContext). At re-find time, that position is programmatically restored and a MutationObserver waits for virtual list renderers (React, Vue) to materialize new DOM nodes before querying. Elements saved deep inside Twitter timelines, Notion databases, or GitHub file lists are now reliably located.
  • Nested Scroll Container Awareness: scrollToElementIntelligently now detects the nearest overflow: scroll | auto ancestor and scrolls it directly — rather than window.scrollTo — before attempting to highlight an element. Elements clipped inside panels, sidebars, and drawers are now properly brought into view.
  • Extended Sibling Context Matching: We now capture four surrounding sibling nodes (prev+next at the element and parent level) into a extendedSiblingContext field on the TruthBundle. Each matching sibling context yields a scoring boost in scoreTruthBundleCandidate, providing a reliable tiebreaker for elements like “Edit” or “Delete” that appear repeatedly across list rows.
  • CDN Image Resilience: For images served from CDN origins (Google, GitHub, Cloudfront, Cloudinary, etc.), we now store a durable three-part fingerprint: hostname, path pattern with token segments normalized to *, and pixel dimensions (naturalWidth/naturalHeight). At re-find time, exact URL matching is replaced with this structured partial match, meaning rotating session tokens no longer break identity.
  • CSS-in-JS Hash Class Stripping: A stripHashClasses utility strips build-time generated class name segments (css-abc123, jsx-1234567890, _button_h3kd2_1) from both stored and live class lists. A second candidate collection pass using semantic-only class fragments ensures elements on Next.js, Emotion, and Stitches codebases survive framework rebuilds.
  • Hover-Only Element Reveal: At save time, document.querySelectorAll(':hover') captures the full CSS hover chain. At re-find time, if no ARIA-based trigger is found, the engine dispatches mousemove → mouseenter → mouseover on the stored hover ancestors before retrying element discovery. This makes elements that are only revealed via CSS :hover (not aria-expanded) reliably findable.
Improvements
  • Fixed/Sticky Header Targeting: Elements in position: fixed or position: sticky containers (e.g. navigation bars, persistent toolbars) now bypass the scroll loop entirely instead of being treated as off-screen elements. The reveal pipeline also explicitly guards against triggering dropdown reveal logic for header-resident elements — previously, the presence of aria-expanded elements anywhere on the page (like a Google search bar) was sufficient to incorrectly enter the reveal path for any short-text element.
  • Capture-time position in Parent Chain: Each ancestor in structure.parentChain now stores its computed CSS position property. This makes fixed/sticky container detection at re-find time data-driven and instantaneous, without requiring live DOM traversal.
  • Viewport Presence Bonus: scoreTruthBundleCandidate now awards a +0.15 scoring boost to elements that are currently visible in the viewport and inside a fixed/sticky container. This differentiates the correct header-resident target from off-screen false-positives that match on other dimensions.

​
February 22, 2026

This release fundamentally overhauls our element finding architecture. We have deprecated brittle, single-dimensional CSS/XPath selection in favor of a mathematically rigorous Element Validation Engine powered by the TruthBundle. What’s New
  • TruthBundle Validation Engine: Instead of blindly trusting selectors, we now deeply validate candidates across multiple contextual dimensions. The engine parses the historical truthBundle, analyzing the element’s semantics, dataset, text content, and accessibility roles (aria-label, alt, role mapping) to guarantee we locate the correct target regardless of layout shifts.
  • Intelligent Spatial Reveal Strategies: Finding hidden elements (dropdowns, menus, accordions) is now mathematically driven. Our findRevealTrigger algorithm maps Euclidean center-to-center distances between the target and potential triggers across the DOM viewport, combined with WAI-ARIA relationship mappings (aria-controls, aria-owns, aria-expanded), to automatically deduce how to expose an element before interacting with it.
  • Structural and Hierarchical Integrity Check: The engine recursively validates the DOM tree against the truthBundle.structure.parentChain. An identical element injected into the wrong parent container is correctly rejected on structural grounds.
Improvements
  • Heuristic Scoring Model: When exact DOM paths fracture on dynamic or hydrated pages, the engine utilizes a fallback scoring heuristic. Candidates are assigned probability scores based on robust metadata (e.g., matching data-testid, exact text length alignment, and parent structure proximity) to locate the best viable target.
  • Strict Misidentification Rejection: Implemented isTruthBundleHardMismatch logic to aggressively filter out geometric false-positives. If intrinsic properties (like a specific id or a contradictory tagName) violate the historical truthBundle constraints, the candidate is discarded instantly, protecting execution integrity.

​
February 21, 2026

This release focuses on delivering seamless extension workflows for unregistered users and enhancing GitHub CI integration with improved authentication and workflow options. What’s New
  • The Magical Save Experience: Logged-out users can now safely capture elements inside the Chrome extension. We securely store an array of your captures locally until you’re ready to create an account.
  • Sync Local Elements to Workspace: When you log in with localized elements, a new “Sync Local” action allows you to cleanly upload them all sequentially right from your extension sidebar.
  • Improved GitHub App Integration: Our CI workspace feature now natively supports GitHub App token callback handling, streamlining CI pipeline validation and metadata management without brittle keys.
Improvements
  • Multiple Local Saves Persistence: Our local payload architecture has been overhauled to preserve all independent unauthenticated captures in storage rather than overwriting past captures.
  • Element Library Slider Polish: The “Element Library” UI redirect has been improved. Navigating to the library triggers our seamless slider functionality instead of redirecting users abruptly to the web dashboard.
  • CI Artifact Bundling: Enhanced artifact workflows to include optional run token authentication strategies.
Fixes
  • Discarded login redirection jarring sequences for unauthenticated users directly clicking “Save Element”.
  • Corrected sidebar failure states caused by trying to display API elements when unauthorized.

​
February 18, 2026

This sprint introduces the first end-to-end version of one-click replay validation in CI, centered on a GitHub Actions workflow for QA and release teams. What’s New
  • Step Replay CI Workspace: Each replay now has a dedicated CI workspace with Run in CI, profile selection (smoke, regression, auth), artifact-bundle download, and run history.
  • Project-level GitHub CI settings: Teams can configure repository/workflow mapping, default run profile, allowed branches, and protected-branch approval behavior from project settings.
  • GitHub Actions orchestration flow: Replay runs can dispatch a GitHub workflow, stream lifecycle callbacks, and keep replay status synchronized from queued through completion.
  • CI-ready replay artifact bundle: Replays can now be exported as a bundle containing Playwright spec scaffold, replay metadata, logs, screenshots, and a PR comment draft.
Improvements
  • Deterministic PR targeting with fallback: Run dispatch supports PR/branch targeting with candidate selection when mapping is ambiguous.
  • Run governance and auditability: New CI run statuses, policy-block handling, idempotency support, and run-event tracking improve reliability and traceability.
  • PR-visible validation context: Completed runs can publish GitHub commit status/check context and PR comment updates with links back to replay evidence.
Fixes
  • Improved callback security with signature validation and timing-safe token comparisons.
  • Improved CI status normalization and failure classification for clearer run outcomes.

​
February 10, 2026

This release introduces Timeline as the project home so teams can immediately see what was captured, replayed, and discussed. What’s New
  • Timeline is now the default project landing page: Login, signup, and onboarding now route users into their project timeline instead of the previous home flow.
  • New project activity feed: Timeline surfaces element saves, step replay recordings, and comments in one stream with date grouping.
  • Replay journey map previews: Timeline replay cards now include a compact journey rail with key actions and event markers for faster scanability.
  • Quick comments from timeline cards: Teams can post comments directly on element and replay activity without leaving the feed.
Improvements
  • Timeline navigation expanded: Timeline is now linked from the Element Library sidebar and the account dropdown for faster access.
  • Pagination and filtering improvements: Timeline and step replay APIs now support stronger page/limit handling and optional total-count behavior for better loading at scale.
  • Faster timeline queries: Timeline comment summaries and feed queries were optimized with raw SQL aggregation and new composite DB indexes.
Fixes
  • Improved redirect reliability to ensure authenticated users consistently land on their default project timeline.
  • Improved replay and activity data loading consistency across larger projects.

​
February 3, 2026

This update focuses on making saved elements easier to find again, improving highlight reliability, and polishing the element library experience. What’s New
  • More reliable element highlighting: Saved elements now re-open more consistently across dynamic pages, including dropdowns and menus.
  • Cleaner highlight experience: The dark “spotlight” dimming effect has been removed while keeping the highlight ring and callouts.
  • Element context view: You can now view more of the captured element context in the element details area to help with validation and troubleshooting.
Improvements
  • Smarter re-find behavior: If a page has changed, the system uses the most dependable signals to find the right element instead of grabbing the first similar one.
  • Fallback guidance: When an exact match isn’t possible, the closest relevant container can be highlighted with a clear notice.
  • Plan limit display accuracy: Free plan element limits now display correctly in the library.
Fixes
  • Improved highlight launch stability from both the element card and the element detail view.
  • Reduced false matches for menu items with similar structure.