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

# Welcome to Vayl

**Give your agent memory that stays true.** Most memory layers *accumulate* — they save every fact and later hand your agent a stale one. Vayl **reconciles**: a new value supersedes the old, a removal actually retracts, ambiguous input is flagged instead of guessed, and the full history stays queryable and auditable. It speaks the [Model Context Protocol](https://modelcontextprotocol.io), so any MCP client plugs in.

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask a question…</button>

<button type="button" class="button secondary" data-action="ask" data-query="How do I connect Vayl to my MCP client" data-icon="bolt">Connect an MCP client</button><button type="button" class="button secondary" data-action="ask" data-query="What is reconciling memory" data-icon="book">What is reconciling memory?</button><button type="button" class="button secondary" data-action="ask" data-query="How do I scope memory per user" data-icon="sitemap">Scope memory per user</button>

***

## See it in one example

Vayl turns a conversation into facts and keeps only what is true now — while preserving the history.

```
"We use Redux."                            → remembered
"Actually we moved off Redux to Zustand."  → Redux retired, Zustand active
"What do we use?"                          → "Zustand"   (not "Redux, Zustand")
"What did we use first?"                   → "Redux"     (history kept)
```

{% hint style="info" icon="sparkles" %}
**New to reconciling memory?** Read [Core concepts](/vayl-docs/documentation/core-concepts/core-concepts.md) to understand *supersede*, *retract*, and the *same-slot invariant* — the ideas that make "what's true now" unambiguous.
{% endhint %}

## Where to start

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-rocket-launch" style="color:$primary;">:rocket-launch:</i></h4></td><td><h4>Getting started</h4></td><td>Install Vayl and connect it to your MCP client in minutes.</td><td><a href="/pages/c1c2bf7d7c5c4cdb53233f70a53b30ff0cc71460">/pages/c1c2bf7d7c5c4cdb53233f70a53b30ff0cc71460</a></td></tr><tr><td><h4><i class="fa-book" style="color:$primary;">:book:</i></h4></td><td><h4>Core concepts</h4></td><td>Reconciliation, the same-slot invariant, events vs. state, and history.</td><td><a href="/pages/FaSGGOl6CSP0t71WWh7l">/pages/FaSGGOl6CSP0t71WWh7l</a></td></tr><tr><td><h4><i class="fa-graduation-cap" style="color:$primary;">:graduation-cap:</i></h4></td><td><h4>Guides</h4></td><td>Deploy a team server, add safety gates, and scope memory per tenant.</td><td><a href="/pages/73b7faa18afc90c9ae3c6c1ae24f9ed214289c08">/pages/73b7faa18afc90c9ae3c6c1ae24f9ed214289c08</a></td></tr><tr><td><h4><i class="fa-book-open" style="color:$primary;">:book-open:</i></h4></td><td><h4>Reference</h4></td><td>Configuration, environment variables, and terminology.</td><td><a href="/pages/87935bb1e2caf4857fc5fe2347c566031b72ecaa">/pages/87935bb1e2caf4857fc5fe2347c566031b72ecaa</a></td></tr></tbody></table>


---

# 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://vayl.gitbook.io/vayl-docs/documentation/welcome-to-vayl.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.