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

# Quickstart

> Install /vibe and send one real message.

## 1. Install

Run this in a terminal:

```sh theme={null}
npx slashvibe-mcp
```

The installer opens GitHub sign-in and configures Claude Code, Codex, and Cursor when they
are present. Your GitHub username becomes your initial `/vibe` handle.

## 2. Restart your coding host

Restart Claude Code, Codex, or Cursor so it loads the new MCP server.

## 3. Send one real message

Inside the coding session, ask naturally or use the direct form:

```text theme={null}
vibe dm @handle <your question>
```

Start with someone you already know. `/vibe` intentionally has no public people directory.

## Claude Code: show waiting messages at session start

```sh theme={null}
npx slashvibe-mcp hook install
```

Restart Claude Code after installing the hook. Waiting messages can then appear at the top
of a later session.

<Note>
  The pilot hook is read-only. It does not mark a message delivered or read, so the same
  waiting message may appear again.
</Note>

## Check the setup

For Claude Code, inspect the configured server:

```sh theme={null}
claude mcp get vibe
```

The command should resolve to `npx -y slashvibe-mcp@latest`.

If you installed the optional hook, check it separately:

```sh theme={null}
npx slashvibe-mcp hook status
```

Inside the coding host, ask `/vibe` who is around or check your inbox. Signed-out, offline,
and empty states should say so; they should not invent presence or delivery.

## Returning from an older Claude Code install

Older installs can leave `vibe` pinned to an earlier package. The installer currently keeps
an existing MCP entry instead of replacing it, so check from the project directory where
you plan to use `/vibe`:

```sh theme={null}
claude mcp get vibe
```

If it names a pinned version, run the exact scope-specific `claude mcp remove` command that
Claude prints. Check again because `vibe` can exist in more than one scope. Remove only the
named `vibe` entry until `claude mcp get vibe` reports that it is missing, then run:

```sh theme={null}
npx slashvibe-mcp
claude mcp get vibe
```

Confirm that the new entry uses `slashvibe-mcp@latest`, then restart Claude Code. A stale
project-local entry can override a current user entry, so trust the scope reported by
`claude mcp get vibe` rather than editing configuration JSON by hand.

## Need the Mac companion?

Vibe Buddy is optional. Install it after terminal messaging works if you want a quiet,
persistent view of people, messages, and local coding sessions. See [Vibe Buddy](/buddy).