Hivemind turns agent traces into skills and shares with your team

Summary

codex 0.130.0 renamed the codex_hooks feature flag to hooks. The legacy
key still works but prints a deprecation warning on every codex startup:

`[features].codex_hooks` is deprecated. Use `[features].hooks` instead.
Enable it with `--enable hooks` or `[features].hooks` in config.toml.

Users who installed an earlier revision of this plugin have codex_hooks = true
written into ~/.codex/config.toml, so the warning keeps firing on every
codex launch even after they upgrade hivemind. codex features disable codex_hooks
does not help — codex just flips it to false, and the deprecation check
fires on the key being present at all, regardless of value.

What changed

• src/cli/install-codex.ts
  • tryEnableCodexHooks() now calls codex features enable hooks (the new
    feature name). The existing best-effort try/catch is preserved so the
    install doesn't fail when codex CLI isn't on $PATH.
  • New stripLegacyCodexHooksKey() runs after the enable on every install
    and removes any top-level codex_hooks = ... line from ~/.codex/config.toml.
    Regex matches the key only at line start, immediately followed by =, so
    it never touches codex_hooks_other or [features.codex_hooks] table
    headers. Gracefully no-ops if the file does not exist.
• codex/INSTALL.md — updated to mention the renamed flag and the legacy-key cleanup.
• tests/cli/cli-install-codex-fs.test.ts
  • Updated the existing "best-effort enable" test to assert the new hooks
    argument and to defend against regressing to codex_hooks.
  • Added coverage for:
    • legacy codex_hooks line is stripped on install
    • config file is byte-identical when no legacy key is present
    • prefix matches (codex_hooks_other) and [features.codex_hooks] table
      headers are not falsely matched
    • install does not crash when config.toml is missing

Why not just enable hooks and leave the legacy line?

Because the deprecation warning fires on key presence. Users who upgrade
without cleanup would still see the warning every time they launch codex.
The strip is a one-shot side effect of running install (or reinstall), so
the upgrade path is "run the new install once → warning gone forever".

Tests

• Unit tests for installCodex: 15/15 passing (includes 4 new tests for the
  strip logic).
• Full suite: 2917/2917 passing.
• End-to-end smoke test against an isolated HOME:
  • Pre-state: ~/.codex/config.toml contains codex_hooks = true plus
    unrelated some_other = true and a model = "..." outside [features].
  • After hivemind codex install:
    • codex_hooks line removed
    • hooks = true added by codex features enable hooks
    • some_other = true and the top-level model = ... untouched
  • codex exec no longer prints the deprecation warning.

Test plan

• [x] Unit tests green (npx vitest run)
• [x] End-to-end isolated-HOME smoke test (legacy line removed, no warning on codex launch)
• [x] False-positive defense (table header / suffixed key not matched)
• [x] Missing config.toml does not throw

Out of scope

The bubblewrap not on PATH and MCP swarm failed to start warnings observed
on the same codex launch are unrelated to this plugin (system package /
external MCP server) and are not addressed here.

Summary by CodeRabbit

• Documentation

  • Updated installation documentation to reflect current setup procedures.

• Refactor

  • Enhanced the installer to use modern feature flag configuration.
  • Added automatic cleanup of legacy configuration entries during installation for smoother upgrades.