Skip to content

Commit

Permalink
πŸ“ update codebase embeddings page
Browse files Browse the repository at this point in the history
  • Loading branch information
sestinj committed Jan 22, 2024
1 parent 175dbac commit 4357a63
Showing 1 changed file with 11 additions and 3 deletions.
14 changes: 11 additions & 3 deletions docs/docs/walkthroughs/codebase-embeddings.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,19 @@ keywords: [talk, embeddings, codebase, experimental]

Continue indexes your codebase so that it can later automatically pull in the most relevant context from throughout your workspace. This is done via a combination of embeddings-based retrieval and keyword search. By default, all embeddings are calculated locally with `all-MiniLM-L6-v2` and stored locally in `~/.continue/index`.

## How to use codebase retrieval
<!-- ## How to use codebase retrieval -->

Currently, the codebase retrieval feature is available as the "codebase" context provider. You can use it by typing `@codebase` in the input box, and then asking a question. The contents of the input box will be compared with the embeddings from the rest of the codebase to determine relevant files.
Currently, the codebase retrieval feature is available as the "codebase" and "folder" context providers. You can use them by typing `@codebase` or `@folder` in the input box, and then asking a question. The contents of the input box will be compared with the embeddings from the rest of the codebase (or folder) to determine relevant files.

There are a few options that let you configure the behavior of the codebase context provider. These can be set in `config.json`:
<!-- Here are some common use cases where it can be useful:
### Asking high-level codebase questions
- -->

## Configuration

There are a few options that let you configure the behavior of the codebase context provider. These can be set in `config.json`, and are the same for the codebase and folder context providers:

```json title="~/.continue/config.json"
{
Expand Down

0 comments on commit 4357a63

Please sign in to comment.