---
title: "Import from another tool"
description: "Bring your Claude Code, Codex, or OpenCode history, skills, and MCP servers into Hoplite."
canonical_url: "https://hoplite.sh/docs/import"
markdown_url: "https://hoplite.sh/docs/import.md"
---

# Import from another tool
URL: /docs/import
LLM index: /llms.txt
Description: Bring your Claude Code, Codex, or OpenCode history, skills, and MCP servers into Hoplite.
Related: /docs/cli, /docs/cli/handoff, /docs/agent/mcp

# Import from another tool

If you've been working locally with **Claude Code**, **Codex**, or **OpenCode**, the Hoplite CLI imports your session history, your personal skills, and (optionally, with your explicit confirmation) your MCP server credentials. One command covers all of it: `hoplite onboard`.

To hand over the session you're actively working in — not just history — see [Handoff](/docs/cli/handoff) instead.

## Install the CLI and run onboard

On macOS or Linux, the native installer downloads a versioned release archive, verifies its SHA-256 checksum, and installs to `~/.local/bin` without modifying your shell configuration:

```bash title="terminal"
curl -fsSL https://hoplite.sh/install.sh | sh
$HOME/.local/bin/hoplite onboard
```

`onboard` scans your machine for local session history from the supported tools, shows what it found, and imports it — so your past context comes with you. You can run it during onboarding or any time later. For Windows, package-manager installs, and the full command reference, see [CLI](/docs/cli).

## Import personal global skills

Skills you installed locally with `npx skills add ... --global` can join your personal Hoplite library. The initial `hoplite onboard` run presents them as a default-selected step before the final confirmation, or you can import selectively later:

```bash title="terminal"
hoplite skills import-global --name <skill-name>
```

Use `--all --yes` for an explicit bulk import, or `--replace` to overwrite a same-named personal skill. Every import reads only the root `SKILL.md` instructions.

Personal skills apply only to projects you start, never to automations. When a personal skill and a repository skill share a name, the repository skill wins.

## Import MCP servers and their credentials

Importing your MCP servers copies **server addresses only** — auth headers and OAuth tokens stay on your machine, and those servers arrive disabled and marked **needs credentials**.

If you'd rather have agents use those servers straight away, `hoplite onboard` offers a separate step — **"Import auth state into Hoplite?"** — listing each server whose API key or OAuth tokens it found locally. Nothing there is selected by default, and nothing is uploaded until you confirm the import.

Selected credentials are encrypted with AWS KMS before storage, never returned by the API, and decrypted only when a run connects. Note that an imported token grants Hoplite's agents the same access it granted your local tools. See [MCP servers](/docs/agent/mcp) for the full encryption model.

<Callout type="info" title="Codex OAuth">
Codex stores its per-server OAuth tokens in a way that would raise a macOS permission prompt to read, so the CLI does not read them. Codex API-key headers are offered as usual; for Codex OAuth servers, add credentials in **Settings → MCP servers** instead.
</Callout>

## Undo an import

Changed your mind? One command reverses it:

```bash title="terminal"
hoplite undo
```

This removes what a previous `onboard` run imported.

## Next steps

- [Handoff](/docs/cli/handoff) — continue a live local session as a cloud thread
- [CLI](/docs/cli) — every command, install option, and flag
- [Make your repo agent-ready](/docs/agent-ready) — set up the project the way your imported context deserves

## Sitemap

See the full [sitemap](/docs/sitemap.md) for all pages.
Well-known sitemap: [/docs/.well-known/sitemap.md](/docs/.well-known/sitemap.md).