# Update Aegis

Use when the user says `aegis:update`, asks to update or upgrade an installed Aegis...

- Repository: https://github.com/GanyuanRan/Aegis (1408 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-25
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add GanyuanRan/Aegis --skill update-aegis -g -a claude-code -y`
Codex: `npx skills add GanyuanRan/Aegis --skill update-aegis -g -a codex -y`
Cursor: `npx skills add GanyuanRan/Aegis --skill update-aegis -g -a cursor -y`
Gemini CLI: `npx skills add GanyuanRan/Aegis --skill update-aegis -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add GanyuanRan/Aegis`

## Description

Use when the user says `aegis:update`, asks to update or upgrade an installed Aegis method-pack, wants the latest Aegis version, or asks whether Aegis is current on this host.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Update Aegis

Update the installed Aegis Method Pack for the current AI coding host.

This skill is host maintenance. Do not edit the target project just because the
user asked to update Aegis.

## Default Semantics

- `aegis:update` updates the current host's registered Aegis installation.
- Updating every registered host requires an explicit `--all` request.
- If more than one host is registered and the current host cannot be identified,
  ask one concrete question before updating.
- Do not update a development checkout when the installed method-pack root is a
  separate path.
- Do not perform background automatic updates. The local registry may record
  `updateMode`, but this skill only performs explicit user-triggered updates.

## Evidence First

From the installed method-pack root, inspect the host-scoped registry:

```bash
python scripts/aegis-update.py status --json
```

If the registry is missing, register the current host before updating. Use the
host's install guide and actual discovery path rather than guessing.

If `~/.config/aegis/config.toml` already declares `method_pack_root`, prefer
that canonical root when registering additional hosts. Host-specific discovery
paths, copied skill directories, plugin caches, or adapter payloads should be
treated as generated / host-managed views into the same Aegis body, not as
separate editable checkouts.

Codex example:

```bash
python scripts/aegis-update.py register \
  --host codex \
  --sync-mode junction \
  --discovery-root ~/.agents/skills/aegis \
  --reload-hint "restart Codex"
```

Copy-based host example:

```bash
python scripts/aegis-update.py register \
  --host codebuddy \
  --sync-mode copy-skills \
  --discovery-root ~/.codebuddy/skills \
  --reload-hint "restart CodeBuddy"
```

The rest: https://github.com/GanyuanRan/Aegis/blob/HEAD/skills/update-aegis/SKILL.md