ahmojo

Codex Claude Transfer — Development skill for Claude Code

Development community

Local-first CLI (cct) that moves Codex & Claude Code sessions between machines: export to a .codexbundle, copy, import.

How to install Codex Claude Transfer

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ahmojo/codex-claude-transfer and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Codex Claude Transfer does

Local-first CLI (cct) that moves Codex & Claude Code sessions between machines: export to a .codexbundle, copy, import. No cloud, no account, optional LAN sync.

Alternatives in Development

  • LifeOS — ⛰️ The Life Operating System — an intent engineering platform that moves you from your current state to your i 18.7k ★
  • /write PRD — Generate a PRD that moves smoothly from strategy to delivery 2.3k ★
  • Dotenv Vault — Sync environment variables across machines for consistent Claude Code behavior 1.2k ★

README

codex-claude-transfer

**Move local Codex and Claude Code sessions between machines.** The command is **`cct`**.

![CI](https://github.com/ahmojo/codex-claude-transfer/actions/workflows/ci.yml/badge.svg) ![Go](https://img.shields.io/badge/Go-1.23%2B-00ADD8?logo=go) ![License](https://img.shields.io/badge/license-MIT-blue) ![Status](https://img.shields.io/badge/status-v2.1.1-blue)

**Unofficial.** Not affiliated with or endorsed by OpenAI or Anthropic. These tools' internals can change at any time and break this tool. Use at your own risk. See the [Disclaimer](#disclaimer).

The problem it solves

Codex and Claude Code keep valuable project context in local session files. That is good for privacy, but painful when you switch machines, rebuild a laptop, or want to continue a thread in the other agent.

`cct` turns that local context into a simple handoff:

Machine A:  cct export --project .      ->  project.codexbundle
                        copy it however you trust
Machine B:  cct import ./project.codexbundle

No cloud account, hosted sync service, or background process by default. You move one `.codexbundle` over a channel you trust, then import it after checksum verification. The agents' indexes are left alone and re-scan the session files themselves.

It works for Codex, Claude Code, and cross-agent handoff. The same flow is available as a CLI, a terminal wizard (`cct ui`), and a local browser app (`cct app`).

Demo

Export on one machine, then import or incrementally sync onto the other:

![Overview: doctor, grouped list, export](demo/clips/01-overview.gif)

![Incremental sync with import --merge](demo/clips/02-sync.gif)

The optional local desktop UI uses the same engine:

![The cct desktop WebUI](demo/clips/10-webui.gif)

More clips in [`demo/`](demo/): [LAN sync](demo/clips/15-sync.gif), [full-text search](demo/clips/11-search.gif), [secret scan & redact](demo/clips/12-secrets.gif), [Markdown export](demo/clips/13-markdown.gif), [re