How do I install the Banana Claude Codex Import skill?

Run npx skillmds@latest add treydong/banana-claude-codex-import in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Banana Claude Codex Import safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Banana Claude Codex Import?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Banana Claude Codex Import free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Banana Claude Codex Import?

treydong (@treydong) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Banana Claude Codex Import by treydong

Name: Banana Claude Codex Import
Author: treydong

Banana Claude Codex Import

Import local Claude Code or Codex conversation history into OpenClaw memory. Triggers when: user asks to "导入"Claude/Codex conversations or chat logs, migrate or consolidate past coding agent sessions, load previous Claude Code or Codex work into memory, analyze or review past coding sessions, or rebuild memory from local coding agent session files. Also triggers proactively when ~/.claude/projects/ or ~/.codex/sessions/ directories are detected. Does NOT trigger for: ChatGPT/Claude web app exports (→ banana-chatgpt-import).

treydong Updated Sep 17, 2026

File contents

banana-claude-codex-import

Import local Claude Code (~/.claude/) and Codex (~/.codex/) conversation history into OpenClaw's memory system, making past coding work queryable and part of long-term memory.

When to use this skill

Use this skill when the user:

Wants to import, migrate, or consolidate Claude Code or Codex sessions
Asks to "导入" or "migrate" past coding agent conversations
Wants to make past Claude Code / Codex work searchable in memory
Needs to rebuild memory from previous coding agent sessions
Mentions ~/.claude/ or ~/.codex/ session files
Is reviewing past work and wants to extract key decisions/patterns into memory

What this skill does

Detect whether Claude Code and/or Codex data exists locally
Preview with --dry-run to show session count, date range, and sample content
Import all sessions to logs/message-archive-raw/
Generate memory candidates for distillation into MEMORY.md

Workflow

Step 1: Dry-run first

Always run with --dry-run first to verify data coverage:

python3 ~/.openclaw/skills/banana-claude-codex-import/scripts/import_conversations.py --dry-run

Check:

Session count (aim for 50+ for Claude Code, 50+ for Codex)
Date range
Whether content looks real (not just noise/environment context)

If results look good, proceed.

Step 2: Full import

python3 ~/.openclaw/skills/banana-claude-codex-import/scripts/import_conversations.py

This writes:

Session archives → logs/message-archive-raw/{claude_code,codex}/
Memory draft → memory/YYYY-MM-DD_import_candidates.md

Step 3: Distill into MEMORY.md

Read memory/YYYY-MM-DD_import_candidates.md and extract high-value content into MEMORY.md:

## Claude Code / Codex 导入记忆（YYYY-MM）

> N sessions imported from `logs/message-archive-raw/`

### 技术决策
- [key decision 1]
- [key decision 2]

### 项目 / 主题
- [project 1]: [what was done]
- [project 2]: [what was done]

### 工具 & 工作流
- [tool/workflow pattern observed across sessions]

Source data

Source	Path	Format
Claude Code sessions	`~/.claude/projects/*.jsonl`	JSONL, user/assistant/tool_result entries
Claude Code index	`~/.claude/history.jsonl`	sessionId → metadata
Codex sessions	`~/.codex/sessions/*/rollout-.jsonl`	JSONL, session_meta/response_item entries

CLI options

--dry-run              # Preview only, no files written
--source both          # Import both Claude Code and Codex (default)
--source claude_code   # Claude Code only
--source codex         # Codex only
--since YYYY-MM-DD     # Only sessions on or after date

What makes a good memory distillation

After import, the most valuable things to capture in MEMORY.md:

Technical decisions — architecture choices, tools selected/rejected, what failed
Recurring workflows — patterns in how the user works with coding agents
Project context — what each project is about, key milestones
Personal preferences — working style, communication patterns, explicit preferences stated

Avoid: verbatim copying of conversations. Capture the distilled meaning.

---name: banana-claude-codex-importdescription: Import local Claude Code or Codex conversation history into OpenClaw memory. Triggers when: user asks to "导入"Claude/Codex conversations or chat logs, migrate or consolidate past coding agent sessions, load previous Claude Code or Codex work into memory, analyze or review past coding sessions, or rebuild memory from local coding agent session files. Also triggers proactively when ~/.claude/projects/ or ~/.codex/sessions/ directories are detected. Does NOT trigger for: ChatGPT/Claude web app exports (→ banana-chatgpt-import).---# banana-claude-codex-importImport local Claude Code (`~/.claude/`) and Codex (`~/.codex/`) conversation history into OpenClaw's memory system, making past coding work queryable and part of long-term memory.## When to use this skillUse this skill when the user:- Wants to import, migrate, or consolidate Claude Code or Codex sessions- Asks to "导入" or "migrate" past coding agent conversations- Wants to make past Claude Code / Codex work searchable in memory- Needs to rebuild memory from previous coding agent sessions- Mentions `~/.claude/` or `~/.codex/` session files- Is reviewing past work and wants to extract key decisions/patterns into memory## What this skill does1. **Detect** whether Claude Code and/or Codex data exists locally2. **Preview** with `--dry-run` to show session count, date range, and sample content3. **Import** all sessions to `logs/message-archive-raw/`4. **Generate** memory candidates for distillation into `MEMORY.md`## Workflow### Step 1: Dry-run firstAlways run with `--dry-run` first to verify data coverage:```bashpython3 ~/.openclaw/skills/banana-claude-codex-import/scripts/import_conversations.py --dry-run```Check:- Session count (aim for 50+ for Claude Code, 50+ for Codex)- Date range- Whether content looks real (not just noise/environment context)If results look good, proceed.### Step 2: Full import```bashpython3 ~/.openclaw/skills/banana-claude-codex-import/scripts/import_conversations.py```This writes:- Session archives → `logs/message-archive-raw/{claude_code,codex}/`- Memory draft → `memory/YYYY-MM-DD_import_candidates.md`### Step 3: Distill into MEMORY.mdRead `memory/YYYY-MM-DD_import_candidates.md` and extract high-value content into `MEMORY.md`:```markdown## Claude Code / Codex 导入记忆（YYYY-MM）> N sessions imported from `logs/message-archive-raw/`### 技术决策- [key decision 1]- [key decision 2]### 项目 / 主题- [project 1]: [what was done]- [project 2]: [what was done]### 工具 & 工作流- [tool/workflow pattern observed across sessions]```## Source data| Source | Path | Format ||--------|------|--------|| Claude Code sessions | `~/.claude/projects/*.jsonl` | JSONL, user/assistant/tool_result entries || Claude Code index | `~/.claude/history.jsonl` | sessionId → metadata || Codex sessions | `~/.codex/sessions/**/rollout-*.jsonl` | JSONL, session_meta/response_item entries |## CLI options```bash--dry-run # Preview only, no files written--source both # Import both Claude Code and Codex (default)--source claude_code # Claude Code only--source codex # Codex only--since YYYY-MM-DD # Only sessions on or after date```## What makes a good memory distillationAfter import, the most valuable things to capture in `MEMORY.md`:1. **Technical decisions** — architecture choices, tools selected/rejected, what failed2. **Recurring workflows** — patterns in how the user works with coding agents3. **Project context** — what each project is about, key milestones4. **Personal preferences** — working style, communication patterns, explicit preferences statedAvoid: verbatim copying of conversations. Capture the distilled meaning.

Frequently asked questions