Metadata-Version: 2.4
Name: codex-move-session
Version: 0.1.0
Summary: Repair local Codex sessions after moving a project directory
Keywords: codex,migration,sessions,uvx
Author: zz
Author-email: zz <zanderzhng@gmail.com>
License-Expression: MIT
License-File: LICENSE
Classifier: Development Status :: 3 - Alpha
Classifier: Environment :: Console
Classifier: Operating System :: MacOS
Classifier: Operating System :: Microsoft :: Windows
Classifier: Operating System :: POSIX :: Linux
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: 3.14
Classifier: Topic :: Utilities
Requires-Dist: psutil>=6.0
Requires-Dist: questionary>=2.1
Requires-Dist: rich>=13.9
Requires-Python: >=3.10
Project-URL: Homepage, https://github.com/zanderzhng/codex-move-session
Project-URL: Repository, https://github.com/zanderzhng/codex-move-session
Project-URL: Issues, https://github.com/zanderzhng/codex-move-session/issues
Description-Content-Type: text/markdown

# codex-move-session

`codex-move-session` repairs local Codex sessions after a project directory is renamed or moved.
It supports macOS, Linux, and Windows, discovers both current and legacy Codex session databases,
and repairs absolute paths in session history and generated memories.

> [!WARNING]
> This is an unofficial tool that modifies undocumented Codex data formats. Inspect the dry-run
> carefully, close every Codex process before applying, and retain the generated backup.

## Install

Run without installing:

```console
uvx codex-move-session
```

Install as a persistent uv tool:

```console
uv tool install codex-move-session
codex-move-session --version
```

Before the first PyPI release, run directly from GitHub:

```console
uvx --from git+https://github.com/zanderzhng/codex-move-session codex-move-session
```

Python 3.10 or newer is required.

## Usage

Running without `--old` and `--new` opens the interactive workflow. It finds session working
directories that no longer exist, lets you filter active or archived sessions, prompts for the new
directory, displays every planned data store change, and asks for confirmation.

```console
codex-move-session
```

For scripts, provide both paths. This is a dry-run and does not write anything:

```console
codex-move-session --old /previous/project --new /current/project
```

Close Codex, review the dry-run, then apply the same migration:

```console
codex-move-session --old /previous/project --new /current/project --apply
```

Include archived sessions or select another Codex profile:

```console
codex-move-session \
  --old /previous/project \
  --new /current/project \
  --include-archived \
  --codex-home ~/.codex-work
```

`CODEX_HOME` is respected when `--codex-home` is not given.

## What Changes

The migration is driven by sessions whose `cwd` equals the old directory or is below it. It can
update:

- Every matching `threads.cwd` and structured sandbox-policy path across compatible databases in
  `CODEX_HOME/sqlite/` and legacy `state_5.sqlite`.
- All exact old-root references in JSON string values inside affected rollout JSONL files,
  including metadata, messages, commands, tool calls, and tool output.
- `raw_memory` and `rollout_summary` for affected thread IDs in Codex memory databases.
- Known workspace roots and thread hints in `.codex-global-state.json` and `cap_sid`.

It does not move project files. The destination must already exist before apply. Prompt history,
logs, caches, and previous backups are not rewritten.

Windows paths use case-insensitive matching and support drive, UNC, extended, and mixed-separator
forms. macOS and Linux matching is case-sensitive. Similar names such as `/project-copy` are not
treated as descendants of `/project`.

## Safety

Dry-run is always the default. Apply mode:

1. Refuses to run while a Codex desktop, CLI, or app-server process is detected.
2. Verifies that files and database values did not change after planning.
3. Creates a timestamped touched-data backup under `CODEX_HOME/backups/`.
4. Uses SQLite transactions and atomic file replacement.
5. Runs post-write database and content verification.
6. Restores every touched store if writing or verification fails.

Each backup contains `manifest.json`, standalone SQLite snapshots, and the original content of every
changed file. Backups can contain private conversations and local paths; do not publish them.

## Development

```console
uv sync --all-groups
uv run ruff check .
uv run pytest
uv build
```

Tests construct temporary Codex profiles and never modify the real profile.

## License

MIT
