Skip to main content

​
2026

​
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.