# Install kelve

> Ask your agent, or install it yourself. Every page of kelve's docs is listed at https://kelve.ai/llms.txt.

kelve runs on your computer, beside your agent. The quickest way to install it is to ask your agent.

## Ask your agent

Paste this to Claude Code, Codex or any agent that can run commands:

```ask
Install kelve from kelve.ai/install.sh
```

Your agent downloads the installer and runs it. The installer checks what it downloads against the release's checksums. Then it sets kelve up with `kelve setup`, which does three things:

- It connects your agent to kelve.
- It adds one hook to your agent's settings. With it, your agent picks up your notes, and lessons as it works. It also shows you its work in kelve as it hands it over. `kelve hook remove` takes the hook out.
- Your agent chooses how much kelve marks for you, from what it knows of you. It picks New, Learning, Working or Deep.

Most agents ask you before they run a command. Asking your agent to install kelve is your yes to the hook.

Then start a new session with your agent, so it has kelve's tools. From then on, your agent shows you its work when it's done. Or ask it:

```ask
Show me what you did in kelve.
```

## Install it yourself

If your agent can't run commands, run the installer in a terminal. It asks what it needs:

- Which agent to connect, if it finds more than one.
- Whether to add the hook.
- How well you know your work.

#### macOS and Linux

```sh
curl -fsSL https://kelve.ai/install.sh | sh
```

> It puts `kelve` in `~/.local/bin`, or in the folder `KELVE_INSTALL_DIR` names.

#### Windows

```powershell
irm https://kelve.ai/install.ps1 | iex
```

> It puts `kelve.exe` in `%LOCALAPPDATA%\kelve\bin`, and adds that folder to your PATH.

#### From source

```sh
git clone https://github.com/kelve-ai/kelve
cd kelve/web && bun install && bun run build && cd ..
cargo install --path crates/cli --locked
```

> You need Rust and Bun. Then run `kelve setup`.

If the folder kelve went in isn't on your PATH, the installer says so. Add it, then open a new terminal.

If the installer can't connect your agent, it says the line to run. [Connect your agent](/docs/connect/) has the line for each one.

## The first time you open kelve

Ask your agent to show you something. kelve opens in a new browser tab and shows what it set up. You see your agent connected, the hook, and how much kelve marks, each with a word to change it. kelve asks two things, once:

- Whether to share anonymous counts of how you use kelve. They're numbers only, once a week, and never your work.
- Whether to join the shared graph. Choose **Sign in with GitHub** or **Sign in with Google**, or **Use kelve without it**. Signing in is agreeing to its [terms](/docs/terms/).

Then open what your agent opened, and you're reading.

## Check it works

1. Ask your agent: "Show me this folder in kelve." kelve opens in a new browser tab and starts reading the folder.
2. Or run `kelve status`. It says whether kelve is running, and where. kelve starts by itself the first time your agent opens something.

> **If `kelve` isn't found,** open a new terminal. If it still isn't, add the folder the installer named to your PATH.

## Update kelve

Run `kelve update`, or ask your agent to update kelve. When a newer kelve is out, **Settings**, **Your agent** says so, and your agent is told once. [Update and uninstall](/docs/update-uninstall/) says more.
