---
name: relvo-setup
description: Connect a user's agent to Relvo and install its workflow skills when asked to set up Relvo.
---

# Set up Relvo

Connect this agent to Relvo's tool catalog. This public guide contains no credentials; the browser sign-in grants access to the user's chosen project.

Console: https://app.relvo.si
API: https://api.relvo.si
MCP: https://app.relvo.si/mcp

## Reuse an existing connection

If Relvo's MCP tools are already connected, read the project and list available tools to verify access. If the Relvo CLI is configured, use the doctor command below. Do not create another connection or replace existing settings unnecessarily.

## Install on macOS or Linux

For Claude Code or Codex CLI, use Node.js 22 or later and run:

```sh
npx --yes --registry=https://registry.npmjs.org --@relvo:registry=https://registry.npmjs.org --package=@relvo/cli@0.1.21 relvo setup --api-url 'https://api.relvo.si' --console-url 'https://app.relvo.si'
```

The command detects installed Claude Code and Codex clients, connects MCP, and installs the six Relvo workflow skills. If the user requested only one client, append --client claude or --client codex. For CLI access alone, append --client terminal.

Keep setup running while the user opens the verification link it prints, signs in, checks the displayed code and client, chooses a project, and approves access. Let the user complete browser approval; never approve access on their behalf or ask them to paste an API key into chat. Every permission is selected by default, including execution, which spends the team's Relvo balance; the user can untick any of them before approving. Rerun the same command to resume an interrupted setup.

If npm cannot find the pinned package version, report that exact error and link to https://app.relvo.si/onboarding. Do not silently switch versions, registries, or products. Existing local files and other MCP servers must be preserved.

## Other clients and Windows

Open https://app.relvo.si/onboarding and choose the user's client for its current connection steps. The MCP endpoint is https://app.relvo.si/mcp. Automatic local skill installation above supports macOS/Linux and Claude Code/Codex CLI; other clients use the displayed MCP setup. Do not run the POSIX installer on Windows.

## Verify and hand back

After local setup completes, run:

```sh
npx --yes --registry=https://registry.npmjs.org --@relvo:registry=https://registry.npmjs.org --package=@relvo/cli@0.1.21 relvo doctor
npx --yes --registry=https://registry.npmjs.org --@relvo:registry=https://registry.npmjs.org --package=@relvo/cli@0.1.21 relvo skills list
```

Tell the user which client and project were configured, whether the skills were installed, and whether a restart is needed to load MCP. Use the connected agent to discover tools and inspect their current inputs and prices.

## Suggest a first task

Then suggest up to three tasks Relvo could do for the user now. Match what Relvo covers (the relvo guide in `skills list`) to what you already know about their work: this conversation, your memory and the loaded project instructions. Do not open other private files to learn more. For each, name the tools, the inputs you would send and the price. If you know too little, ask one question about their work instead. Run nothing until the user picks one. Use the CLI above while MCP waits for a restart.

Setup does not authorize paid tool execution: run paid work only for a task the user asks for, within any budget they set. The project's balance pays for it and platform_run quotes internally, so quote separately only when the user asks to approve a price. Never print or transmit saved credentials. The installed Relvo skills contain execution and recovery guidance; use them for subsequent work.