Skip to content
helios/docs — search
Type to search all six guides.

    From sign-up to a searchable index

    Guide 01

    A direct path from account creation to one indexed repository and one answered search.

    1. 01

      Create one workspace

      Create an account and name your organization. Each workspace keeps one code index; Hobby includes one workspace, Pro five, Team twenty-five.

    2. 02

      Connect GitHub

      Open Graph & Index and connect GitHub. You install the GitHub App on the account or organization that owns the code and choose which repositories the installation grants. Nothing outside that grant is read.

    3. 03

      Choose repositories

      Pick the granted repositories to index, on the branch GitHub reports as default or one you name. Hobby indexes one repository, Pro five, Team every repository the installation grants.

    4. 04

      Watch the index build

      Each repository is mirrored, its files split into syntax-aware chunks and, on Pro and Team, embedded. Graph & Index shows the state of each repository: mirroring, refreshing, fresh, stale, or failed, with the indexed commit and the file and chunk counts.

    5. 05

      Search from Home

      The Home page searches the index. Pattern search is on every plan; search by meaning and plain-language questions need Pro or Team.

    6. 06

      Give your agents the same index

      Mint an API key in Manage account → Access, then follow the MCP guide to connect Codex, Claude Code, or GitHub Copilot CLI. On your desktop, sign Fluxcode in from its own window and approve the request in mux; no key is copied by hand.

    Choose pattern or meaning

    Section titled “Choose pattern or meaning”

    Pattern search (grep_code). Matches the shape of the syntax tree rather than text: foo($X) finds every call of foo with one argument, whatever that argument is. Narrow it with a repository, a language, or a path prefix inside the corpus. Every plan includes it.

    Search by meaning (search_code). Ranks chunks by what they mean, not by the words they contain, and returns the repository, file path, start and end lines, a score, and an excerpt. Pro and Team.

    Ask a question (ask_code). Takes a question in plain words and returns the passages from the index that bear on it, for your agent to read. The answer itself is not written for you. Pro and Team.

    On Hobby, search_code and ask_code answer 403 with {"error":{"code":"plan_refused"}} rather than quietly returning pattern results.

    How the index stays current

    Section titled “How the index stays current”

    One mirror is kept per selected repository and re-indexed from the branch you chose. Hobby refreshes only when someone asks for a refresh; Pro and Team refresh on push. A repository whose latest commit differs from its indexed commit is reported as stale, and anyone with the editor or owner role can refresh it from Graph & Index.

    Removing a repository removes its mirror and its part of the index.