aaslisted

# Account-aware agent execution aas may hold multiple accounts. Discover them at runtime; never hard-code local account names or assume only the active account exists. Use the installed `aas` binary and its help to check feature availability. ## Discover and choose Run `aas candidates --provider <provider> --json` before choosing an account. The versioned JSON contains `accounts`, sorted with eligible accounts first and then by observed remaining quota. Use `name` as the CLI account argument, not `id`. `eligible` means observed quota is available; it does not guarantee model access, valid inference credentials, or compatibility. `cached` and `fetchedAtMs` describe freshness. Missing meters and usage errors are unknown, not available capacity. `usageCooldownUntilMs` is a usage-endpoint cooldown, not an inference reset time. Use `--fresh` to refresh evidence when needed; it still honors usage backoff. Repeat `--exclude <name>` to exclude accounts already attempted. On older versions without `candidates`, use `aas list` and `aas usage --json`. Do not expose credentials: avoid `list -d`, credential files, and `export` output. Prefer a compatible account on the same provider. Respect the user's account, organization, model, and data-routing constraints. Registration alone does not authorize sending a project's data to another organization or provider. ## Execute and recover For an authorized alternate account, run `aas exec <name> -- <agent arguments>`. This selects the acc