# Auto-updating vector database

If enabled, `Vigil` can add submitted prompts back to the vector database for future detection purposes. When `n` number of scanners match on a prompt, that prompt will be indexed in the vector database.

Because each individual scanner is prone to false positives, it is recommended to set the threshold at `3` to require all input scanners (YARA, vector db, transformer) to match before auto-updating is invoked.

This is disabled by default but can be configured in the **`embedding`** section of the **`conf/server.conf`** file.

**Example configuration**

```ini
[embedding]
auto_update = true
update_threshold = 3
```

This configuration would require three different scanners to match against a submitted prompt before that prompt is indexed back in the database. 

The following metadata is stored alongside the detected prompt:

```json
{
     "uuid": scan uuid,
     "source": "auto-update",
     "timestamp": timestamp string,
     "threshold": update_threshold
 }
```

Once enabled, you will see log output similar to the screenshot below when the threshold is met:

<figure><img src="/files/0zv6CaQGodSG9WdZO9ZG" alt=""><figcaption><p>Auto-update example log output</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://vigil.deadbits.ai/overview/use-vigil/configuration/auto-updating-vector-database.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.