Discovery Copilot is the Quikly Copilot browser extension (Chrome and Chromium-based browsers such as Edge). It runs alongside Google Meet, Zoom Web, and Microsoft Teams Web so you can capture live meeting audio, see a rolling transcript, and receive discovery-style prompts grounded in the client and deal context you load from Quikly. It complements Discovery Gen in the web app: Discovery Gen is for structured sessions and reports inside Quikly; Discovery Copilot is for real-time help while you are already in a video call.Documentation Index
Fetch the complete documentation index at: https://docs.getquikly.com/llms.txt
Use this file to discover all available pages before exploring further.
Distribution: Your team or Quikly provides the install path (Chrome Web Store listing, managed policy, or an unpacked build for development). This page describes how the product works once installed.
What you get
- Side panel UI — transcript stream, suggestions, and scope context in one place (Chrome side panel).
- Live transcription — meeting audio from the tab (remote participants) plus your microphone is mixed, sent to Deepgram (Nova-class streaming), and displayed as text. Audio is not stored by the extension; it is processed for transcription in real time.
- Quikly-backed intelligence — after you authenticate, the extension calls Quikly’s Live Copilot API with transcript context so suggestions align with your workspace (clients, deals, proposals where applicable).
- Meeting detection — content scripts recognize Meet, Zoom (
*.zoom.us), and Teams (teams.microsoft.com,teams.live.com) tabs so the copilot knows you are in a supported meeting surface.
Requirements
- Browser: Chrome 116+ (Manifest V3), or a Chromium browser that supports side panel + the same extension package (for example Edge builds from the same codebase).
- Meeting: A supported platform opened in a normal tab (web clients, not desktop-only clients unless the tab is still a supported URL).
- Quikly access: A valid Quikly account and an API key created in the app (Settings → Integrations → API Keys or the link shown in the extension sign-in screen).
Installation and first run
Install the extension
Install Quikly Copilot using the method your organization or Quikly provides (store link, ZIP from a secure channel, or developer Load unpacked for local builds).
Pin or open the side panel
Click the puzzle icon in Chrome (or the extension icon), choose Quikly Copilot, and open the side panel when you are on or about to join a Meet, Zoom Web, or Teams Web call.
Sign in with an API key
Paste a Quikly API key from Settings → Integrations → API Keys in the app. The extension validates it against Quikly (
/users/me pattern) and stores it locally for subsequent sessions.Using it during a call
- Join the meeting in Meet, Zoom Web, or Teams Web in a regular browser tab.
- Open Quikly Copilot’s side panel for that window.
- Start live capture when prompted (after consent). You should see transcription updating as people speak.
- Load context from Quikly when the UI offers it — for example link a client or deal so suggestions and matching use the same data as your pipeline and proposals.
- Use suggested discovery prompts or notes to steer the conversation; copy anything you need into Discovery Gen or a new proposal later.
Permissions (why the extension needs them)
The extension requests only what it needs to mix tab + mic audio, show the panel, and talk to Quikly and Deepgram:| Permission / host | Purpose |
|---|---|
sidePanel | Main Discovery Copilot UI attached to the browser window |
tabCapture | Capture audio from the meeting tab (other participants) |
offscreen | Offscreen document for AudioWorklet / PCM processing |
storage | Session and API key storage |
activeTab / tabs | Detect meeting tab URL and title |
meet.google.com, *.zoom.us, teams.microsoft.com, teams.live.com | Meeting surfaces |
calendar.google.com | Optional hooks for calendar-aware flows where implemented |
api.getquikly.com (and localhost in dev) | Live Copilot and auth against your backend |
| Deepgram hosts | Streaming speech-to-text |
Privacy and data handling
- Audio: Processed for live transcription; the README architecture states audio is not persisted in the extension — it is streamed for STT.
- Transcript and suggestions: Shown in your panel; downstream retention follows Quikly product behavior for Live Copilot endpoints and your org’s policies.
- API key: Stored in extension storage; protect your device and revoke keys you no longer need from Settings → Integrations in the app.
Troubleshooting
| Issue | What to try |
|---|---|
| 401 / invalid key | Regenerate the API key in Quikly, paste again, confirm no trailing spaces. |
| No transcription | Confirm consent was granted, the meeting tab is active, and the platform is web (Meet / Zoom / Teams in browser). |
| Wrong client context | Re-select the client or deal in the panel; some flows auto-match from meeting title — verify the proposed match before relying on it. |
| Side panel empty | Reload the extension or the tab; confirm you are on a supported host. |
Related documentation
- Proposal editor (wizard) — Step 2→3 Analyze and continue and the rest of the assistant flow.
- Discovery Gen — Structured discovery workspace, scorecard, PDF, and handoff to proposals inside Quikly.
- AI features — Quimy in the proposal editor and product-wide AI behavior.
- API keys — Creating and revoking keys used by the extension and automations.
- Clients — Client records that feed context in the app and in copilot flows.
- Deals pipeline — How deals relate to proposals and discovery context.