Import Wizard
Import your AI programming conversations into Mantra and start Time Traveling.
Overview
The Import Wizard helps you import conversation logs from AI programming tools into Mantra, allowing you to review, search, and analyze these conversations.
Import Wizard Features
- Auto Detect Projects: Mantra automatically scans for AI tool projects on your computer.
- Incremental Import: Only imports new conversations, avoiding duplicates.
- Data Integrity: Preserves full conversation context and code snippets.
- Batch Operation: Supports importing multiple projects at once.
Supported AI Tools
| Tool | Version Req | Log Format | Status |
|---|---|---|---|
| Claude Code | 1.0.0+ | JSONL | ✅ Supported |
| Gemini CLI | 0.20.0+ | JSON | ✅ Supported |
| Cursor | 0.40.0+ | SQLite | ✅ Supported |
| Codex | 1.0.0+ | JSONL | ✅ Supported |
| GitHub Copilot Chat | latest | JSONL | ✅ Supported (v0.12.0+) |
| OpenCode | latest | SQLite | ✅ Supported (v0.12.0+) |
Tip
Claude Code is the most common import source, and most users start here.
General Import Flow
The import flow is consistent for all tools:
- Open Import Wizard - Click the "Import" button at the top of Mantra.
- Select AI Tool - Choose the tool type you want to import from.
- Select Project - Choose projects from the detected list.
- Wait for Completion - Import usually takes just a few seconds.
- Auto-linking (v0.7.0+) - After import, Mantra automatically guides you to link new sessions to existing Logical Projects based on Git Remote URLs or paths, enabling seamless multi-source aggregation.
Claude Code Import
About Claude Code
Claude Code is Anthropic's official AI programming CLI tool, offering powerful code assistance. It stores conversation logs in local project directories.
Version Requirements
- Minimum Version: 1.0.0
- Recommended: Latest stable
Check Version
Run claude --version to check your Claude Code version.
Log Location
Claude Code stores logs at:
~/.claude/projects/%USERPROFILE%\.claude/projects/~/.claude/projects/Directory Structure Example:
~/.claude/projects/
├── my-project-1/
│ ├── conversations/
│ │ ├── 2025-01-15_session1.jsonl
│ │ └── 2025-01-16_session2.jsonl
│ └── settings.json
└── my-project-2/
└── conversations/
└── 2025-01-17_session1.jsonlImport Steps
- Open Mantra, click Import button at the top.
- Select Claude Code as source.
Wait for Scan, Mantra auto-detects your Claude Code projects.
Select Projects, choose one or more.
- Click Import, wait for completion.
FAQ
Project not in list?
Possible Reasons:
Non-standard Path - Claude Code might be using a custom path.
- Solution: Add custom scan path in Settings.
No Conversations - New projects might not have logs yet.
- Solution: Have a conversation in Claude Code first, then rescan.
Permission Issues - Mantra might lack read permissions.
- Solution: Check directory permissions.
Conversation incomplete?
Possible Reasons:
Corrupted File - JSONL file might be malformed.
- Solution: Try re-importing or checking original file.
Version Compatibility - Older versions might differ.
- Solution: Upgrade Claude Code and retry.
Import slow?
Tips:
- Check conversation count; large projects take longer.
- Ensure disk read speed is normal.
- Close other disk-intensive apps.
Gemini CLI Import
About Gemini CLI
Gemini CLI is Google's command-line AI assistant, supporting code generation and Q&A.
Version Requirements
- Minimum Version: 0.20.0
- Recommended: Latest stable
Check Version
Run gemini --version to check your Gemini CLI version.
Log Location
Gemini CLI stores logs at:
~/.gemini/%USERPROFILE%\.gemini/~/.gemini/Directory Structure Example:
~/.gemini/
├── tmp/
│ └── <project_hash>/
│ ├── checkpoint_1.json
│ └── checkpoint_2.json
├── settings.json
└── history/
├── session_20250115.json
└── session_20250116.jsonImport Steps
Open Mantra, click Import button.
Select Gemini CLI as source.
Wait for Scan, Mantra auto-detects Gemini CLI logs.
Select Sessions, choose some or all.
Click Import, wait for completion.
FAQ
No Gemini CLI logs found?
Possible Reasons:
No Conversations - Gemini CLI creates directory only after first chat.
- Solution: Have a conversation in Gemini CLI first.
Custom Path - You might have changed default storage.
- Solution: Check Gemini CLI config.
Missing content?
Possible Reasons:
Abnormal Exit - Session might not have saved completely.
- Solution: Check JSON file integrity.
Incompatible Format - Older versions might not be supported.
- Solution: Upgrade Gemini CLI.
Cursor Import
About Cursor
Cursor is an AI-powered code editor based on VS Code.
Version Requirements
- Minimum Version: 0.40.0
- Recommended: Latest stable
Check Version
In Cursor, go to Help > About.
Log Location
Cursor stores logs in SQLite database:
~/Library/Application Support/Cursor/%APPDATA%\Cursor\~/.config/Cursor/Directory Structure Example:
~/Library/Application Support/Cursor/
├── User/
│ ├── workspaceStorage/
│ │ └── <workspace_id>/
│ │ └── state.vscdb
│ ├── globalStorage/
│ │ └── state.vscdb
│ └── settings.json
└── Cache/Note
Cursor uses SQLite. Please ensure Cursor is closed during import to avoid database lock issues.
Import Steps
Close Cursor (Recommended).
Open Mantra, click Import.
Select Cursor as source.
Wait for Parsing, Mantra reads SQLite DB.
Select Projects/Conversations.
Click Import.
FAQ
"Database Locked"?
Solution:
- Completely close Cursor (check system tray).
- Wait a few seconds and retry.
- Reboot if issue persists.
Cursor DB not found?
Possible Reasons:
Fresh Install - No logs yet.
- Solution: Use AI features in Cursor first.
Custom Install Location.
- Solution: Manually specify DB path in Settings.
Incorrect Project Association?
Note:
Cursor logs might span multiple projects. Mantra tries to identify context. You can manually adjust project association after import.
Codex Import
About Codex
Codex is OpenAI's command-line AI assistant.
Version Requirements
- Minimum Version: 0.75.0+
- Recommended: Latest stable
Check Version
Run codex --version.
Log Location
Codex stores logs at:
~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl/mnt/c/Users/{User}/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonlDirectory Structure Example:
~/.codex/
├── sessions/
│ └── 2025/
│ └── 01/
│ └── 15/
│ ├── rollout-1705312800000-abc123.jsonl
│ └── rollout-1705316400000-def456.jsonlTip
Codex organizes sessions by date. Each JSONL file is a session.
Import Steps
Open Mantra, click Import.
Select Codex as source.
Wait for Scan, Mantra auto-detects Codex logs.
Select Sessions.
Click Import.
FAQ
Codex logs not found?
Possible Reasons:
No Conversations - Directory created after first chat.
- Solution: Have a conversation first.
Custom Path.
- Solution: Check Codex config.
Windows non-WSL - Only WSL supported currently.
- Solution: Run Codex in WSL.
Incomplete logs?
Possible Reasons:
Corrupted File.
- Solution: Check JSONL integrity.
Interrupted Session.
- Solution: Normal behavior, Mantra recovers what it can.
Support reasoning models (o1/o3)?
Yes!
Mantra fully supports importing and displaying thinking processes from OpenAI reasoning models.
GitHub Copilot Chat Import
About GitHub Copilot Chat
GitHub Copilot Chat is GitHub's AI programming chat assistant, integrated into VSCode, JetBrains, and other major IDEs. It has 20M+ active users worldwide.
Version Requirements
- Recommended: Latest stable
- Supported IDEs: VSCode, VSCode Insiders, JetBrains IntelliJ, PyCharm, etc.
Log Location
GitHub Copilot Chat stores conversation logs in the IDE's extension storage directory:
~/Library/Application Support/Code/User/globalStorage/github.copilot-chat/~/.config/Code/User/globalStorage/github.copilot-chat/%APPDATA%\Code\User\globalStorage\github.copilot-chat\Multi-IDE Auto-Scan
Mantra automatically scans for Copilot Chat data across VSCode, VSCode Insiders, and JetBrains IDEs, and distinguishes sources via distribution subtitle chips (e.g., VSCode / JetBrains) in the Import Wizard.
Import Steps
Open Mantra, click the Import button.
Select GitHub Copilot Chat as source.
Wait for scan — Mantra auto-detects Copilot Chat sessions across IDEs.
Select projects, choose one or more.
Click Import, wait for completion.
FAQ
Multiple cards for the same tool?
This is expected.
If you use Copilot Chat in multiple IDEs (e.g., both VSCode and JetBrains), Mantra detects each separately and shows a distribution subtitle to distinguish them. Select the ones you want.
No Copilot Chat sessions found?
Possible Reasons:
Never used Chat — you may only have used code completion, not the Chat panel.
- Solution: Start a conversation in the IDE's Copilot Chat panel first.
Outdated version — older versions may not store exportable chat history.
- Solution: Update to the latest GitHub Copilot Chat extension.
OpenCode Import
About OpenCode
OpenCode is an open-source AI coding CLI developed by the SST team, distributed as both opencode and opencode-ai. It stores conversation logs in a SQLite database.
Version Requirements
- Recommended: Latest stable
- Database file:
opencode.db
Check Version
Run opencode --version to check your version.
Log Location
OpenCode stores logs in the following SQLite database:
~/Library/Application Support/opencode/opencode.db~/.local/share/opencode/opencode.db%APPDATA%\opencode\opencode.dbImport Steps
Open Mantra, click the Import button.
Select OpenCode as source.
Wait for parsing — Mantra reads
opencode.db.Select projects/sessions.
Click Import, wait for completion.
FAQ
Database not found?
Possible Reasons:
Never used OpenCode — the database is created only after the first session.
- Solution: Run a session in OpenCode first.
Custom data path — you may have set
$XDG_DATA_HOMEor another custom location.- Solution: Add the custom path in Mantra Settings.
Import slow?
Tips:
- Large SQLite databases take more time to parse.
- No need to close OpenCode — Mantra accesses the database read-only.
Advanced Config
Custom Log Paths
If your AI tools use non-default paths, you can add custom scan paths in Mantra settings:
- Open Settings (click gear icon or
Cmd/Ctrl + ,). - Select "Development" in the sidebar.
- Find the "Tool Configuration Paths" section.
- Click the "Add Path" button next to the corresponding tool (e.g., Claude Code).
- Select your custom log storage folder.
Once added, Mantra will immediately rescan for projects in that path.
Batch Import
To import multiple projects:
- Select multiple projects in the list.
- Or click "Select All".
- Click "Batch Import".
Tip
Batch import processes projects sequentially.
Troubleshooting
General Issues
| Issue | Possible Cause | Solution |
|---|---|---|
| No projects scanned | Tool unused | Use tool first |
| Import button disabled | No selection | Select at least one |
| Import interrupted | Disk full | Free up space |
| No conversations shown | Refresh delay | Restart or Refresh |
Tool Specific Issues
Claude Code:
- Check
~/.claude/projects/exists. - Check JSONL format.
- Check permissions.
Gemini CLI:
- Check
~/.gemini/exists. - Check JSON format.
- Update tool.
Cursor:
- Ensure Cursor closed.
- Check SQLite DB exists.
- Check DB integrity.
Codex:
- Check
~/.codex/sessions/exists. - Check JSONL format.
- Windows users check WSL.
GitHub Copilot Chat:
- Make sure you've used the Chat panel in your IDE (not just code completion).
- macOS: check
~/Library/Application Support/Code/User/globalStorage/github.copilot-chat/exists. - Multiple IDE users: seeing separate cards per IDE distribution is expected behavior.
OpenCode:
- Check
~/.local/share/opencode/opencode.db(Linux) or~/Library/Application Support/opencode/opencode.db(macOS) exists. - No need to close OpenCode; Mantra accesses the database read-only.
Get Help
If issues persist:
- Check FAQ.
- Search GitHub Issues.
- Join Discord Community.
- Submit new Issue with details.
