Agent support

AlignTrue supports 30+ AI coding agents through 50+ exporters. Each exporter generates agent-specific configuration files from your AlignTrue rules, ensuring your AI assistants stay aligned across your entire development workflow.

Coverage statistics

• 50+ exporters supporting 30+ agents (counts change frequently)
• MCP configurations for protocol-based agents
• Agent-specific format exporters for native configurations
• Universal format exporters using AGENTS.md
• Dual-output exporters that emit both universal + native formats

This comprehensive coverage ensures AlignTrue rules work across the entire AI coding agent ecosystem, from established tools like Cursor and GitHub Copilot to emerging agents like Windsurf and Roo Code.

Exporter categories

1. MCP (Model Context Protocol) config exporters

These generate JSON/YAML configuration files for agents that support the MCP protocol. MCP allows agents to connect to external tools and data sources. AlignTrue creates agent-specific MCP files with rule-based guidance. See MCP Support for details.

2. Agent-specific format exporters

These create native configuration files or markdown formats specific to each agent (.mdc, .md, .json, .yml, etc.). Each format preserves agent-specific metadata and adapts rules to the agent’s preferred structure.

3. Universal format exporters

AGENTS.md provides a single, universal markdown format that multiple agents can consume, reducing duplication while maintaining broad compatibility.

4. Dual-output agents

Some agents (like Aider) use both a universal format (AGENTS.md) AND their own specific config file for optimal results.

Key features

• Fidelity Notes: Each exporter documents what information may be lost when converting from AlignTrue’s IR format
• Vendor Metadata: Agent-specific extensions are preserved in vendor.* namespaces
• Version Control: All exporters are versioned and follow semantic versioning
• Comprehensive Coverage: Supports 33 agents including Cursor, Claude, GitHub Copilot, Aider, and many others
• Multi-File Adaptation: AlignTrue automatically adapts exports based on each agent’s capabilities—merging for single-file agents, preserving structure for multi-file agents

Multi-file organization support

When you organize your rules across multiple files, AlignTrue adapts exports based on each agent’s native capabilities:

Native multi-file support (preserves your file organization):

• Cursor (.cursor/rules/*.mdc)
• Antigravity (.agent/rules/*.md)
• Amazon Q (.amazonq/rules/*.md)
• KiloCode (.kilocode/rules/*.md)
• Augment Code (.augment/rules/*.md)
• Kiro (.kiro/steering/*.md)
• Trae AI (.trae/rules/*.md)
• Firebase Studio (.idx/*.md)
• Cline (.clinerules/*.md)

Single-file format (AlignTrue merges your files automatically):

• AGENTS.md and all agents using it
• Claude, Warp, Gemini (single markdown files)
• Cline, Goose (plain text files)
• All JSON/config format agents

You organize rules however you want. AlignTrue handles the export complexity.

See Multi-file organization for details.

Export format options

Agents with native multi-file support can optionally use AGENTS.md instead. Configure format per agent in your config:

exporters:
  cursor:
    format: native # Default: .cursor/rules/*.mdc
  amazonq:
    format: agents-md # Use AGENTS.md instead

See Export formats for complete configuration options.

Per-rule targeting

Control which agents receive specific rules using frontmatter:

# Only export to specific agents
export_only_to: [cursor, amazonq]
 
# Exclude from specific agents
exclude_from: [copilot]

See Per-rule targeting for details.

Full compatibility matrix

Targeting rules to specific agents

You can control which agents receive specific rules using frontmatter options:

# .aligntrue/rules/cursor-specific.md
---
title: Cursor-specific debugging
export_only_to: [cursor]
---

This is useful for:

• Agent-specific guidance and tips
• Experimental rules you want to test in one agent
• Performance or compliance requirements
• Reducing noise by excluding irrelevant rules

See Per-rule targeting for details.

Extensibility

Built-in extensibility allows the community to add support for new agents. Each exporter follows a consistent pattern and can be contributed via pull request.

Related documentation

• MCP Support - Complete MCP protocol guide
• CLI Reference - Commands for working with exporters
• Adding Exporters - Guide for adding new agent support
• Sync Behavior - How AlignTrue syncs rules to agents