Skip to main content
Step Code can reuse Claude Code / Codex workflows: import MCP configuration on first launch, use the Claude Code plugin layout, and load existing CLAUDE.md instructions. Login credentials must be configured again.

​
What migration does

When first launch detects Claude Code or Codex MCP configuration, it shows an import screen. After confirmation, supported servers are written to [mcp_servers] in ~/.stepcode/config.toml.
  • Sources include ~/.claude.json and ~/.codex/config.toml.
  • Source files are read-only: they are not moved, deleted, or overwritten.
  • Each source is offered once, and duplicate content is not imported again.
  • Same-name servers with different configurations receive -claude / -codex suffixes.
  • Environment references retain variable names rather than expanding their values into configuration.
  • Untranslatable fields generate warnings; review the imported result.
Supported transports are stdio and Streamable HTTP. SSE, WebSocket, and IDE-injected servers are not imported automatically. Configure Claude Code project-level mcpServers manually.

​
Automatic MCP import

Use /mcp to inspect connection status and tool counts. Commands, environment variables, and remote permissions must be valid in the environment running Step Code. Both tools can coexist. Import does not keep the two configurations continuously synchronized.

​
Using Claude Code plugins

Step Code reads .claude-plugin/plugin.json, plus .mcp.json, skills, commands, and agents inside the plugin. Marketplace manifests are compatible with .claude-plugin/marketplace.json. Most Claude Code plugins can be installed without changes. See Plugins.

​
Project instruction files

From the current directory up to the filesystem root, select the first matching instruction file in each directory:
  1. AGENTS.override.md
  2. AGENTS.md
  3. CLAUDE.md
Global instructions live at ~/.stepcode/agent/AGENTS.md. Existing CLAUDE.md files do not need to be rewritten just to change their name; check that referenced tools, commands, and paths still apply. Run /reload or restart after changes. --no-context-files disables automatic discovery; /init generates new instructions.

​
What is not migrated

Do not copy credential files in unknown formats or commit configurations containing keys.

​
Next steps