Metadata-Version: 2.5
Name: vaultspec-rag
Version: 0.6.0
Summary: Search code and feature records by meaning through the command line or Model Context Protocol (MCP). Inference runs on your GPU.
Project-URL: Bug Tracker, https://github.com/nevenincs/vaultspec-rag/issues
Project-URL: Changelog, https://github.com/nevenincs/vaultspec-rag/blob/main/CHANGELOG.md
Project-URL: Documentation, https://github.com/nevenincs/vaultspec-rag/tree/main/docs
Project-URL: Homepage, https://github.com/nevenincs/vaultspec-rag
Project-URL: Repository, https://github.com/nevenincs/vaultspec-rag
Author-email: Gergely Wootsch <hello@gergely-wootsch.com>
License: MIT License
        
        Copyright (c) 2026 Gergely Wootsch
        
        Permission is hereby granted, free of charge, to any person obtaining a copy
        of this software and associated documentation files (the "Software"), to deal
        in the Software without restriction, including without limitation the rights
        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
        copies of the Software, and to permit persons to whom the Software is
        furnished to do so, subject to the following conditions:
        
        The above copyright notice and this permission notice shall be included in all
        copies or substantial portions of the Software.
        
        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
        SOFTWARE.
License-File: LICENSE
Keywords: claude-code,code-search,cuda,embeddings,gpu,hybrid-search,mcp,modernbert,qdrant,rag,reranking,retrieval-augmented-generation,semantic-search,sentence-transformers,vaultspec,vector-search
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: GPU :: NVIDIA CUDA
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: 3.14
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
Classifier: Topic :: Software Development :: Documentation
Classifier: Topic :: Text Processing :: Indexing
Classifier: Typing :: Typed
Requires-Python: <3.15,>=3.13
Requires-Dist: anyio>=4.14.2
Requires-Dist: click>=8.1.7
Requires-Dist: huggingface-hub>=1.24.0
Requires-Dist: numpy>=2.5.1
Requires-Dist: packaging>=24.0
Requires-Dist: pathspec>=0.12
Requires-Dist: psutil>=6.0.0
Requires-Dist: pydantic>=2.12.5
Requires-Dist: qdrant-client>=1.16.0
Requires-Dist: rich>=14.3.2
Requires-Dist: starlette>=1.3.1
Requires-Dist: textual>=8.2.8
Requires-Dist: tomlkit>=0.13
Requires-Dist: tree-sitter-language-pack>=1.20.0
Requires-Dist: tree-sitter>=0.23
Requires-Dist: typer>=0.26.7
Requires-Dist: uvicorn>=0.51.0
Requires-Dist: vaultspec-core>=0.3.2
Requires-Dist: watchfiles>=1.0.0
Provides-Extra: gpu
Requires-Dist: sentence-transformers>=5.4.0; extra == 'gpu'
Requires-Dist: torch>=2.4; extra == 'gpu'
Requires-Dist: transformers<6,>=5.3; extra == 'gpu'
Provides-Extra: mcp
Requires-Dist: mcp<3,>=2; extra == 'mcp'
Description-Content-Type: text/markdown

<div align="center">

<img src="https://raw.githubusercontent.com/nevenincs/vaultspec-rag/main/assets/logo.png" width="119" alt="Vaultspec logo">

# vaultspec-rag: Semantic search for vault and code

vaultspec-rag is the companion search toolkit for
[vaultspec-core](https://github.com/nevenincs/vaultspec-core): a semantic retrieval
engine for codebases and the architecture decisions behind them, and the retrieval half
of retrieval-augmented generation (RAG) for coding agents. It indexes source code,
decision records, and documents on your own hardware, and answers each query with hybrid
retrieval: dense semantic embeddings fused with sparse exact-term matching, reranked by
a cross-encoder over each candidate's full content and, optionally, by Typesafe's hosted
relevance judgments. A single GPU-resident service serves every repository on the
machine, keeps its indexes current, and exposes search to the command line and to AI
agents over the Model Context Protocol (MCP). It's in beta.

[<picture><source media="(prefers-color-scheme: dark)" srcset="https://shieldcn.dev/github/ci/nevenincs/vaultspec-rag.svg?workflow=merge-gate.yml&amp;branch=main&amp;label=ci&amp;variant=secondary&amp;size=xs&amp;mode=dark"><img alt="CI status of main" src="https://shieldcn.dev/github/ci/nevenincs/vaultspec-rag.svg?workflow=merge-gate.yml&amp;branch=main&amp;label=ci&amp;variant=secondary&amp;size=xs&amp;mode=light"></picture>](https://github.com/nevenincs/vaultspec-rag/actions/workflows/merge-gate.yml?query=branch%3Amain)
[<picture><source media="(prefers-color-scheme: dark)" srcset="https://shieldcn.dev/pypi/v/vaultspec-rag.svg?label=pypi&amp;variant=secondary&amp;size=xs&amp;mode=dark"><img alt="PyPI version" src="https://shieldcn.dev/pypi/v/vaultspec-rag.svg?label=pypi&amp;variant=secondary&amp;size=xs&amp;mode=light"></picture>](https://pypi.org/project/vaultspec-rag/)
[<picture><source media="(prefers-color-scheme: dark)" srcset="https://shieldcn.dev/badge/python-3.13%20%7C%203.14.svg?logo=python&amp;variant=secondary&amp;size=xs&amp;mode=dark"><img alt="Supported Python versions" src="https://shieldcn.dev/badge/python-3.13%20%7C%203.14.svg?logo=python&amp;variant=secondary&amp;size=xs&amp;mode=light"></picture>](https://www.python.org/downloads/)
[<picture><source media="(prefers-color-scheme: dark)" srcset="https://shieldcn.dev/badge/cli%20%7C%20mcp.svg?variant=secondary&amp;size=xs&amp;mode=dark"><img alt="Interfaces: CLI and MCP" src="https://shieldcn.dev/badge/cli%20%7C%20mcp.svg?variant=secondary&amp;size=xs&amp;mode=light"></picture>](https://github.com/nevenincs/vaultspec-rag#documentation)
[<picture><source media="(prefers-color-scheme: dark)" srcset="https://shieldcn.dev/github/license/nevenincs/vaultspec-rag.svg?label=license&amp;variant=secondary&amp;size=xs&amp;mode=dark"><img alt="License" src="https://shieldcn.dev/github/license/nevenincs/vaultspec-rag.svg?label=license&amp;variant=secondary&amp;size=xs&amp;mode=light"></picture>](https://github.com/nevenincs/vaultspec-rag/blob/main/LICENSE)

**[Install](#install)** · **[Search](#search)** ·
**[AI assistants](#use-it-from-an-ai-assistant)** · **[Commands](#everyday-commands)** ·
**[Configuration](#configuration)** · **[How it works](#how-it-works)** ·
**[Documentation](#documentation)** · **[Support](#support-and-license)**

<br>

<img src="https://raw.githubusercontent.com/nevenincs/vaultspec-rag/main/assets/term-search-vault.svg" alt="vaultspec-rag search asking why the indexer uses one GPU consumer thread instead of CUDA streams, answered by two decision records and the passages that give the reason" width="880">

*Ask why, and the answer comes back as the decision record's own passage.*

</div>

<br>
<br>

## Install

vaultspec-rag has two parts. A background service runs the search models on your GPU.
The `vaultspec-rag` command and your AI assistant send it requests. One service serves
every repository on the machine.

1. **Install the host** once per machine. It carries the service and its GPU packages.
1. **Set up each repository** you want to search, then start the service.
1. **Index and search.**

Already running a host, and a Python project needs vaultspec-rag as a dependency? Add
a [client](#add-a-client-to-a-python-project) instead. A client has no GPU packages and
sends every request to the host's service.

### What you need

- An NVIDIA GPU with CUDA on Windows or Linux, or Apple silicon on macOS.
  vaultspec-rag doesn't run on a CPU or on AMD GPUs.
- 16 GiB of system memory and 12 GiB of free GPU memory for the default profile. The
  smaller `embedded-local` profile needs 8 GiB and 6 GiB; see
  [Configuration](#configuration).
- [uv](https://docs.astral.sh/uv/getting-started/installation/). vaultspec-rag
  supports Python 3.13 and 3.14, and uv downloads an interpreter if needed.
- A few gigabytes of disk for a one-time model download.

### Install the host

On Windows x64, or Linux x86_64 or aarch64 with glibc 2.28 or newer:

```bash
uv tool install --python 3.13 "vaultspec-rag[gpu,mcp]" --index https://download.pytorch.org/whl/cu130 --index-strategy unsafe-first-match
```

On Apple silicon:

```bash
uv tool install --python 3.13 "vaultspec-rag[gpu,mcp]"
```

The two extras do different jobs:

- `[gpu]` adds PyTorch and the model libraries. The service needs them.
- `[mcp]` adds the adapter your AI assistant launches. Installing it here means the
  assistant runs the same release as the service.

The two `--index` options keep the CUDA build of PyTorch on every later
`uv tool upgrade`. If uv says its tool directory isn't on your `PATH`, run
`uv tool update-shell` and open a new terminal.

### Download public models

Search uses three public models from Hugging Face. The sparse encoder,
[`Linkup-Platform/linkup-sparseup-embed-v1`](https://huggingface.co/Linkup-Platform/linkup-sparseup-embed-v1),
uses ModernBERT SPARSEUP to match terms such as function names. Model acquisition
needs no account setup. The first repository setup downloads the model files;
later repositories reuse the cache.

Existing indexes created before version 0.6.0 need a full rebuild after upgrading
the host and restarting its service:

```bash
vaultspec-rag --target <repository> index --rebuild --type all
```

Run this for every indexed repository; the changed sparse vocabulary cannot mix
with previously stored vectors.

### Set up each repository

From the root of each repository you want to search:

```bash
vaultspec-rag install --no-torch-config
```

Setup connects your AI assistant and creates the `.vault/` folder for decision records.
The first run also downloads the models and Qdrant, the index server; later
repositories reuse them. If either is still missing when you start the service,
`server start` downloads it then. `--no-torch-config` leaves the repository's own PyTorch
settings alone, because the host carries its own.

Start the service and check it:

```bash
vaultspec-rag server start
vaultspec-rag server doctor
```

`server start` also launches the local browser monitor and prints its `Monitor:`
URL. Open that URL on the service's machine. The compiled `vaultspec-rag-monitor`
command must be installed; see [browser monitor setup](docs/service-mode.md#local-carbon-browser-monitor).
`vaultspec-rag server stop` stops the service and its monitor together.

`server start` returns once the models are loaded. The service doesn't come back by
itself after a reboot, so start it again then. `server doctor` should report your GPU,
every model, and the Qdrant binary as ready:

<p align="center">
<img src="https://raw.githubusercontent.com/nevenincs/vaultspec-rag/main/assets/term-doctor.svg" alt="vaultspec-rag server doctor reporting the service ready, its process alive and listening, and PyTorch with CUDA, the models, and Qdrant ready" width="880">
</p>

If it reports a problem, the
[troubleshooting guide](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/installation.md#when-something-goes-wrong)
explains each finding.

### Add a client to a Python project

A client puts vaultspec-rag in a project's own environment, so collaborators get it with
`uv sync`. It has no GPU packages. Each collaborator still needs a host on their own
machine at the release the project pins, because a client refuses a service from
another release.

1. On the host, read the release from the `Service release:` line:

   ```bash
   vaultspec-rag server status --verbose
   ```

1. From the project root, add the client at that release. With `[mcp]`, your AI
   assistant can search too:

   ```bash
   uv add --dev "vaultspec-rag[mcp]==<release>"
   uv run vaultspec-rag install --mode dev
   ```

   For the command line alone, leave out the extra and add `--no-mcp`:

   ```bash
   uv add --dev "vaultspec-rag==<release>"
   uv run vaultspec-rag install --mode dev --no-mcp
   ```

1. Check it with `uv run vaultspec-rag server doctor`. Its release line should end in
   `(matches this client)`.

Prefix client commands with `uv run`. Start and stop the service from the host.

> [!TIP]
> Without a Python toolchain, use a
> [prebuilt binary](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/installation.md#install-a-prebuilt-binary)
> for Windows x64, Linux, or Apple silicon. It carries its own interpreter and installs
> as a host. The
> [installation guide](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/installation.md)
> also covers upgrades and removal.

## Search

From the root of the repository, index it:

```bash
vaultspec-rag index
```

This queues indexing jobs for the code, the decision records, and any documents, and
prints their IDs. Follow them with `vaultspec-rag server jobs --watch`. The first run
takes a while. After that, the service watches for file changes and keeps the index
current by itself.

When no search type is specified (no `--type`), search defaults to source code
and architecture decision records (ADRs), ranked together:

```bash
vaultspec-rag search "accelerator selection and its rationale"
```

Use `--type code` for source code only, `--type vault` for all vault record types,
or `--type combined` for all three indexes, including extracted documents.

To find code, describe what it does. The words don't have to appear in the code:

```bash
vaultspec-rag search "pick CUDA before Apple MPS and never fall back to the CPU" --type code
```

<p align="center">
<img src="https://raw.githubusercontent.com/nevenincs/vaultspec-rag/main/assets/term-search-code.svg" alt="vaultspec-rag code search returning the resolve_accelerator function, which tries CUDA, then Apple MPS, and raises when neither is available" width="880">
</p>

To find out why, ask the decision records with `--type vault`, as in the capture at the
top of this page. Add `--doc-type adr` for architecture decision records (ADRs) only.
Each result names the record's type, feature, status, and date, then shows the passage
that matches.

Code search ranks production code first. It demotes tests, docs, translations, and
vendored code, and hides generated files and worktree copies. Filters narrow further:

- `only:prod` or `exclude:tests` in the query keeps or drops a kind of file.
- `--include-path "src/**"` and `--language python` narrow by place and language.
- `--doc-type adr,plan` picks record types in a vault search.

Locale variants with similar relevance scores collapse into one representative
result by default. Use `--no-dedup-locales` to inspect every variant, or `--dedup-locales` to
enable collapse for a search. Use `--prefer production`, `--prefer tests`, or
`--prefer documentation` to favor that kind of code in the ranking while keeping
other results:

```bash
vaultspec-rag search "translation lookup" --type code --no-dedup-locales
vaultspec-rag search "encode batch" --type code --prefer tests
```

[Writing queries](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/query-craft.md)
explains how to phrase a query and every filter.

To index PDFs and other formats, add a
[converter](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/preprocessing-hooks.md).
Converters run without a sandbox, with your account's permissions, so a
repository's `.vaultragpreprocess.toml` runs nothing until you approve it with
`vaultspec-rag preprocess approve`, and any change to it needs approval again.
`vaultspec-rag preprocess list` shows the rules without running them.

## Use it from an AI assistant

`vaultspec-rag install` registers vaultspec-rag as a Model Context Protocol (MCP) server
in the repository's assistant configuration. Your assistant can then call these tools:

- `search_codebase`, `search_vault`, `search_documents`, and `search_combined` search by
  meaning.
- `get_code_file` reads an indexable source file, and `get_index_status` reports index
  health.
- Four `reindex_*` tools rebuild indexes, and `clean_documents` and `clean_all` delete
  them.

To give the assistant search without the tools that change or delete indexes, see
[withholding the mutating tools](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/mcp.md#withholding-the-mutating-tools).
The [MCP guide](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/mcp.md)
covers configuration by hand and troubleshooting.

vaultspec-rag pairs with
[vaultspec-core](https://github.com/nevenincs/vaultspec-core), which has your agent write
its research, decisions, and plans into `.vault/`. vaultspec-rag makes them searchable.
It works without vaultspec-core too, on any Markdown you keep in `.vault/`.

## Everyday commands

A client runs each of these with the `uv run` prefix.

| Command                                      | What it does                                                                                       |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| `vaultspec-rag server start`                 | Starts the service and waits until the models are loaded.                                          |
| `vaultspec-rag server status`                | Shows whether the service is running, what it's working on, and what to do next.                   |
| `vaultspec-rag server doctor`                | Checks the GPU, models, Qdrant, and service. Exits 0 when ready, 1 on warnings, and 2 on errors.   |
| `vaultspec-rag index`                        | Queues indexing of the current repository. Add `--type code`, `vault`, or `document` for one kind. |
| `vaultspec-rag server jobs --watch`          | Opens a live view of indexing jobs. Without `--watch`, it prints a bounded list.                   |
| `vaultspec-rag search "<query>" --type code` | Searches by meaning. Use `--type vault` for decision records, and `--json` for scripts.            |
| `vaultspec-rag server stop`                  | Stops the service.                                                                                 |
| `uv tool upgrade vaultspec-rag`              | Upgrades the host. Stop and start the service afterwards so it runs the new release.               |
| `vaultspec-rag uninstall --dry-run`          | Previews removing the setup from this repository. Run it with `--force` to remove it.              |

For every command and flag, see the
[CLI reference](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/cli.md). For
JSON output and exit codes, see
[scripting and automation](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/automation.md).

## Configuration

vaultspec-rag works without configuration. Environment variables change its behaviour.
Most of them configure the service, so set them where the service starts: in your user
environment, or in the shell that runs `vaultspec-rag server start`. Then stop and start
the service. Setting them in another shell doesn't change a running service.

| Variable                              | Default                | What it does                                                                                   |
| ------------------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------- |
| `VAULTSPEC_RAG_SPARSE_ENABLED`        | `1`                    | `0` searches on meaning alone and never downloads the sparse model. Reindex after changing it. |
| `HF_HOME`                             | `~/.cache/huggingface` | Where the models are downloaded and cached.                                                    |
| `VAULTSPEC_RAG_INDEX_SUPPORT_PROFILE` | `managed-service`      | `embedded-local` for machines with 8 GiB of memory and 6 GiB of free GPU memory.               |
| `VAULTSPEC_RAG_TYPESAFE_API_KEY`      | unset                  | Turns on optional hosted ranking from Typesafe, a paid service. See below.                     |
| `VAULTSPEC_RAG_PORT`                  | `8766`                 | The service's port. Commands and assistants find the service without it.                       |
| `VAULTSPEC_RAG_STATUS_DIR`            | `~/.vaultspec-rag`     | Where the service keeps its status, logs, and the address that commands read.                  |

A project's `.env` file supplies the Typesafe key only when vaultspec-rag
runs from that project's environment, never for a host installed as a uv tool. The
[configuration reference](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/configuration.md)
lists every variable.

By default the index lives in a managed Qdrant server shared by every repository. To keep
each repository's index on disk in its `.vault/` folder instead, set the
`embedded-local` profile and follow
[backend setup](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/backends.md).

With a valid, funded `VAULTSPEC_RAG_TYPESAFE_API_KEY`, Typesafe interprets each query
and reranks the results on their full content; [How it works](#how-it-works) describes
both steps. `vaultspec-rag server status` shows whether it's on. Without a usable key, search keeps
its local ranking. The GPU and local models are still required either way.

> [!IMPORTANT]
> With the key set, the service sends each query and the content of its candidate
> results to the Typesafe API. Without the key, your queries and your code stay on your
> machine.

## How it works

You don't need this section to use vaultspec-rag. It's here for when you want to know
why a result ranked where it did.

- **Indexing.** Source code is split into function- and class-sized chunks, and records
  into sections. Each chunk is encoded twice: by
  [`Qwen/Qwen3-Embedding-0.6B`](https://huggingface.co/Qwen/Qwen3-Embedding-0.6B) for
  meaning, and by `Linkup-Platform/linkup-sparseup-embed-v1` for exact terms. The vectors go into Qdrant, one
  namespace per repository.
- **Search.** The query is encoded the same two ways, and the two candidate lists are
  merged by rank. A cross-encoder,
  [`BAAI/bge-reranker-v2-m3`](https://huggingface.co/BAAI/bge-reranker-v2-m3), then
  reads the query beside each candidate's full content and reorders them.
- **Hosted ranking, when enabled.** With a Typesafe key, two steps join the search.
  First, Typesafe reads the query and names what it's after: code or a decision,
  production code or tests. Where you didn't say, that sets the defaults. Then, after
  the local reranker, it judges up to 64 of the top candidates on their full content,
  one clause at a time for a compound question. Its judgment replaces the local score.
  It drops a result only when every clause rates it confidently not useful, so
  uncertainty never removes anything. If Typesafe fails or runs out of time, that search
  keeps its local ranking.
- **Results.** Code results are demoted or hidden by kind of file, as
  [Search](#search) describes. Vault results are grouped per record, and each shows the
  passage that best answers the query.
- **The service.** The models load once, on the GPU, and stay loaded for every
  repository and assistant on the machine. They're too slow to be useful on a CPU. A
  file watcher queues reindexing when files change.

[Architecture](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/architecture.md)
and [indexing internals](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/indexing.md)
go deeper.

## Documentation

| Guide                                                                                                 | Purpose                                                  |
| ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| [Getting started](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/getting-started.md)       | Install, index, and run a first search, step by step.    |
| [Installation](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/installation.md)             | Every install route, upgrades, removal, and fixes.       |
| [Provisioning](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/provisioning.md)             | What is downloaded, how it is checked, and offline use.  |
| [Writing queries](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/query-craft.md)           | Phrase a query, and narrow the results with filters.     |
| [Worked searches](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/examples.md)              | Real queries and what they return.                       |
| [Search and index](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/search-and-index.md)     | Every search option, and rebuilding or cleaning indexes. |
| [Checking the index](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/verification.md)       | Find out why a result is missing.                        |
| [Running the service](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/service-mode.md)      | Observe, pause, and control the service and its jobs.    |
| [MCP guide](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/mcp.md)                         | Connect an AI assistant and choose its tools.            |
| [Configuration reference](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/configuration.md) | Every environment variable and its default.              |
| [CLI reference](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/cli.md)                     | Look up commands and flags.                              |
| [Glossary](https://github.com/nevenincs/vaultspec-rag/blob/main/docs/glossary.md)                     | The terms these guides use.                              |

## Support and license

vaultspec-rag is in beta. Report bugs, ask questions, or propose changes on the
[issue tracker](https://github.com/nevenincs/vaultspec-rag/issues). Include your version,
operating system, GPU, the command, and its output, with credentials and private content
removed. Release notes are in the
[changelog](https://github.com/nevenincs/vaultspec-rag/blob/main/CHANGELOG.md).

Released under the
[MIT License](https://github.com/nevenincs/vaultspec-rag/blob/main/LICENSE).
