← All use cases

Use one release in Claude Code and Codex

Goal

Half your team uses Claude Code and half uses Codex. You want both on the same Guild Stack release. Claude Code and Codex are the two hosts the 3.0.0 release was tested on before it shipped.

The result

Four commands later, both hosts carry Guild Stack, and two receipt files under ~/.guild/receipts/ name the same version and the same source commit — your proof that the two installs match. Here is the whole thing.

Commands

You need the claude and codex command-line tools on your machine.

git clone -q https://github.com/lookatitude/guild.git src
git -C src checkout -q v3.0.0
bash src/install.sh --host claude-code-cli
bash src/install.sh --host codex-cli

To try it without touching your real setup, put HOME="$PWD/home" in front of each bash src/install.sh line, after mkdir home. That is what the test suite does.

What Guild Stack produced

For Claude Code:

  • An entry guild@guild in ~/.claude/plugins/installed_plugins.json at the release version.
  • The plugin files under ~/.claude/plugins/cache/guild/guild/<version>/.
  • A release identity file in that folder that names the version, the source commit, and the claude-code package.
  • An install receipt at ~/.guild/receipts/claude-code-cli.json.

For Codex:

  • The plugin files under ~/.codex/plugins/cache/guild/guild/<version>/, with skills under .agents/skills/guild/.
  • A release identity file naming the same version and source commit, and the codex package.
  • An install receipt at ~/.guild/receipts/codex-cli.json.
  • A guild entry in ~/.codex/config.toml.

Both receipts carry the same version and commit. That is how you confirm the two hosts match:

cat ~/.guild/receipts/claude-code-cli.json ~/.guild/receipts/codex-cli.json

Time and cost

The test suite allows up to 10 minutes per host install. Token cost is not measured by these scenarios.

New to Guild Stack? Install it first.