codex-sync

Portable backup and sync repo for Codex skills and MCP/config scaffolding.

Update Notes

2026-03-14

Added 8 AIGC platform skills for multi-service FastAPI and AI workflow work:

• aigc-backend-architect
• aigc-ai-engineer
• aigc-api-tester
• aigc-devops-automator
• aigc-security-engineer
• aigc-sre
• aigc-database-optimizer
• aigc-technical-writer

These skills are tailored for an AIGC platform with Python microservices, Docker Compose operations, shared integration tests, PostgreSQL-backed task tables, observability tooling, and documentation-heavy workflows.

What is stored here

• skills/ — user-installable skills copied from ~/.codex/skills (excluding .system)
• config.shared.toml — shared Codex settings that can be reused across machines
• hosts/*.toml — host-specific overlays (local Windows, server Windows, server Linux)
• install-server.ps1 / install-server.sh — install helpers that copy skills and build ~/.codex/config.toml

Why it is split this way

Do not copy an entire ~/.codex directory between machines. A full copy can contain:

• machine-specific paths
• Windows/Linux-specific settings
• local MCP working-directory fixes
• auth/session state
• secrets or tokens

Instead, keep:

• shared settings in config.shared.toml
• per-host differences in hosts/*.toml
• credentials and login state configured separately on each machine

Current profiles

• hosts/local.windows.toml — current AICHI Windows workstation profile
• hosts/server.windows.toml — template for a Windows server
• hosts/server.linux.toml — generic Linux server template
• hosts/server.ubuntu.toml — Ubuntu-oriented server template

Install on a Windows machine

# from the repository root
./install-server.ps1 -HostProfile server.windows.toml

To rebuild the current local Windows config instead:

./install-server.ps1 -HostProfile local.windows.toml

Install on a Linux server

chmod +x install-server.sh
./install-server.sh server.linux.toml

Install on an Ubuntu server

Recommended if your server is Ubuntu:

git clone [email protected]:nleson/codex-sync.git
cd codex-sync
chmod +x install-server.sh
./install-server.sh server.ubuntu.toml

If you want chrome-devtools on Ubuntu server, make sure the machine has:

• Node.js 20.19+ or newer LTS
• Chrome or Chromium installed
• a usable headless environment

After installation on each machine

1. Set CODEX_API_KEY
2. Edit the target host profile placeholders (YOUR_USER, paths, optional MCP blocks)
3. Login to Context7 again:
   • codex mcp login context7
4. Verify:
   • codex mcp list
   • codex mcp get context7
   • if enabled: codex mcp get chrome-devtools

Optional Chrome DevTools MCP notes

• The local Windows profile includes a validated chrome-devtools MCP block.
• On the AICHI workstation it also keeps:
  • cwd = 'C:\Users\AICHI'
• That workaround avoids C:\Users\AICHI\.openclaw\node.cmd interfering with npx resolution.
• For servers, enable chrome-devtools only if the target machine actually has the required Node.js + Chrome environment.
• The Ubuntu profile ships with a safer commented example using:
  • --headless
  • --isolated

Refresh skills from the source machine

Windows PowerShell example:

robocopy "$HOME\.codex\skills" ".\skills" /E /XD .system

Secrets / auth not stored here

Do not commit:

• CODEX_API_KEY
• PATs / tokens
• MCP login state
• local browser/session data