---
title: "Install Overlane in an agent"
description: "Connect Claude Code and Codex with overlane connect, and add Grok Build, Cursor, Gemini CLI or a cloud session with overlane client install."
---

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

# Install Overlane in an agent

Every client signs in with its own screen. Overlane never asks for a subscription token or a vendor key, and the install commands write none.

## Claude Code and Codex

These two have a plugin. [`overlane connect`](/cli/connect/) registers it with each agent it finds, signs you in, and binds the project. Preview first with `--dry-run`.

```sh
overlane connect --dry-run
overlane connect --yes
```

## Other clients

Add Cursor or Gemini CLI with the commands below.

[`overlane client install`](/cli/client-install/) writes the few project files a client reads: instructions and a remote MCP entry. It is safe to repeat, changes only what it owns, keeps your other settings, and writes no credential. Sign in happens in the client.

| Client | Command |
| --- | --- |
| Grok Build | `overlane client install grok` |
| Cursor | `overlane client install cursor` |
| Gemini CLI | `overlane client install gemini` |
| Claude cloud session | `overlane client install claude --surface cloud` |
| Codex cloud session | `overlane client install codex --surface cloud` |

Use `--surface cloud` for Cursor's cloud agent file too. The Claude cloud recipe commits every hook and skill of the plugin, because cloud sessions do not install plugins; it reads them from the plugin that ships with the CLI, or from `--marketplace-root`. Install the CLI in the cloud environment's setup script, and each session signs in and connects on its own. A Claude project's cloud threads never run a repository's hooks: package the plugin with `overlane client package claude`, upload it on claude.ai and add it to the project. See [Set up Claude Code cloud, Claude projects and Codex cloud](/getting-started/cloud-agents/).

Every capability a client lacks is labelled **advisory** or **unavailable** by the compatibility suite, so an agent can tell which rules are enforced for it and which only warn.

```sh
overlane client install cursor --dry-run
```

After installing, run [`overlane doctor`](/cli/doctor/) to see one readiness state per agent and the next repair command.

Background bots such as ChatGPT Dots and Grok Bot connect differently: see [Bots](/bots/).

Source: https://docs.overlane.app/client-install/index.mdx