Codex setup rewrites root symlink into generated skill directory on macOS

[mekcverse]

Codex setup rewrites root symlink into generated skill directory on macOS

Hey gstack team — ran into this while using /gstack-upgrade:

What I was trying to do: Upgrade a shared gstack install and keep Codex using the same installation as Claude.
What happened instead: After ./setup --host auto (or --host codex), the ~/.codex/skills/gstack symlink ended up pointing at the generated .agents/skills/gstack/ directory instead of the gstack repo root. That made runtime paths like ~/.codex/skills/gstack/bin/gstack-update-check fail because bin/ does not exist under .agents/skills/gstack/.
My rating: 6/10 — setup mostly worked, but the Codex root symlink became invalid for runtime assets after upgrade.

Steps to reproduce

1. Install gstack as a git checkout in a Claude skills directory.
2. Expose the same install to Codex via ~/.codex/skills/gstack.
3. Run ./setup --host codex or ./setup --host auto on macOS.
4. Inspect ~/.codex/skills/gstack.
5. Try running ~/.codex/skills/gstack/bin/gstack-update-check.

Raw output

$ readlink ~/.codex/skills/gstack
.../.agents/skills/gstack/

$ ~/.codex/skills/gstack/bin/gstack-update-check
no such file or directory

What would make this a 10

setup should replace the existing Codex symlink atomically so it always points to the gstack repo root, never to the generated .agents/skills/gstack/ directory.

Date: 2026-03-21 | Version: 0.9.4.0 | Skill: /gstack-upgrade

[mvanhorn]

Implemented in #269 - the gstack*/ glob in link_codex_skill_dirs() was matching the sidecar dir and overwriting the root symlink. Added a guard to skip it.