Skip to Content
v1.33.6 · shipped One-screen report · Looks like your app Read the changelog →
Admin consoleResearch
Pin QA + product findings so the next iteration starts smarter · · open live demo ↗

Research

Route: /research (a Lab: under More pages in the sidebar unless you keep it there)

Research in Mushi Mushi is a web search through your own Firecrawl key. Use it while reviewing a bug to find release notes, Stack Overflow threads or vendor changelogs, and attach what helps to the bug. The tabs are Search and History.

What it’s for

  • Debug a library error: “Why does react-query v5 throw on an empty select return?”
  • Find migration paths: “How do I upgrade from Next.js 14 to 15 App Router?”
  • Check best practices: “What are the current Supabase RLS performance recommendations?”

Each search is saved as a session for the project, so teammates can open it from History (query, mode, number of results and when) without running it again.

  1. Type a query of 2 to 500 characters (an error signature, library name or doc topic).
  2. Press Search or Enter.

Each result card shows the page title, its URL and an excerpt of the page text, plus Attached or Not attached. Results are not summarised by AI and carry no relevance score.

If the search fails, the page names the reason:

  • FIRECRAWL_NOT_CONFIGURED: no Firecrawl key for this project. Open Firecrawl key takes you to it.
  • FIRECRAWL_AUTH_FAILED: Firecrawl rejected the key.
  • RATE_LIMITED: Firecrawl is rate-limiting you. Try again shortly.
  • SEARCH_FAILED: the search did not complete.

Research sessions are stored in Mushi Mushi’s database for your project and are not shown to other teams. Firecrawl processes queries on their infrastructure using your key; see their privacy policy .

Attaching a result to a bug

Click Attach to bug on a result, pick the bug under Which bug does this help?, and click Attach to this bug. The card then reads Saved on bug with a link to it.

Automatic results on error reports

When a report carries a real error (a Sentry exception or an error-level console line), Mushi Mushi searches for it once after diagnosis and shows the results on the report under Others who hit this.

  • Where it looks: Firecrawl’s developer index first (GitHub issues, merged pull requests, READMEs and docs), then GitHub and Stack Overflow web results for any remaining slots. The developer index often finds the pull request that fixed the same error.
  • Search again / Search now: runs the search from the report page. Only results not already on the report are added. Pressing it twice within 10 minutes searches once.
  • Cost: about 2 to 5 Firecrawl credits per search, billed to your own key.

Prerequisites

A Firecrawl API key must be configured in Settings → AI keys before Research works. A key shared with every app in your organization works too.

  • Settings — add your Firecrawl key
  • Bugs — where attached results and Others who hit this appear
Last updated on
ExperimentsSettings