IDE Integrations for Claude Code, Gemini CLI, and Codex CLI in AIOX Core

SynkraAI/aiox-core provides native IDE integrations for Claude Code, Gemini CLI, and Codex CLI through a unified agent synchronization layer, with full automation for Claude Code and Gemini CLI and limited manual support for Codex CLI.

The SynkraAI/aiox-core repository streamlines AI-assisted development by maintaining a single source of truth for agent definitions that syncs to multiple CLI platforms. This unified approach eliminates configuration drift across Claude Code, Gemini CLI, and Codex CLI environments while enforcing validation through a centralized compatibility contract.

How AIOX Core Synchronizes Agents Across IDEs

The integration architecture centers on the .aiox-core/development/agents/ directory, which stores markdown and YAML agent definitions describing each agent's purpose, tools, and optional MCP servers. The Sync Engine distributes these definitions to platform-specific directories using npm scripts.

Run the following command to synchronize all platforms:

npm run sync:ide

Or target a specific platform:

npm run sync:ide:claude
npm run sync:ide:gemini
npm run sync:ide:codex

The engine maps the source directory to:

• .claude/commands/AIOX/agents/ for Claude Code
• .gemini/rules/AIOX/agents/ for Gemini CLI
• .codex/agents/ for Codex CLI

After syncing, the Validation Layer executes platform-specific validators to ensure generated files conform to the compatibility contract at .aiox-core/infrastructure/contracts/compatibility/aiox-4.2.11.yaml. Run validation using:

npm run validate:<platform>-sync
npm run validate:<platform>-integration

Claude Code Integration

Claude Code offers the richest integration experience with full automation and native hooks. The platform supports automatic session tracking, full pre/post checks, and audit trails without manual intervention.

Agent definitions reside in .claude/commands/AIOX/agents/ after synchronization. Activation occurs through slash commands defined in these wrapper files. For example, to activate the development agent:

# In a Claude Code session

/dev

The integration injects pre/post-tool hooks, memory loading, and secret-filtering automatically during runtime. According to the source code in docs/ide-integration.md, this platform requires no additional installation steps beyond the initial sync.

Gemini CLI Integration

Gemini CLI achieves comparable automation through the AIOX Gemini CLI Extension. This integration requires installing the extension from the repository before accessing agent commands.

First, install the extension:

gemini extensions install github.com/synkra/aiox-core/packages/gemini-aiox-extension

After installation and running npm run sync:ide:gemini, agent definitions populate .gemini/rules/AIOX/agents/ alongside native hooks in .gemini/hooks/. Access agents through the launcher menu:

# List all available AIOX agents

/aiox-menu

# Launch a specific agent (e.g., architect)

/aiox-architect

The extension generates platform-specific wrapper commands and supports native Gemini events and hooks with high automatic check coverage, though minor timing differences may occur compared to Claude Code.

Codex CLI Integration

Codex CLI provides limited support requiring manual synchronization steps. Unlike the other platforms, Codex lacks built-in pre/post check automation, necessitating explicit validation workflows.

Agents sync to .codex/agents/ using the dedicated command:

npm run sync:ide:codex

Activation flows through the generic skills interface rather than native commands. After syncing, open the skill selector and choose your agent:

# Open the Codex skill selector

/skills

# Select the AIOX dev agent (displayed as aiox-dev)

aiox-dev

Because Codex CLI offers minimal hook support, you must run validation scripts manually after any agent changes to ensure compatibility with the aiox-4.2.11.yaml contract.

Summary

• Claude Code provides full native integration with automatic pre/post checks via slash commands in .claude/commands/AIOX/agents/.
• Gemini CLI requires the gemini-aiox-extension but delivers comparable automation through /aiox-menu and native hooks.
• Codex CLI supports basic integration via manual npm run sync:ide:codex and the /skills selector with limited validation.
• All platforms source agents from .aiox-core/development/agents/ and validate against .aiox-core/infrastructure/contracts/compatibility/aiox-4.2.11.yaml.

Frequently Asked Questions

Which AI CLI platforms does AIOX Core support?

AIOX Core supports three platforms: Claude Code (full native integration), Gemini CLI (full integration via extension), and Codex CLI (limited manual integration). All three consume agent definitions from the centralized .aiox-core/development/agents/ directory.

How do I activate an AIOX agent in Claude Code?

Activate agents using slash commands generated in .claude/commands/AIOX/agents/. For example, type /dev to launch the development agent or /qa for the quality assurance agent. These commands trigger automatic pre-checks and memory loading without additional configuration.

Why does Codex CLI require manual synchronization?

Codex CLI lacks native hook support and automatic validation capabilities present in Claude Code and Gemini CLI. Therefore, you must manually run npm run sync:ide:codex after modifying agents and execute npm run validate:codex-sync to verify compliance with the compatibility contract before using /skills.

Where are the agent definitions stored?

The single source of truth resides in .aiox-core/development/agents/. The Sync Engine copies these definitions to platform-specific directories: .claude/commands/AIOX/agents/, .gemini/rules/AIOX/agents/, and .codex/agents/. Refer to docs/ide-integration.md for the complete synchronization matrix.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}