Import from an Editor
If you already have rules, MCP servers, or other AI config in your editor, aix init --from can convert it into an ai.json for you.
aix init --from <editor>Supported editors:
| Editor | Flag value |
|---|---|
| Cursor | cursor |
| VS Code | vscode |
| Claude Code | claude-code |
| Windsurf | windsurf |
| Zed | zed |
| Codex | codex |
What gets imported
Section titled “What gets imported”aix reads the editor’s existing config files and extracts:
- Rules —
.cursorrules,.windsurfrules,.github/copilot-instructions.md, etc. - MCP servers — from the editor’s MCP config JSON
- Prompts — custom prompt files if the editor stores them
- Skills — any SKILL.md references
Imported content is written to .aix/imported/ and referenced from ai.json:
{ "rules": { "imported-cursor": { "path": ".aix/imported/rules/cursor.md" } }, "mcp": { "github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"], "env": { "GITHUB_TOKEN": "${GITHUB_TOKEN}" } } }}Overwrite protection
Section titled “Overwrite protection”If ai.json already exists, aix init --from will refuse to overwrite it. Use --force to override:
aix init --from cursor --forceNext steps
Section titled “Next steps”After importing, review the generated ai.json and clean up anything that doesn’t apply across editors. Then run:
aix installThis syncs the config to all your detected editors — including the one you originally imported from.