> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bymiles.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Lifecycle and compatibility

> Check, update, remove, and integrate the Miles skill without relying on legacy command names.

## Skill lifecycle

The installer adds a lifecycle helper at `~/.miles/bin/miles-skill`.

| Command                                                   | Use                                                                                                       |
| --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| `~/.miles/bin/miles-skill status --json`                  | Check the local installation.                                                                             |
| `~/.miles/bin/miles-skill check-update --json [--force]`  | Check for an available update.                                                                            |
| `~/.miles/bin/miles-skill update`                         | Update the installed skill after user approval.                                                           |
| `~/.miles/bin/miles-skill uninstall [--dry-run] [--json]` | Inspect or remove the installed skill after user approval.                                                |
| `~/.miles/bin/miles-skill uninstall --purge`              | Remove the skill and local Miles credentials only when the user explicitly asks to remove all local data. |

Use `miles help` for the installed CLI's summary. Agents should run `doctor --json` when setup or capability support is unclear.

## Compatibility aliases

These older names remain supported, but new scripts and docs should use the canonical command.

| Earlier name                  | Canonical command                           |
| ----------------------------- | ------------------------------------------- |
| `login`, `whoami`, `logout`   | `auth login`, `auth status`, `auth logout`  |
| `create-site`                 | `site-create`                               |
| `reply`                       | `say`                                       |
| `select-design-direction`     | `build-site --design <number>`              |
| `preview`                     | `connect-browser`                           |
| `build-theme`                 | `convert-theme`                             |
| `export-site`, `export-theme` | `export --type html`, `export --type theme` |
| `messages`                    | `history` for new integrations              |
| `balance`                     | `account-status` for new integrations       |
| `wait`                        | `wait-job` for structured automation        |

`status`, `sites`, and `use` remain supported convenience commands. Use `site-state` when an agent needs the richer state, recovery, approval, plan, and connection details.

## Agent hooks

The installed Miles skill can use host-agent hooks to surface interrupted runs and current authentication state. These hooks are part of the installed skill, not commands for a user or integration to call directly.

## Keeping integrations reliable

Use canonical names, request `--json` when your agent needs to branch on results, and handle the shared exit codes from [Miles CLI reference](/reference/miles-cli/overview). Run an update check at the start of a new session, but ask the user before installing an update or removing the skill.