Installation & Updating

Both hosts expose the same skills and workflows. Choose the install and update commands for the host where you work:

Host	Install	Update
Claude Code	`/plugin marketplace add` then `/plugin install`	Turn on auto-update, run `/plugin marketplace update`, or rerun the Git/local install
Codex	`codex plugin marketplace add` then `codex plugin add`	`codex plugin marketplace upgrade` then `codex plugin add`

Claude Code

Marketplace install (recommended) — run inside a Claude Code session:

/plugin marketplace add trackbed/skills
/plugin install trackbed@trackbed

Then turn on auto-update so new releases install themselves: run /plugin, open Marketplaces, select trackbed, and choose Enable auto-update. Claude Code leaves auto-update off for third-party marketplaces until you do.

Other installs — run from your terminal:

# Direct Git install
claude /plugin install git+https://github.com/trackbed/skills

# Local development
claude /plugin install /path/to/skills/trackbed

Codex

The plugin ships to Codex as a native Codex plugin. A converter builds a Codex marketplace from the Claude plugin source, and Codex installs the plugin from that marketplace into its own plugin cache, where it also owns updates and removal.

Install the published plugin without a clone (requires the Codex CLI):

codex plugin marketplace add trackbed/skills --ref codex-plugin
codex plugin add trackbed@trackbed

Or build and install it yourself:

# From a checkout
npm install
node trackbed/scripts/convert-plugin.js install trackbed

# With npx, without a clone
npx --yes github:trackbed/skills install trackbed

# Local development from this repository
./trackbed/scripts/install-codex.sh

Checkout installs build the marketplace under the Codex home ($CODEX_HOME or ~/.codex; override it with --codex-home) and offer to remove output left by earlier converter releases. The Agent Portability Matrix covers installer options, build output, and publishing.

To uninstall:

# Published install
codex plugin remove trackbed@trackbed
codex plugin marketplace remove trackbed

# Checkout install, including the marketplace and any legacy output
node trackbed/scripts/convert-plugin.js uninstall trackbed

Updating

When a new release is out, the update-check hook tells you at the start of a session and gives the update commands for your host. It checks at most once a day, so the notice can arrive up to a day after the release. After you update, the next session names the new version and, in Claude Code, how many breaking changes it includes. To turn the hook off or keep it offline, see update-check.

Install	How to update
Claude Code marketplace	Auto-update, `/plugin marketplace update trackbed` in a session, or `claude plugin update trackbed@trackbed` from a terminal
Claude Code Git or local	Re-run the install command
Codex published	`codex plugin marketplace upgrade trackbed`, then `codex plugin add trackbed@trackbed`
Codex checkout	Re-run the install command; it rebuilds the marketplace and reinstalls the plugin into the Codex cache

Codex update notices include both paths. marketplace upgrade requires a Git marketplace; local installs made from a checkout or through npx must re-run their original install command.

Restart the host you updated, or run /reload-plugins in Claude Code, for changes to take effect.

Claude Code auto-update needs v2.0.70 or later. When a release lands, Claude Code shows Plugin updated with a /reload-plugins prompt. /trackbed:setup reports the auto-update policy from local settings and the marketplace record, but it does not inspect session flags, remote or OS-managed policy, or workspace trust; confirm the effective policy under /plugin.

Checking Your Installation

Claude Code: open /plugin to see the marketplace registration and installed version.
Codex: run codex plugin list; the plugin appears as trackbed@trackbed with its status, version, and marketplace source.
Either host: run /trackbed:setup for a read-only report of missing tools, cached plugin versions, and update status. It never installs plugins or changes host configuration.

With a non-default Codex home, keep CODEX_HOME exported in shells Codex runs, because converted skills locate their files through it. If skills from an earlier converter release appear twice, run the checkout install again with --yes to remove the legacy copy.