bdb-updater git:20260908.e3de3ceA

Immutable. This exact content is served forever at /api/v1/blob/c20b4266f9c75434.

---
name: bdb-updater
description: Use when proactively checking for and installing updates to the AOS (BDB Agent OS) package via npm.
category: bdb-core
disable-model-invocation: true
---

# BDB Updater Skill

Keeps AOS (`@hybridlabor-api/aos`) up to date. Since v4.0.0 (renamed from
`@hybridlabor-api/bdb-dev-optimized-agent-skills`, which is deprecated on
npm and frozen at its last pre-rename version — never check that name,
it will never report a real update again).

## 1. Check for an update

```bash
npm view @hybridlabor-api/aos dist-tags --json
```

Compare against the locally installed version (`~/.agents/aos/package.json`,
or wherever the primary install target's `package.json` lives — the
installer's own `verifyEcosystemInstallation()` status table is the
authoritative source if you're running from inside an existing install).

Two dist-tags exist:
- **`@latest`** — the stable channel. CI (`release-please`) publishes here
  automatically on every release; this is what real users should run.
- **`@next`** — an ad-hoc staging tag used occasionally to validate a large
  change (a rename, a major version bump) before promotion to `@latest`.
  It is not a standing parallel channel — don't default to it unless the
  user is specifically testing a migration.

## 2. Run the update

```bash
npx -y @hybridlabor-api/aos@latest
```

`-y` runs it fully non-interactively. If an install already exists, this
takes the **Quick Update** path (refreshes skills, re-syncs installed
submodules, refreshes the OpenWiki daemon schedule) rather than a full
reinstall — it does not need a `--force` flag or any special handling for
"already installed."

The installer syncs skills to every detected harness in one pass, not
just one: `~/.claude/skills`, `~/.gemini/config/skills` (Antigravity),
`~/.agents/skills`, `~/.codex/skills`, `~/.cursor/skills`, `~/.roo/skills`.
Don't assume Gemini/Antigravity is the only target.

## 3. Verify the result

After running, `verifyEcosystemInstallation()`'s own status table (printed
at the end of the run) is the ground truth — it checks each tracked
submodule's actual installed version against its own npm dist-tags
(`bdb-synapse`, `memB`, `heimdall-token-saver`, `bdb-dev-creator-extension`,
`bdb-os-remote`, `bdb-dev-tool-installer`, and `aos` itself). Read that
table rather than assuming success from a clean exit code — a partial
failure (e.g. a daemon not responding on its port) still exits 0 and logs
a warning, not an error.

Report the new version and anything flagged as a warning in that table
(not just "update complete"). Don't report success without having actually
looked at the status table's contents.

## 4. Scheduled updates

If the user wants recurring checks, recommend `/schedule` with the current
package name:
`/schedule CronExpression="0 10 * * 1" Prompt="Check if there is a new version of @hybridlabor-api/aos via npm view and update it"`