Skip to content

Introduction

Aura finds configuration drift between the coding agents on your machine and gives you one safe plan to repair it. Use it when Claude Code, Codex, and Cursor should share instructions, skills, and MCP servers without maintaining the same configuration three times.

Imagine a repository with these three states:

Application Instructions Skills MCP servers
Claude Code Loads the team rules Has review Has GitHub
Codex Loads an older rules file Missing review Has GitHub
Cursor Loads no shared rules Has a stale review Missing GitHub

Aura reads each application’s configuration into one model and reports the differences. When a finding can be repaired, Aura builds a file plan, shows it to you, and waits for confirmation.

Inspect

Detect supported applications and explain configuration, authentication, instruction, skill, and MCP findings.

Converge

Consolidate shared instructions and apply reviewed skills and MCP selections through one previewable plan.

Recover

Back up successful writes, roll back failed transactions, and restore an earlier change with aura undo.

Aura manages personal configuration below ~/agents and the global configuration of applications you select. It may inspect repository files for diagnostics, but setup, fixes, and undo do not modify the current repository.

Every write goes through the same safety path:

  1. Aura reads and validates the current files.
  2. It shows one combined plan; add --detail when you need the complete diff.
  3. It checks that the files did not change after the preview.
  4. It writes atomically and records a backup for aura undo.