Use Claude and Codex without getting locked into one platform

Question: How do you use Claude and Codex without getting locked into one platform? Answer: Keep your skills and instructions outside any single tool and point every tool at the same copy. Dustin Thompson stores his skills on GitHub, symlinks his CLAUDE.md file to his AGENTS.md file so Claude Code and Codex read identical instructions, and uses GitHub versioning to roll back a broken skill in plain English. Once the skills live in one canonical place, choosing Claude or Codex for a project, or moving a scheduled task between them, becomes a feature and usage decision rather than a migration. In this episode, Andrew Foxwell and Thomas Moen talk with Dustin Thompson, owner of Konnected Interactive, about how to use Claude and Codex side by side without getting locked into either platform. Dustin explains why every skill he has lives in one place on GitHub, how a symlink lets Claude Code and Codex read the same instructions, where scheduled tasks should run, and how he tests a new model before trusting it with real work. Dustin owns Konnected Interactive, where he builds AI systems for agencies and ecommerce teams, and he is the builder behind the Foxwell Bot and much of the internal tooling at Foxwell Founders and Foxwell Digital. We discuss: - Why Dustin runs Claude and Codex all day instead of picking one - How Codex imports your memories and skills from Claude - Why your AI skills belong on GitHub instead of Dropbox or a local drive - Using GitHub versioning to roll back a broken skill in plain English - Sharing one skills library across a team, and seeing which skills actually get used - What a symlink is, and how CLAUDE.md and AGENTS.md stay in sync - Whether scheduled tasks should run in Claude or Codex - Why reporting is the first thing an agency should automate, not ad creative - Why AI without a strategy usually means more cost for the same output - How to test a new model with known-answer tasks, reasoning traces and evals Listen to the full podcast: https://podcasts.apple.com/us/podcast/ai-dtc-wtf/id1896687855 Show site: https://www.ai-dtc-wtf.com/ Connect the Foxwell MCP to Claude or ChatGPT: https://www.foxwelldigital.com/mcp Guest: Dustin Thompson, Owner, Konnected Interactive Konnected Interactive: https://konnectedinteractive.com/ Dustin on LinkedIn: https://www.linkedin.com/in/dustinjthompson This Episode is sponsored by Motion's very own Runneth. Runneth is the AI Tool that is quickly becoming the go to decision maker brands turn to when it comes to creative decisions within their ad accounts. From Creative strategist to hook inspirations and creative briefs, runneth can do it all. See the case studies and try runneth yourself https://runneth.com/ AI DTC WTF is the show for brand owners, in-house advertisers and agency operators who use AI every day and want tactical workflows they can implement now. Published by Foxwell Digital: https://www.foxwelldigital.com/ To connect with Andrew Foxwell reach him here [email protected] To connect with Will Sartorius DM him here https://x.com/will_sartorius To connect with Thomas Moen DM him here https://x.com/thomasmoen To learn more about Foxwell Founders and conversations like this one, go here: https://www.foxwellfounders.com Learn more about Foxwell Digital and join our newsletter: https://www.foxwelldigital.com/email Chapters 02:22 Why run Claude and Codex side by side 05:52 Why your AI skills belong on GitHub, not Dropbox 08:03 How to share one skills library across a team 10:49 What a symlink is, and why it keeps Claude and Codex in sync 11:53 Should scheduled tasks run in Claude or Codex? 14:16 What to automate first: reporting, not ad creative 18:55 Why AI without a strategy just costs you more 21:28 How to test a new AI model before you switch 24:35 What Dustin is building: the Foxwell Bot and a model orchestrator