> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xysq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Connect your first AI tool, push a session into your context lake, see it in your vault, then correct a fact and watch the fix land.

You will go from a fresh account to a working, correctable memory in about ten minutes. This page is the generic path; the per-tool setup detail lives in the [connect guides](/connect/overview).

**Prerequisites:**

* An xysq account. Sign up at [app.xysq.ai](https://app.xysq.ai).
* One AI tool that speaks MCP. Claude, Claude Code, Cursor, ChatGPT, and Windsurf all work.

<Steps>
  <Step title="Connect your first AI tool">
    Pick your tool in the [connect guides](/connect/overview) and follow its steps. The in-app guide at [app.xysq.ai](https://app.xysq.ai) walks the same steps with your key and config pre-filled; the result is the same either way: the xysq MCP server is wired into your tool.

    Verify it worked: ask your tool "are you connected to xysq?". It should call `userinfo` and answer with something like "Connected. 0 items in memory staging."
  </Step>

  <Step title="Push your first context">
    Work in your tool normally for a bit, then say: "Save this session to xysq." The tool calls `push_context` with the transcript, and the call returns immediately. The engine does everything else server-side: extraction, deduplication, structuring, indexing.

    <Note>
      The transcript goes in **verbatim**, turn by turn, not summarized. Summarizing destroys the details the engine extracts from (exact numbers, names, file paths). The server decides what is durable, not the tool. Re-pushing identical content is safe; the server dedupes it.
    </Note>
  </Step>

  <Step title="See it in your vault">
    Open your vault at [app.xysq.ai](https://app.xysq.ai).

    * The **Sources** tab shows the raw push, stored byte for byte. This is immutable; nothing downstream can edit it.
    * The **Pages** tab shows the distilled pages the engine built from it. These appear within a few minutes of the push, and every fact on a page cites the source it came from.

    Retrieval is fresher than the pages: new content is searchable in seconds, and the readable pages catch up in minutes.
  </Step>

  <Step title="Pull it back in a new session">
    Start a fresh session, in the same tool or a different connected one, and ask about the topic: "What did we decide about the migration?" The tool calls `pull_context` with a plain-words query and gets ranked context back. One memory, every connected tool.
  </Step>

  <Step title="Correct something and watch it apply">
    Find a fact in your pages that is wrong or stale. Tell any connected tool the correction and have it push it, for example: "Correction for xysq: we deprecated the v2 endpoint in March, everything routes through v3 now."

    The engine treats this as superseding evidence. In one gated run it closes the old fact, updates every page that hosts it, and downweights the stale content in retrieval. Ask about it again: the next answer serves the corrected state. That is the loop the whole product is built on. Correct once, and it improves.

    Anything the engine cannot apply safely (an ambiguous edit, a conflict with something you wrote yourself) lands in your review queue instead of changing silently.
  </Step>
</Steps>

## Where next

<CardGroup cols={3}>
  <Card title="Connect guides" icon="plug" href="/connect/overview">
    Per-tool setup for Claude, Claude Code, Cursor, ChatGPT, Windsurf, and more.
  </Card>

  <Card title="Concepts" icon="lightbulb" href="/concepts/context-lake">
    The context lake, context graphs, and how the engine works underneath.
  </Card>

  <Card title="MCP reference" icon="code" href="/builders/mcp-tools">
    Exact parameters and responses for all four tools.
  </Card>
</CardGroup>