# Codex Memory Sync

> Use when the user says "Sync the current project memory", or when a long-running project changes phase, grows in context, or is about to end a thread.

- **Type:** Skill
- **Install:** `agentstack add skill-akin-lvyifang-codex-memory-lite-codex-memory-sync`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [AKin-lvyifang](https://agentstack.voostack.com/s/akin-lvyifang)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [AKin-lvyifang](https://github.com/AKin-lvyifang)
- **Source:** https://github.com/AKin-lvyifang/codex-memory-lite/tree/main/skills/codex-memory-sync

## Install

```sh
agentstack add skill-akin-lvyifang-codex-memory-lite-codex-memory-sync
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Codex Memory Sync

When a task runs long, changes phase, approaches the end of a thread, or becomes context-heavy, sync the effective information from the session back into the **project-local `.codex-memory/`**.

**Important**: Always use the project-local `.codex-memory/` (for example, `{PROJECT_ROOT}/.codex-memory/`), not the global `~/.codex-memory/`.

## Pre-Write Checks

Before any read, create, or write action, first define an absolute path variable: `PROJECT_ROOT`.

- `PROJECT_ROOT` must be the project root for the current session
- Do not treat `~`, `/`, `~/.config/opencode`, `~/.codex`, a skills directory, or a config directory as the project root
- If the current directory looks like a home directory or a config directory, or if the project root is still unclear, stop and confirm it first
- All memory paths must be written as absolute paths: `{PROJECT_ROOT}/.codex-memory/...`
- Do not treat the bare relative path `.codex-memory/...` as the final write target

## When To Use

Use this when any of the following is true:
- The user explicitly says "Sync the current project memory"
- A phase of work just finished
- The task changed direction
- The current thread is about to end
- Context has clearly grown large
- The user explicitly asks to update `current`, write `archive`, or promote a rule

## Natural Trigger Phrases

- Sync the current project memory

## Goal

Route information from the current session into the correct destination:
- current effective state -> `current.md`
- long-lived stable rules -> `spec/`
- active task context -> `tasks/active//`
- historical process -> `archive/`

## Workflow

1. Read:
   - `.codex-memory/current.md`
   - `.codex-memory/spec/index.md`
   - if an active task exists, also read its `brief.md`
2. Extract information from the current session and classify it with the following rules:

### A. current
Only write information to `current.md` if it is still currently effective:
- current goal
- scope / not doing
- current status
- stable constraints summary
- key index
- risks / next steps

### B. spec
Promote a rule to `spec/` if any of the following is true:
- it stays valid across more than two sessions
- it appears repeatedly in more than one topic
- losing it would create obvious rework

### C. tasks
If the current work belongs to an active task, sync:
- `brief.md`
- `decisions.md`
- `refs.md`

### D. archive
Write this round's process notes, old goals, one-off tweaks, and historical decisions into the monthly archive file

3. Update rules:
- `current.md` must be overwritten by section, not extended into a dated running log
- historical information goes into `archive/`, not back into `current.md`
- active tasks should keep only information that is still ongoing
- do not dump every node ID into `current`; keep only the key few
- if the target path is not `{PROJECT_ROOT}/.codex-memory/`, stop immediately and do not keep writing

## Report Back

After sync finishes, report:
- the `PROJECT_ROOT` used this time
- updated files
- what went into `current`
- what went into `archive`
- which rules were promoted into `spec`
- whether any conflicts or pending confirmations were found

## Constraints

- Do not delete old archive records on your own
- Do not mix "current state" and "historical process" back together
- Do not create task directories unless they are actually needed
- Do not create any `.codex-memory/` directories or files before `PROJECT_ROOT` is confirmed

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [AKin-lvyifang](https://github.com/AKin-lvyifang)
- **Source:** [AKin-lvyifang/codex-memory-lite](https://github.com/AKin-lvyifang/codex-memory-lite)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-akin-lvyifang-codex-memory-lite-codex-memory-sync
- Seller: https://agentstack.voostack.com/s/akin-lvyifang
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.