 | For the last 8 months I've developed strictly using Claude Code, setting up context layers, hooks, skills, etc. But relying on one model has been limiting, so here is how I setup context knowledge transfer between Claude and Codex. The key idea is that just like Claude Code (.claude/skills/ + CLAUDEmd), you can generate matching Codex CLI docs (AGENTSmd + .agents/skills/). Then, the only things is to keep documentation current for both. Aspens can generate both doc sets once and an optional git post-commit hook can auto-update them on commits. You can work with both models or just one. It works either way. I would love to see if others have found better ways for this ? [link] [comments] |
Continuous Knowledge Transfer Between Claude and Codex
Reddit r/artificial / 4/8/2026
💬 OpinionDeveloper Stack & InfrastructureSignals & Early TrendsTools & Practical Usage
Key Points
- The article describes a workflow for sharing and synchronizing project context between Claude Code and Codex by generating parallel documentation and skill directories for each model.
- It proposes keeping Claude-specific files under .claude (skills, hooks, and CLAUDE.md) and Codex-specific files under .agents (AGENTS.md and corresponding skills), so both models can reference up-to-date instructions.
- The author suggests using tools like Aspens to generate both doc sets initially and optionally automate updates via a git post-commit hook.
- The approach is presented as flexible—developers can use both models together or rely on only one while still maintaining the synchronized documentation structure.
- The post invites community feedback on whether others have found improved methods for continuous knowledge transfer across coding assistants.
