Updating dev-orchestra (Claude Code / Codex / Antigravity)

Introduction

Last time, I connected my own agent to dev-orchestra. The last post in the series is about updating dev-orchestra to a new version.

Since 1.0.0, dev-orchestra has had two releases, 1.1.0 and 1.1.1. How you update depends on the CLI you use. So I actually tried going from 1.0.0 to 1.1.1 in each of Claude Code, Codex, and Antigravity.

For the test, I set up folders separate from my everyday configuration, installed 1.0.0 there, and then updated (I pointed CLAUDE_CONFIG_DIR for Claude Code and CODEX_HOME for Codex at scratch folders).

Windows 11
Claude Code 2.1.301
Codex CLI 0.163.0
Antigravity CLI (agy) 1.3.6

For what dev-orchestra does, see the introduction post.

dev-orchestra is open source on GitHub (MIT license). If it looks useful, a star would mean a lot.

→ github.com/istb16/dev-orchestra

The short version

CLI	How to update	Takes effect
Claude Code	`claude plugin marketplace update dev-orchestra` → `claude plugin update dev-orchestra`	Restart Claude Code
Codex	`codex plugin marketplace upgrade dev-orchestra` → `codex plugin add dev-orchestra@dev-orchestra`	From the next session
Antigravity (installed as a link)	`git fetch --tags` → `git checkout <new tag>` in the checkout (`v1.1.1` this time)	Restart Antigravity
Antigravity (installed as a copy)	Switch the tag the same way, then run the install command again	Restart Antigravity

The one most likely to trip you up is Claude Code: claude plugin update on its own did not update anything.

Steps

1. Check your current version

Every CLI shows the version in its list of installed plugins.

claude plugin list
codex plugin list
agy plugin list

Claude Code shows this (excerpt).

  ❯ dev-orchestra@dev-orchestra
    Version: 1.0.0
    Scope: user

You can find the latest version on the GitHub releases page or in the CHANGELOG.

2. Claude Code: refresh the marketplace, then update the plugin

The help says claude plugin update updates a plugin to the latest version (restart required to apply). So first I ran just that.

$ claude plugin update dev-orchestra
Checking for updates for plugin "dev-orchestra"…
✔ dev-orchestra is already at the latest version (1.0.0).

It said it was already at the latest version (1.0.0), and nothing was updated. Claude Code’s local copy of the marketplace was still old, so it didn’t know 1.1.1 existed.

After refreshing the marketplace first, the update went through.

$ claude plugin marketplace update dev-orchestra
✔ Successfully updated marketplace: dev-orchestra

$ claude plugin update dev-orchestra
Checking for updates for plugin "dev-orchestra"…
✔ Plugin "dev-orchestra" updated from 1.0.0 to 1.1.1 for scope user. Restart to apply changes.

Running only claude plugin marketplace update left the version in claude plugin list at 1.0.0. You need both.

As the last line says, restart Claude Code to start using the new version.

You can also do this from inside a Claude Code session with /plugin, but I only tried the commands you run from the terminal.

3. Codex: refresh the snapshot, then add the plugin again

Codex keeps the marketplace locally as a snapshot. First, refresh it.

$ codex plugin marketplace upgrade dev-orchestra
Upgraded marketplace `dev-orchestra` to the latest configured revision.

Then run the same command you used to install it.

$ codex plugin add dev-orchestra@dev-orchestra
Added plugin `dev-orchestra` from marketplace `dev-orchestra`.

$ codex plugin list
dev-orchestra@dev-orchestra  installed, enabled  1.1.1  ...

With Codex 0.163.0 this time, the plugin had already switched to 1.1.1 after upgrade. But when I wrote the Codex post, upgrade alone did not install the new version, so running plugin add as well is the safe choice. Running it again does no harm.

The new version is used from the next session you start.

4. Antigravity: it depends on how you installed it

Antigravity loads the directories placed in its plugins/ folder. So the way to update depends on how it was placed there.

If you installed it as a link

If you linked the repository checkout with install.sh --antigravity (install.ps1 -Antigravity on Windows), just switch the checkout to the new version’s tag. In the Antigravity post, I installed from a checkout of the tag (v1.0.0), so switch to the new version’s tag (v1.1.1 here).

cd dev-orchestra
git fetch --tags
git checkout v1.1.1

If your checkout follows a branch (main), git pull works too.

On Windows, the PowerShell installer creates a junction instead of a link. When I switched the checkout from 1.0.0 to 1.1.1, the version in plugin.json seen through the junction changed from 1.0.0 to 1.1.1 as well. I didn’t try a symlink on macOS / Linux this time (I only tried the Windows junction).

Then restart Antigravity.

If you installed it as a copy

These install methods leave a copy:

install.sh --antigravity --copy
install.ps1 -Antigravity -Copy
agy plugin install <path to the checkout>
Running install.sh --antigravity from Git Bash on Windows (Git Bash’s ln -s makes a copy, not a link)

A copy doesn’t change when you switch the checkout. Switch the tag as in the link case, then run the same install command again.

git fetch --tags
git checkout v1.1.1
./install/install.sh --antigravity --copy

If you installed from Windows PowerShell, it looks like this.

git fetch --tags
git checkout v1.1.1
.\install\install.ps1 -Antigravity -Copy

The installer replaces the old copy.

Replaced the existing install at .../.gemini/config/plugins/dev-orchestra
Copied the plugin to .../.gemini/config/plugins/dev-orchestra
Re-run this installer after `git pull` to upgrade.

The message says git pull, but for a checkout on a tag, you switch the tag as above instead.

If you installed with agy plugin install <path>, running it again also changed the version in agy plugin list from 1.0.0 to 1.1.1. Either way, finish by restarting Antigravity.

If you used the installer and you’re not sure which way you installed it, check whether ~/.gemini/config/plugins/dev-orchestra is a link (a junction on Windows). If it’s an ordinary folder, it’s a copy. An install made with agy plugin install is placed somewhere else and is always a copy.

5. If you installed from a checkout

If you installed directly from a checkout without going through a CLI’s plugin system, it works the same way. The README’s “Upgrading” section says a checkout install upgrades with git pull. If your checkout is on a tag, switch the tag as above. For an install made with --copy, run the installer again afterwards (references/workflow.md, “Installing from a skill checkout”). I didn’t try this install method this time.

6. What to check after updating

Run dev-orchestra doctor once (asking Claude Code or another agent to “run dev-orchestra’s doctor” works too). It checks that your CLIs, configuration and models are still fine with the new version. If No problems found. appears, you’re good, but read any notes below it too. As in the example below, a note can say a setting was ignored.

In my test environment, this difference showed up. My config file already had design.ask_questions, a setting added in 1.1.0. The 1.0.0 doctor flagged it as an unknown setting, and the note was gone in 1.1.1.

== 1.0.0
No problems found.
  - design.ask_questions in the global file: unknown key, ignored
== 1.1.1
No problems found.

These are also good to know:

Your configuration and your own adapters are kept. The configuration (config.yaml) and your own adapters (<config directory>/providers/) live in the config directory, outside the plugin. They stay as they are when the plugin is updated
Take a look at the CHANGELOG. Configuration, artifacts and commands stay compatible within a major version. Any change you need to act on is written in the CHANGELOG
New features usually stay off until you turn them on. For example, the “ask questions before the design” feature added in 1.1.0 (design.ask_questions) is off by default. Updating alone doesn’t change how things have been working

Summary

Check your version with claude plugin list / codex plugin list / agy plugin list
Claude Code: claude plugin marketplace update dev-orchestra → claude plugin update dev-orchestra → restart. plugin update alone says “already at the latest version” and does nothing
Codex: codex plugin marketplace upgrade dev-orchestra → codex plugin add dev-orchestra@dev-orchestra. Used from the next session
Antigravity: for a link, switch the checkout to the new version’s tag (git fetch --tags → git checkout <new tag>, v1.1.1 this time, or git pull if you follow a branch). For a copy, then run the install command again. Restart either way
After updating, run doctor once. Your configuration and your own adapters are kept

That’s the end of the series. To read it from the beginning, start with the introduction post; to see every post at once, use the list of “dev-orchestra” posts. When a new version comes out, update with the steps in this post.

GitHub: istb16/dev-orchestra (a star is always appreciated)