EvoX Docs
  • Product
  • Pricing
  • Docs
  • Marketplace
Back to EvoMap
Log InSign Up
Overview
Get startedUse EvoXImport experience
Practice cases
Features
Configuration
Developers
Security
Administration
Overview
Get startedUse EvoXImport experience
Practice cases
Features
Configuration
Developers
Security
Administration
EvoX docs/Introduction/Import experience

Import experience

Bring past conversations, agent connections, and reusable skills into EvoX.

EvoX provides separate flows for copying conversation history, connecting other local agents, and adding reusable skills. Each flow lets you select and review what changes instead of treating everything as one migration.

Import past conversations

Choose past conversations from Claude Code, Codex, Cursor, or Gemini CLI and add copies to EvoX. Import during onboarding or from Settings → My agents → Bring in past conversations. Originals stay unchanged.

EvoX

Bring your conversations into EvoX

Select conversations and review them before importing.

Selected 0 / 4

Interactive sample. No local data is read; original conversations are unchanged.

Grouped by source and project

Scan results are organized by tool and project.

Only what you select

Nothing is selected by default. Select sessions, projects, or sources.

Review every result

Results distinguish imported, existing, and failed items, with retries.

Imported history first becomes EvoX conversations. It enters long-term memory only when you explicitly choose to save it. Task-package handoff is a separate, default-off flow: its export and import entries require a pre-release build with the task-handoff experimental switch, session import, and task transfer enabled. The recipient imports an independent copy with new identities; importing does not execute historical actions or inherit source approvals. Check continuation prerequisites before starting work.

Connect other agents

Connecting is different from copying conversations. Claude Code and Codex can use EvoX tools in the selected project, while Cursor can read knowledge learned by EvoX. EvoX recognizes Kiro and opencode environments but does not write connection configuration for them.

Settings · My agents
Appearance
Personalization
Connections
My agents

Current project

Most agents read project settings, so this connection applies only to the selected folder.

Example project / sample-project

Connect your agents

Tool access enables EvoX tools; experience access provides saved experience through rule files.

Claude Code

Tool access

Connected to this folder

Codex

Tool access

Available

Cursor

Experience access

Available

Unsupported tools · 2

EvoX recognizes these runtimes but does not write connection settings for them yet.

KiroUnsupported
opencodeUnsupported
Advanced · All projects for this user

Claude Code only: load EvoX in every project for the current system user. Manage this separately from the current project connection above.

Claude Code — this OS user

All-project connection disabled

Interactive demo · The project path is an example. Connections do not change local configuration.

Import reusable skills

From the Skills library, choose Add, then Scan local, Import, or GitHub sync. The Import dialog accepts either a ZIP file or public ZIP URL and shows names, files, powerful-access checks, and conflict handling before installation.

EvoX

Create skill also appears in the Add menu; this mock focuses on the three import paths.

Import

Review and install skills from a ZIP file or public ZIP URL.

Drop a skill ZIP here

You can also paste a ZIP file or public URL.

One archive supports multiple skills, up to 64 MB.

Review before and after importing

  • Confirm the selected sources, projects, and conversations.
  • Review skill files, readable contents, name conflicts, and powerful permissions.
  • Check imported, existing, failed, and unresolved result items.
  • Review plugin authorization and connection permissions separately. Before sharing a task package, review included full conversations, other tasks, files, and omissions. Packages are unencrypted and cannot be recalled after sharing; images and binary files are not guaranteed to be scrubbed of sensitive data.
PreviousUse EvoXNextAvailable on