Back to Home
RecBug Documentation & Multi-Destination Hub

Supported Destinations & Setup Guide

Step-by-step guides for installing RecBug and configuring all supported issue trackers, team chat webhooks, and offline diagnostic exports.

1. Installing the RecBug Chrome Extension

Official Chrome Web Store Release

Get RecBug directly from the Chrome Web Store

Install the verified extension in one click to get automatic updates, strictly bug-focused telemetry recording, and instant bug synchronization.

Quick Installation Steps:

1
Open Chrome Web Store

Click the Add to Chrome button above or anywhere across the site to open the official listing.

2
Confirm Installation

Click Add to Chrome on the store page and accept the standard browser prompt.

3
Pin & Start Recording

Click the puzzle piece icon in Chrome's toolbar and pin RecBug for instant access.

Compatible with:Google ChromeBraveMicrosoft EdgeArcChromium

2. Supported Destination Setup Guides

CU

ClickUp Integration

Deep Space/List hierarchy sync, custom markdown descriptions & priority mapping

API Token (pk_...) • OAuth 2.0

How to obtain your ClickUp Personal API Token:

  1. Log in to your ClickUp workspace.
  2. Click your user profile avatar in the bottom-left corner and select Settings.
  3. Scroll down in the left navigation and click Apps or Integrations.
  4. Under the API Tokens card, click Generate Personal API Token.
  5. Copy the generated token (pk_...) and paste it into RecBug's Connection screen or Settings drawer.
🗂️ Hierarchy Navigation

RecBug automatically fetches all your authorized Workspaces, Spaces, Folders, and Lists.

⚡ Priority & Attachment Sync

Maps Urgent (1), High (2), Normal (3), Low (4) and uploads video, console logs, and HAR directly.

Jira

Atlassian Jira (Cloud & Server / Data Center)

Project Keys, Issue Types (Bug/Task/Story), Jira ADF formatting & attachments

Cloud API Token • Personal Access Token (PAT)

How to connect Jira Cloud:

  1. Visit https://id.atlassian.com/manage-profile/security/api-tokens and log in.
  2. Click Create API token, provide a label (e.g. RecBug QA), and copy the generated token.
  3. In RecBug, enter your Jira Domain (e.g. myteam.atlassian.net), your Atlassian Email, and the API Token.
  4. Select your target Project Key (e.g. DEV, BUG) and Issue Type (Bug).
📌 Jira Server / Data Center: Enter your custom self-hosted host URL and provide your Personal Access Token (PAT) generated under Jira Profile > Personal Access Tokens.
LIN

Linear

Team selector, issue states, urgency levels, and markdown description injection

Personal API Key (lin_api_...)

How to generate a Linear Personal API Key:

  1. In Linear, open Settings > Account > Security > Personal API Keys.
  2. Click New API Key, name it (e.g. RecBug Reporter), and copy the key (lin_api_...).
  3. Paste the key into RecBug. RecBug will automatically query Linear’s GraphQL API to populate all your organization’s Teams.
  4. Select the target engineering team and default state (e.g. Triage or Backlog).

Slack (Incoming Webhooks & Block Kit)

Instant bug notifications with Block Kit cards, error badges, and attachment links

Incoming Webhook URL • OAuth

How to create a Slack Incoming Webhook:

  1. Go to https://api.slack.com/apps or search for Incoming WebHooks in the Slack App Directory.
  2. Click Add to Slack and choose the channel where QA bug reports should be posted (e.g. #qa-incidents or #bug-reports).
  3. Copy the Webhook URL (formatted as https://hooks.slack.com/services/T.../B.../...).
  4. Paste the Webhook URL into RecBug’s Slack configuration card and click Test Connection.
💬 Block Kit Formatting: RecBug automatically formats the notification with title, priority pill, environment specs, console error counts, and direct links to the video reproduction.
MS

Microsoft Teams

Adaptive Card notifications for Microsoft 365 channels and developer triage teams

Connector Webhook • Power Automate URL

How to configure Microsoft Teams Webhooks:

  1. In Microsoft Teams, navigate to your desired team channel and click ••• (More options) > Connectors > Incoming Webhook (or set up a Power Automate "When a webhook request is received" workflow).
  2. Provide a name (e.g. RecBug Bug Triage), upload an icon, and click Create.
  3. Copy the generated Webhook URL (starts with https://outlook.office.com/webhook/... or https://prod-XX.logic.azure.com/...).
  4. Paste the URL into RecBug’s MS Teams configuration card.

Offline Standalone ZIP & HAR Export

Zero-network offline archives for air-gapped environments, email attachments, and local audits

No Cloud • 100% Local Archive

Download a complete, organized package directly to your local file system with zero network requests or third-party connections:

📁 recording.webm

High-definition screen & audio recording trimmed to the exact reproduction window.

🌐 network_requests.har

Standard HTTP Archive 1.2 log inspectable in Chrome DevTools Network panel.

📝 console_logs.json

Structured array of error, warn, and log statements with timestamps and stack traces.

🖼️ annotated_screenshots/

High-resolution screenshot captures with custom arrows, boxes, and text annotations.

3. In-Browser Video Trimmer & Markup Studio

RecBug features a custom in-browser media engine capable of trimming recordings down to 1-second increments directly in local memory:

  • Drag Trim Handles: Drag the cyan handles on the left and right sides of the filmstrip timeline track to define exact start and end cut points.
  • Timeline Markers: Click anywhere on the scrubber timeline to add an annotated marker to pinpoint the exact moment of failure.
  • Visual Annotator: Draw red highlight boxes, arrows, pointers, and custom text callouts directly onto screenshot attachments.

Security & Privacy Commitments

Strict Purpose Limitation & Ephemeral Processing

RecBug collects user-initiated screen recordings, console logs, and network telemetry strictly for bug reporting. Video recordings and annotations are transmitted to RecBug servers (api.recbug.com) for video transcoding/trimming. Media processing is strictly ephemeral and temporary files are deleted immediately after delivery. Data is never sold to third parties or data brokers, and is not used for advertising, marketing, or creditworthiness evaluation. Destination credentials remain stored in your local browser storage, and finalized reports are dispatched directly to your authorized tools (ClickUp, Jira, Linear, Slack, Teams).