codex-settings-sync

Migrates Codex state from ~/.codex to a Redis-backed Agent Filesystem workspace.

30|6|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/redis/agent-filesystem --skill codex-settings-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-settings-sync
Source: https://github.com/redis/agent-filesystem/tree/main/skills/codex-settings-sync
Command: npx skills add https://github.com/redis/agent-filesystem --skill codex-settings-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It prevents fragmented Codex state when you switch machines by letting you migrate and mount your ~/.codex directory as a shared Redis-backed workspace.

Core Features & Use Cases

  • Migration with workspace import: Moves existing ~/.codex into Agent Filesystem while applying an ignore file to avoid copying high-churn and local-only state.
  • Cross-machine sharing via mount (sync or live mount): Recreates the same shared Codex memory/settings on additional computers using either sync mode or live mount mode.
  • Safety-oriented defaults and rollback: Encourages excluding worktrees/ and cache/tmp/log/temp artifacts, and provides unmount/restore steps if something goes wrong.

Use Case: You want the same Codex prompts, notes, and configuration across a laptop and a desktop without manually reconfiguring or losing local state each time.

Quick Start

Use the skill to migrate your current Codex state by running: ./afs ws import --mount-at-source .codex ~/.codex.

Frequently Asked Questions about codex-settings-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Codex settings and state across multiple computers?

You can sync Codex settings across computers by migrating the ~/.codex directory into a Redis-backed Agent Filesystem workspace using ws import, then mounting it on secondary machines with ws mount.

What is the best way to migrate Codex memory to a shared workspace?

The best way to migrate Codex memory is running an afs workspace import command on the source machine, which moves ~/.codex into a checkpointable Redis-backed workspace for shared use.

How do I exclude local-only artifacts like caches and logs during Codex state migration?

You exclude local-only artifacts during Codex state migration by creating an optional .afsignore file that uses .gitignore-style patterns to filter out caches, logs, and temporary files.

Can I use a live mount mode for cross-machine workspace sharing?

Yes, you can use either sync mode or live mount mode when running ws mount on secondary machines to recreate shared Codex memory and settings across computers.

What should I exclude from my Codex workspace to prevent syncing high-churn files?

You should exclude worktrees and cache/tmp/log artifacts from your Codex workspace to prevent syncing high-churn local-only state and maintain cross-machine consistency.

How do I restore local state if a Codex workspace mount goes wrong?

If a Codex workspace mount goes wrong, the skill provides safety-oriented defaults and unmount/restore steps to roll back the shared Redis-backed workspace configuration.