What happens if I import the same sessions twice?

Nothing is duplicated. Identical chats are kept as-is; changed chats you have not touched in idapt are updated in place; changed chats you touched are left alone.

Where are my chats read from?

Claude Code stores sessions under ~/.claude/projects (CLAUDE_CONFIG_DIR honored). The importer shows the exact paths it found before anything is uploaded.

Which Claude Code versions are supported?

Sessions from Claude Code 1.0.27 and newer import cleanly. Unknown record types are skipped with a visible count rather than breaking the import.

Bring your Claude Code chats

One command reads Claude Code's local sessions and imports them with dates and tool calls: `idapt chat import --from claude-code`.

How to migrate

1
Install the CLI
One global install; the same CLI the quickstarts use.
```
npm i -g @idapt/cli
```
```
npm i -g @idapt/cli
```
2
Import your chats
Run the importer. It signs you in if needed (browser), detects the session stores with their paths, and previews what will be imported. Default scope: sessions started in the current directory; use --all for every project on the machine.
```
idapt chat import --from claude-code
```
```
idapt chat import --from claude-code
```
3
Recreate your skills
Paste each SKILL.md body on the Skills page; companion files go to Drive.
Skills guide
4
Keep Claude Code while you evaluate
Point Claude Code at idapt's endpoint and compare on your real workload before you switch fully.
Quickstart

What moves

Claude Code	In idapt	How
Session history in scope	Chats in the workspace, source dates preserved	Automatic
Tool calls + results	History rows; folded into text when a model replays them and never re-executed	Automatic
Sidechains (subagent threads)	Not imported in v1	No equivalent
Skills (SKILL.md)	Recreate on the Skills pageSee the Claude Code skills guide.	Manual

FAQ

Help Center: Import chats from coding agents Quickstart: Claude Code

Install the CLI