Bring your agent setup with you
One command, hoplite onboard, finds the skills, MCP servers and session history you use with Claude Code, Codex, OpenCode or Cursor, shows you what it found and imports what you pick. Your credentials stay on your machine unless you choose otherwise.
What does importing your setup mean?
Importing your setup means a cloud coding agent starts with the workflows and connections you already rely on locally, instead of you rebuilding them by hand in a new tool.
In Hoplite, the CLI's onboard command scans your machine for local history, personal skills and MCP server configuration, lets you choose what to bring, and imports it into your workspace. Past sessions arrive as threads, skills join your personal library, and MCP servers arrive with their addresses, waiting for credentials where they need them.
One scan across the tools you use
hoplite onboard looks for Claude Code, Codex, OpenCode and Cursor history on your machine and lists it by project. Only repositories the Hoplite GitHub App can reach are offered, and project MCP servers attach to a project only when the folder's Git remote verifies the repository. Run hoplite update later to bring in new sessions.
Your skills, in your personal library
Skills you installed globally, for example with npx skills add --global, show up as a default-selected step, or import them one at a time with hoplite skills import-global. Each import reads only the root SKILL.md. Personal skills apply to runs you start, and a repository skill with the same name wins.
MCP servers arrive, secrets stay home
By default only server addresses are imported. Servers that need auth arrive disabled and marked needs credentials. A separate step offers to import API keys and OAuth tokens; nothing is selected by default, and anything you do import is encrypted with AWS KMS, never returned by the API, and decrypted only when a run connects.
Changed your mind? Undo it
hoplite undo removes what your most recent import into the workspace added. Hoplite records which import that was, so undo works from any machine and however you signed in. Personal items you changed after importing are kept. Only the latest import can be undone.
Copying config by hand vs. hoplite onboard
| Question | Copying config by hand | hoplite onboard |
|---|---|---|
| Finding what you have | Dotfiles in each tool's own folder | One scan across Claude Code, Codex, OpenCode and Cursor |
| Skills | Copied into every repository | Imported into your personal library |
| MCP servers | Re-entered one URL at a time | Server addresses imported in one step |
| Credentials | Pasted into another tool | Stay local unless you opt in, then encrypted with AWS KMS |
| Past sessions | Left on your laptop | Imported as threads, with hoplite update for new ones |
| Taking it back | Delete it all by hand | hoplite undo |
Importing, answered
- Which tools can I import from?
- Claude Code, Codex, OpenCode and Cursor. hoplite onboard scans your machine for their local session history, personal skills and MCP server configuration, and imports what you select.
- Are my API keys and OAuth tokens uploaded?
- Not unless you choose to. MCP imports copy server addresses only by default. A separate, explicitly labelled step offers to import auth state, with nothing selected. Codex OAuth tokens aren't read at all; add those credentials in the app instead.
- Who can use the skills I import?
- Imported skills go into your personal library and apply to runs you start, not to automations or Linear-delegated runs. For workflows the whole team needs, owners and admins can add organization skills.
- What if a skill has the same name as one in the repository?
- The repository skill wins. When skills share a name, Hoplite picks project skills first, then organization, then personal, then built-in.
- Do my local stdio MCP servers work in the cloud?
- Hosted runs connect to remote HTTP and SSE servers and exclude stdio servers from the tool catalog. To use a local server from one cloud thread, run hoplite mcp connect on macOS or Linux and keep it running while the thread uses it.
- What about my Cursor rules?
- Onboarding imports local user rules from ~/.cursor/rules. Account-level user rules aren't in profile exports, so copy them to a text file and pass it with --cursor-user-rules-file. Committed rules stay with the repository.
Start where you left off
Install the CLI, run hoplite onboard and pick what to bring. Start on Free.