Claude Codex Memory Sync banner
DaizeDong DaizeDong

Claude Codex Memory Sync

Development community

Description

Lightweight local one-way memory sync from Claude Code to Codex for Windows PowerShell 5.1.

Installation

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

README

Claude Code → Codex Memory Sync

Convert Claude Code project auto-memory into local Codex `ad_hoc` staging notes with one PowerShell command.

[![Test](https://github.com/DaizeDong/claude-codex-memory-sync/actions/workflows/test.yml/badge.svg)](https://github.com/DaizeDong/claude-codex-memory-sync/actions/workflows/test.yml) [![PowerShell 5.1](https://img.shields.io/badge/Windows%20PowerShell-5.1-5391FE?logo=powershell&logoColor=white)](sync-claude-memory-to-codex.ps1) [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE) [![Languages](https://img.shields.io/badge/Languages-EN%20%2F%20CN-blue?style=flat)](#languages)

[English](README.md) | [中文版](README_CN.md)

This is an independent community project. It is not affiliated with or endorsed by Anthropic or OpenAI.

⭐ Read this first: the design philosophy

**Stage verifiable memory updates; never pretend the two agents share a brain.**

This tool is intentionally small. Its design follows three principles:

  1. Fill the seam, do not add another agent surface. Claude Code already stores project memory, and Codex already owns its memory consolidation. This tool only converts one representation into the format accepted by the detected local ingress contract. It adds no agent terminal, daemon, MCP server, database, vector store, or model call.
  2. Stage through the detected local contract, do not impersonate Codex internals. The script appends self-contained notes under extensions\ad_hoc\notes\. It never rewrites Codex memory summaries, rollout evidence, or SQLite state. A successful sync means “safely staged,” not “already consolidated or guaranteed to be recalled.”
  3. Memory quality matters more than memory volume. Dry-run first, select conservatively, fail closed on likely credentials, bound every input, and deduplicate incrementally. Copying every log and stale decision would make the pool larger while potentially making recall worse.

The design target is the smallest audit