Importing Existing Configs

Already using Claude Code, Cursor, Codex, or GitHub Copilot? The import command scans your existing configuration and converts it to .ai/ format.

Usage

dotai import

The command auto-detects which tools have configuration in your project and imports from all of them.

To import from a specific tool:

dotai import --from claude-code
dotai import --from cursor
dotai import --from codex

What Gets Imported

From Claude Code

Source	Imported as
CLAUDE.md	Directive (alwaysApply: true)
.claude/rules/*.md	Directive (with frontmatter)
.claude/skills/*/SKILL.md	Skill
.claude/agents/*.md	Agent
.mcp.json	ToolServer entries
.claude/settings.json (permissions)	Permission entries
.claude/settings.json (hooks)	Hook entries

From Cursor

Source	Imported as
.cursor/rules/*.mdc	Directive (globs → appliesTo)
.cursor/skills/*/SKILL.md	Skill
.cursor/agents/*.md	Agent
.cursor/mcp.json	ToolServer entries
.cursorignore	IgnorePattern entries

From Codex

Source	Imported as
AGENTS.md	Directive (alwaysApply: true)
.codex/skills/*/SKILL.md	Skill
.codex/config.toml (agents)	Agent entries
.codex/config.toml (mcp_servers)	ToolServer entries
.codex/config.toml (approval_policy)	Permission entries

After Import

After importing, review the generated .ai/ directory:

dotai status    # See what was imported
dotai check     # Validate the configuration
dotai sync      # Generate output for all tools

Tip

Import is non-destructive — it creates .ai/ files but does not modify your existing tool configs. Run dotai sync when you’re ready to regenerate from the unified source.