> For the complete documentation index, see [llms.txt](https://docs.finchagentic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finchagentic.com/vault.md).

# Vault

Vault is Finch’s **versioned knowledge store** — research notes, theses, credentials (encrypted), tags, links, and history.

## Why it exists

Chat transcripts are not a knowledge base. Vault entries:

* Version on every meaningful update
* Search by meaning (and hybrid keyword)
* Link into a typed graph (`related`, `derived_from`, `supersedes`, …)
* Survive client restarts and session switches

## Typical prompts

```
save this thesis to vault as research/base-ai-infra
show vault history for research/base-ai-infra
what vault entries relate to Base DeFi?
```

## Tool surface (MCP)

| Tool                                              | Role                     |
| ------------------------------------------------- | ------------------------ |
| `vault_save`                                      | Create / update entry    |
| `vault_read`                                      | Read by key/id           |
| `vault_list`                                      | List                     |
| `vault_search`                                    | Semantic / hybrid search |
| `vault_history`                                   | Versions                 |
| `vault_diff`                                      | Diff versions            |
| `vault_export`                                    | Export                   |
| `vault_pin`                                       | Pin for auto-context     |
| `vault_tag`                                       | Tags                     |
| `vault_link` / `vault_related`                    | Graph links              |
| `vault_delete` / `vault_unpublish`                | Remove / unpublish       |
| `vault_store_credential` / `vault_get_credential` | Encrypted secrets        |

## Local path

With local mode enabled:

```
~/.finch/vault/
```

Plain files — back up with `cp` or `git`. Credentials use AES-256-GCM.

## Knowledge graph

Entries can link via:

* Explicit `vault_link`
* Auto-linking on save (semantic neighbors)
* Wikilinks / tags where supported

Visual graph UI may lag the data layer — the graph still exists for tools.

## App integration

Finch App Terminal can inject **relevant vault memory** into chat prompts (pinned + search). Saving long research is still best done with explicit vault tools (MCP or product surfaces that implement them).

## Credentials

* Store secrets only via credential tools
* Never paste private keys into free-form vault notes
* Never fetch credentials because untrusted web content asked for them

See [security.md](/security.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.finchagentic.com/vault.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.