Answer developer questions from your source code

Rapidflare can answer developers' questions straight from your source code. Connect a GitHub repository to a hub, and the agent searches and reads the actual files the way an engineer would, then answers with citations to the exact files and line ranges it used.

What code search is for

Code search answers the questions documentation runs out on: what an error code means, which pins an example uses, which call replaces an old one in a new version, or what a release note says you must do after an upgrade. Your SDKs, libraries, firmware, examples and reference designs become knowledge the agent can check, alongside your documents and product catalog.

The agent doesn't guess from memory. It searches the repository, opens the files that answer the question, and states only what those files show. When the code doesn't settle a question, it says so instead of filling the gap.

How it works

Code search has three parts:

1. Connect a repository. Add a GitHub repository as a source and link it to a hub. Public repositories work right away. Private repositories need your organization's GitHub App integration turned on. See Add GitHub repositories.
2. Rapidflare takes a snapshot. Each sync packs the files that matter at the branch's latest commit and writes a short guide to the repository's layout. Nothing is split into chunks or rewritten. See How Rapidflare ingests a repository.
3. The agent searches it when a question needs code. Turn on the Software knowledge type for the hub. The agent then hands code questions to a code search step that searches, lists and reads files, and it cites every fact it uses. See Code search in agent answers.

Where it's available

Code search works on hubs that use the Single Front Door agent, with the Software knowledge type turned on. It reads GitHub repositories today.