Migration wizard for importing config from Claude Code, Codex and other AI tools

Context

Raised in Slack. There are plans for a migration wizard to help users switching from other AI coding tools (Claude Code, Codex, etc.). Users have given feedback that while Claude Code config currently works out of the box, there's no control or visibility over what gets imported. Codex has no import path at all.

Problem

When users switch to PostHog Code from another AI coding tool, there is no guided way to:

• Discover what existing configuration is available to import (skills, plugins, permissions, settings, MCP server connections)
• Select which items to import vs skip
• Preview what will be synced and how it maps to PostHog Code concepts
• Track what was imported and what's being kept in sync

Currently Claude Code config is silently picked up with no user control, MCP connections may be missing from the auto-import, and Codex has no import support.

Expected behavior

A migration wizard flow that:

1. Detects installed AI coding tools and their configuration
2. Presents a checklist of importable items grouped by category (settings, MCP servers, permissions, skills/plugins, etc.)
3. Lets the user select what to import and optionally keep in sync
4. Shows a summary of what was imported and any items that couldn't be mapped

Tools to support (initial scope)

• Claude Code — skills, plugins, permissions, settings, MCP connections
• Codex — TBD (needs investigation into what config Codex exposes)

https://posthog.slack.com/archives/C09G8Q32R6F/p1776730221661669?thread_ts=1776723291.344969&cid=C09G8Q32R6F

The issue names no files, tests, or entry points. Start by locating the existing Claude Code auto-import behavior and investigating what Codex configuration exposes. Done means a designed and implemented wizard can discover, select, preview, import, and optionally sync supported items, while reporting unmapped items.