Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
fix(codex): drop activity-marker hooks Codex can't drive (#2786)
Maximilian Roos233cd493d010
diff --git a/CLAUDE.md b/CLAUDE.mdindex d836010a6..07ae474c6 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -168,6 +168,22 @@ cargo insta test --accept -- --test integration "test_help"Config docs (`USER_CONFIG_START`/`PROJECT_CONFIG_START` sections in `src/cli/mod.rs`) generate `dev/*.example.toml` files where every line is commented out with `#`. TOML comments inside code blocks become double-commented (`# # comment`). Use plain text descriptions ending with colons before each code block instead — inline end-of-line comments (e.g., `key = "value" # explanation`) are fine.+## Codex Plugin++The Codex plugin is separate from the Claude Code plugin (`.claude-plugin/`) and uses Codex's marketplace layout:++```+.agents/plugins/marketplace.json ← marketplace manifest Codex enumerates+plugins/worktrunk/.codex-plugin/plugin.json ← plugin manifest+plugins/worktrunk/skills -> ../../skills ← symlink to repo-root skills/+```++Codex discovers a marketplace's plugin list strictly from `<repo-root>/.agents/plugins/marketplace.json` (no fallback to `.claude-plugin/marketplace.json`). Each plugin's `source` must be an object pointing at a non-empty subdirectory — codex rejects a bare or root-relative source — so the plugin lives in `plugins/worktrunk/`, not at the repo root.++**No activity-marker hooks.** Unlike the Claude Code plugin, the Codex plugin ships no `hooks` — the manifest has no `hooks` key and there is no `hooks/` directory. Codex's `HookEventNameWire` vocabulary (codex-cli 0.130.0: `PreToolUse`, `PermissionRequest`, `PostToolUse`, `PreCompact`, `PostCompact`, `SessionStart`, `UserPromptSubmit`) has no `Stop`/turn-end event, so a 🤖 marker set on `UserPromptSubmit` could never return to 💬 within a session — it would stick at "working" indefinitely. Re-add `hooks.json`, the `hooks` manifest key, the install hints in `src/commands/config/codex.rs`, and the docs (`docs/content/claude-code.md` "Activity tracking", `src/cli/config.rs` plugin list) once Codex exposes a turn-end hook event.++**Accepted tradeoff — `skills` exposes `wt-switch-create`.** The manifest's `"skills": "./skills/"` resolves through the `plugins/worktrunk/skills -> ../../skills` symlink, exposing the entire repo-root `skills/` directory — including `wt-switch-create`, which depends on Claude session-cwd switching and the `WorktreeCreate` hook that Codex doesn't provide. We accept this: Codex loading a skill it can't act on is harmless, and a single repo-root `skills/` keeps the `worktrunk` skill single-source across both plugins. Don't add a Codex-only skills subtree to exclude it.+## Data SafetyNever risk data loss without explicit user consent. A failed command that preserves data is better than a "successful" command that silently destroys work.diff --git a/docs/content/claude-code.md b/docs/content/claude-code.mdindex 97e5af101..913b90195 100644--- a/docs/content/claude-code.md+++ b/docs/content/claude-code.md@@ -1,23 +1,21 @@+++title = "Claude Code & Codex Integration"-description = "Worktrunk plugins for Claude Code and Codex: configuration skill, agent worktree isolation, and activity tracking for wt list."+description = "Worktrunk plugins for Claude Code and Codex: a shared configuration skill, plus Claude-only worktree isolation and wt list activity tracking."weight = 23[extra]group = "Reference"+++-Worktrunk ships plugins for Claude Code and Codex. Both bundle:--1. **Configuration skill** — Documentation the agent can read, so it can help set up LLM commits, hooks, and troubleshoot issues-2. **Activity tracking** — Status markers in `wt list` showing which worktrees have active agent sessions (🤖 working, 💬 waiting)+Worktrunk ships plugins for Claude Code and Codex. Both bundle a **configuration skill** — documentation the agent can read, so it can help set up LLM commits, hooks, and troubleshoot issues.The Claude Code plugin additionally provides:-3. **Worktree isolation** — Routes agent-created isolated worktrees through `wt switch --create` / `wt remove` instead of raw `git`-4. **`/wt-switch-create` command** — Creates a worktrunk worktree and moves the current Claude session into it+1. **Activity tracking** — Status markers in `wt list` showing which worktrees have active agent sessions (🤖 working, 💬 waiting)+2. **Worktree isolation** — Routes agent-created isolated worktrees through `wt switch --create` / `wt remove` instead of raw `git`+3. **`/wt-switch-create` command** — Creates a worktrunk worktree and moves the current Claude session into it-Codex does not currently expose equivalent worktree-lifecycle hooks, so Codex users invoke `wt switch --create` and `wt remove` directly.+Codex exposes no turn-end or worktree-lifecycle hooks, so the Codex plugin ships only the configuration skill.## Installation@@ -37,9 +35,7 @@ This configures the Worktrunk marketplace in Codex. Then run `/plugins` in Codex{{ terminal(cmd="codex plugin marketplace add max-sixty/worktrunk") }}-To remove the marketplace entry, run `wt config plugins codex uninstall`. Already-installed plugins and global Codex hook feature flags are left unchanged.--If activity markers do not appear after installing the plugin, Codex may be gating plugin-bundled hooks. Run `codex features list`; if `plugin_hooks` is `false`, enable it (`codex features enable plugin_hooks`), or copy this repo's `plugins/worktrunk/hooks/hooks.json` to `~/.codex/hooks.json`.+To remove the marketplace entry, run `wt config plugins codex uninstall`. Already-installed plugins are left unchanged.## Configuration skill@@ -52,9 +48,9 @@ The plugin includes a skill — documentation the agent can read — covering WoClaude Code is designed to load the skill automatically when it detects worktrunk-related questions.-## Activity tracking+## Activity tracking (Claude Code only)-The plugins track agent sessions with status markers in `wt list`:+The Claude Code plugin tracks Claude sessions with status markers in `wt list`:<!-- ⚠️ AUTO-GENERATED from tests/snapshots/integration__integration_tests__list__list_with_user_marker.snap — edit source to update -->@@ -74,7 +70,7 @@ The plugins track agent sessions with status markers in `wt list`:- 🤖 — agent is working- 💬 — agent is waiting or idle-The Claude Code plugin clears the marker when a session ends; Codex exposes no session-end hook event, so a Codex worktree rests at 💬 after its session ends rather than clearing. Either plugin can also leave a stale marker if the agent process is killed before its stop hook runs. `wt config state marker clear` removes a marker manually.+The plugin clears the marker when a session ends. A stale marker can remain if the Claude process is killed before its stop hook runs; `wt config state marker clear` removes a marker manually.### Manual status markersdiff --git a/docs/static/llms.txt b/docs/static/llms.txtindex 93310f347..13850942e 100644--- a/docs/static/llms.txt+++ b/docs/static/llms.txt@@ -23,6 +23,6 @@ with many parallel changes, including hooks to automate local workflows.- [Extending Worktrunk](https://worktrunk.dev/extending.md): Three ways to add custom behavior: hooks for lifecycle automation, aliases for reusable commands, and custom subcommands for standalone tools.- [LLM Commit Messages](https://worktrunk.dev/llm-commits.md): Generate commit messages from diffs using any LLM. Integrates with wt merge, wt step commit, and wt step squash.-- [Claude Code & Codex Integration](https://worktrunk.dev/claude-code.md): Worktrunk plugins for Claude Code and Codex: configuration skill, agent worktree isolation, and activity tracking for wt list.+- [Claude Code & Codex Integration](https://worktrunk.dev/claude-code.md): Worktrunk plugins for Claude Code and Codex: a shared configuration skill, plus Claude-only worktree isolation and wt list activity tracking.- [Tips & Patterns](https://worktrunk.dev/tips-patterns.md): Practical recipes for Worktrunk workflows: aliases, shell integration, Zellij layouts, and parallel agent patterns.- [FAQ](https://worktrunk.dev/faq.md): Common questions about Worktrunk: comparison to git worktree and branch switching, bare repos, TUI support, and more.diff --git a/plugins/worktrunk/.codex-plugin/plugin.json b/plugins/worktrunk/.codex-plugin/plugin.jsonindex 78fa9a50e..b48c1ee05 100644--- a/plugins/worktrunk/.codex-plugin/plugin.json+++ b/plugins/worktrunk/.codex-plugin/plugin.json@@ -1,23 +1,22 @@{"name": "worktrunk",- "description": "Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance and bundled activity hooks for Codex sessions.",+ "description": "Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths) for Codex sessions.","author": {"name": "Worktrunk","url": "https://github.com/max-sixty/worktrunk"},- "homepage": "https://worktrunk.dev/claude-code/",+ "homepage": "https://worktrunk.dev","repository": "https://github.com/max-sixty/worktrunk","license": "MIT OR Apache-2.0","keywords": ["git", "worktree", "codex", "agent"],"skills": "./skills/",- "hooks": "./hooks/hooks.json","interface": {"displayName": "Worktrunk","shortDescription": "Git worktree workflows for parallel Codex sessions.",- "longDescription": "Use Worktrunk from Codex to manage linked worktrees, set up LLM commit workflows, configure hooks, and bundle activity markers for wt list.",+ "longDescription": "Use Worktrunk from Codex to manage linked worktrees, set up LLM commit workflows, and configure project hooks.","developerName": "Worktrunk","category": "Productivity","capabilities": ["Interactive", "Write"],- "websiteURL": "https://worktrunk.dev/claude-code/"+ "websiteURL": "https://worktrunk.dev"}}diff --git a/plugins/worktrunk/hooks/hooks.json b/plugins/worktrunk/hooks/hooks.jsondeleted file mode 100644index f99a09e1d..000000000--- a/plugins/worktrunk/hooks/hooks.json+++ /dev/null@@ -1,34 +0,0 @@-{- "hooks": {- "SessionStart": [- {- "hooks": [- {- "type": "command",- "command": "wt config state marker set \"💬\" >/dev/null 2>&1 || true"- }- ]- }- ],- "UserPromptSubmit": [- {- "hooks": [- {- "type": "command",- "command": "wt config state marker set \"🤖\" >/dev/null 2>&1 || true"- }- ]- }- ],- "Stop": [- {- "hooks": [- {- "type": "command",- "command": "wt config state marker set \"💬\" >/dev/null 2>&1 || true"- }- ]- }- ]- }-}diff --git a/skills/worktrunk/reference/claude-code.md b/skills/worktrunk/reference/claude-code.mdindex bb4792826..82862d397 100644--- a/skills/worktrunk/reference/claude-code.md+++ b/skills/worktrunk/reference/claude-code.md@@ -1,16 +1,14 @@# Claude Code & Codex Integration-Worktrunk ships plugins for Claude Code and Codex. Both bundle:--1. **Configuration skill** — Documentation the agent can read, so it can help set up LLM commits, hooks, and troubleshoot issues-2. **Activity tracking** — Status markers in `wt list` showing which worktrees have active agent sessions (🤖 working, 💬 waiting)+Worktrunk ships plugins for Claude Code and Codex. Both bundle a **configuration skill** — documentation the agent can read, so it can help set up LLM commits, hooks, and troubleshoot issues.The Claude Code plugin additionally provides:-3. **Worktree isolation** — Routes agent-created isolated worktrees through `wt switch --create` / `wt remove` instead of raw `git`-4. **`/wt-switch-create` command** — Creates a worktrunk worktree and moves the current Claude session into it+1. **Activity tracking** — Status markers in `wt list` showing which worktrees have active agent sessions (🤖 working, 💬 waiting)+2. **Worktree isolation** — Routes agent-created isolated worktrees through `wt switch --create` / `wt remove` instead of raw `git`+3. **`/wt-switch-create` command** — Creates a worktrunk worktree and moves the current Claude session into it-Codex does not currently expose equivalent worktree-lifecycle hooks, so Codex users invoke `wt switch --create` and `wt remove` directly.+Codex exposes no turn-end or worktree-lifecycle hooks, so the Codex plugin ships only the configuration skill.## Installation@@ -39,9 +37,7 @@ This configures the Worktrunk marketplace in Codex. Then run `/plugins` in Codexcodex plugin marketplace add max-sixty/worktrunk```-To remove the marketplace entry, run `wt config plugins codex uninstall`. Already-installed plugins and global Codex hook feature flags are left unchanged.--If activity markers do not appear after installing the plugin, Codex may be gating plugin-bundled hooks. Run `codex features list`; if `plugin_hooks` is `false`, enable it (`codex features enable plugin_hooks`), or copy this repo's `plugins/worktrunk/hooks/hooks.json` to `~/.codex/hooks.json`.+To remove the marketplace entry, run `wt config plugins codex uninstall`. Already-installed plugins are left unchanged.## Configuration skill@@ -54,9 +50,9 @@ The plugin includes a skill — documentation the agent can read — covering WoClaude Code is designed to load the skill automatically when it detects worktrunk-related questions.-## Activity tracking+## Activity tracking (Claude Code only)-The plugins track agent sessions with status markers in `wt list`:+The Claude Code plugin tracks Claude sessions with status markers in `wt list`:```bash$ wt list@@ -72,7 +68,7 @@ $ wt list- 🤖 — agent is working- 💬 — agent is waiting or idle-The Claude Code plugin clears the marker when a session ends; Codex exposes no session-end hook event, so a Codex worktree rests at 💬 after its session ends rather than clearing. Either plugin can also leave a stale marker if the agent process is killed before its stop hook runs. `wt config state marker clear` removes a marker manually.+The plugin clears the marker when a session ends. A stale marker can remain if the Claude process is killed before its stop hook runs; `wt config state marker clear` removes a marker manually.### Manual status markersdiff --git a/src/cli/config.rs b/src/cli/config.rsindex be99de3b1..590291e5a 100644--- a/src/cli/config.rs+++ b/src/cli/config.rs@@ -209,7 +209,7 @@ This does not install the plugin by itself. Afterward, open `/plugins` in Codex$ codex plugin marketplace remove worktrunk```-This leaves any already-installed Worktrunk plugin and global Codex hook feature flags unchanged."#+This leaves any already-installed Worktrunk plugin unchanged."#)]Uninstall,}@@ -272,9 +272,7 @@ $ wt config plugins claude install-statusline/// Codex plugin#[command(- after_long_help = r#"Bundled activity hooks — can show status markers in `wt list` when Codex loads plugin hooks:-- 🤖 — Codex is working-- 💬 — Codex is waiting or idle+ after_long_help = r#"Bundles a configuration skill — documentation Codex can read to help set up LLM commits, project hooks, and worktree paths. Activity markers in `wt list` are Claude Code only: Codex exposes no turn-end hook event, so the Codex plugin omits them until it does.## Examples@@ -575,7 +573,7 @@ $ wt config alias dry-run deploy -- --env=staging## Supported tools- **claude** — Claude Code plugin (activity tracking + statusline)-- **codex** — Codex plugin (Worktrunk skill + bundled activity hooks)+- **codex** — Codex plugin (Worktrunk configuration skill)- **opencode** — OpenCode plugin (activity tracking)## Examplesdiff --git a/src/commands/config/codex.rs b/src/commands/config/codex.rsindex 7b0372591..d07b748a2 100644--- a/src/commands/config/codex.rs+++ b/src/commands/config/codex.rs@@ -44,16 +44,11 @@ pub fn handle_codex_install(yes: bool) -> Result<()> {"{}",hint_message("Next, run /plugins in Codex and install Worktrunk from the marketplace"));- eprintln!(- "{}",- hint_message("Activity markers (🤖/💬) use Codex plugin-bundled hooks")- );- eprintln!(- "{}",- hint_message(- "If markers do not appear, enable Codex plugin hooks or copy plugins/worktrunk/hooks/hooks.json to a standard Codex hook location"- )- );+ // The Codex plugin deliberately ships no activity-marker hooks: Codex's+ // HookEventNameWire vocabulary (codex-cli 0.130.0) has no `Stop`/turn-end+ // event, so a 🤖 set on UserPromptSubmit could never return to 💬 within a+ // session. Re-add the hooks (and restore the marker hints + docs) once+ // Codex exposes a turn-end hook event. See CLAUDE.md → "Codex Plugin".Ok(())}@@ -94,10 +89,7 @@ pub fn handle_codex_uninstall(yes: bool) -> Result<()> {}eprintln!("{}", success_message("Codex marketplace removed"));- eprintln!(- "{}",- hint_message("Installed plugins and global Codex hook feature flags are left unchanged")- );+ eprintln!("{}", hint_message("Installed plugins are left unchanged"));Ok(())}diff --git a/tests/integration_tests/config_show.rs b/tests/integration_tests/config_show.rsindex 3ad681d70..d86a70082 100644--- a/tests/integration_tests/config_show.rs+++ b/tests/integration_tests/config_show.rs@@ -3557,14 +3557,45 @@ fn test_codex_plugin_metadata_is_valid_json() {&fs::read_to_string(project_root.join(".agents/plugins/marketplace.json")).unwrap(),).unwrap();- let hooks: serde_json::Value = serde_json::from_str(- &fs::read_to_string(project_root.join("plugins/worktrunk/hooks/hooks.json")).unwrap(),- )- .unwrap();assert_eq!(plugin["name"], "worktrunk");assert_eq!(plugin["skills"], "./skills/");- assert_eq!(plugin["hooks"], "./hooks/hooks.json");+ // Metadata must not drift back toward the Claude plugin: the Codex plugin+ // ships only the configuration skill, and its URLs are the canonical site+ // (not the `/claude-code/` doc slug).+ for key in ["description", "homepage"] {+ let val = plugin[key].as_str().unwrap();+ assert!(+ !val.contains("activity") && !val.contains("claude-code"),+ "plugin.json `{key}` regressed toward Claude/activity wording: {val}"+ );+ }+ let iface = &plugin["interface"];+ assert!(+ !iface["longDescription"]+ .as_str()+ .unwrap()+ .contains("activity"),+ "plugin.json interface.longDescription must not claim activity tracking"+ );+ assert!(+ !iface["websiteURL"]+ .as_str()+ .unwrap()+ .contains("claude-code"),+ "plugin.json interface.websiteURL must point at the canonical site"+ );+ // The Codex plugin ships no activity-marker hooks: Codex's+ // HookEventNameWire vocabulary (codex-cli 0.130.0) has no `Stop`/turn-end+ // event, so a 🤖 set on UserPromptSubmit could never return to 💬 within a+ // session. Keep the manifest free of a `hooks` key (and the hooks/ dir+ // absent) until Codex adds a turn-end hook event — see CLAUDE.md →+ // "Codex Plugin".+ assert_eq!(plugin.get("hooks"), None);+ assert!(+ !project_root.join("plugins/worktrunk/hooks").exists(),+ "plugins/worktrunk/hooks/ must not exist while Codex lacks a turn-end hook event"+ );assert_eq!(marketplace["plugins"][0]["name"], "worktrunk");// Source is a non-empty subdir object; a bare "./" is rejected by codex.assert_eq!(marketplace["plugins"][0]["source"]["source"], "local");@@ -3579,14 +3610,6 @@ fn test_codex_plugin_metadata_is_valid_json() {// Codex validates `interface` is an object and requires `displayName`;// omitting it is what made the plugin undiscoverable in /plugins.assert_eq!(marketplace["interface"]["displayName"], "Worktrunk");- assert_eq!(- hooks["hooks"]["UserPromptSubmit"][0]["hooks"][0]["command"],- "wt config state marker set \"🤖\" >/dev/null 2>&1 || true"- );- assert_eq!(- hooks["hooks"]["Stop"][0]["hooks"][0]["command"],- "wt config state marker set \"💬\" >/dev/null 2>&1 || true"- );}// ==================== Plugin Install-Statusline Tests ====================diff --git a/tests/snapshots/integration__integration_tests__config_show__plugins_codex_install.snap b/tests/snapshots/integration__integration_tests__config_show__plugins_codex_install.snapindex 2cffee68a..91ebeb67b 100644--- a/tests/snapshots/integration__integration_tests__config_show__plugins_codex_install.snap+++ b/tests/snapshots/integration__integration_tests__config_show__plugins_codex_install.snap@@ -61,5 +61,3 @@ exit_code: 0[36m◎[39m [36mAdding Codex plugin marketplace...[39m[32m✓[39m [32mCodex marketplace configured[39m[2m↳[22m [2mNext, run /plugins in Codex and install Worktrunk from the marketplace[22m-[2m↳[22m [2mActivity markers (🤖/💬) use Codex plugin-bundled hooks[22m-[2m↳[22m [2mIf markers do not appear, enable Codex plugin hooks or copy plugins/worktrunk/hooks/hooks.json to a standard Codex hook location[22mdiff --git a/tests/snapshots/integration__integration_tests__config_show__plugins_codex_uninstall.snap b/tests/snapshots/integration__integration_tests__config_show__plugins_codex_uninstall.snapindex d25091d13..c13b8cc5a 100644--- a/tests/snapshots/integration__integration_tests__config_show__plugins_codex_uninstall.snap+++ b/tests/snapshots/integration__integration_tests__config_show__plugins_codex_uninstall.snap@@ -14,13 +14,19 @@ info:COLUMNS: "500"GIT_AUTHOR_DATE: "2025-01-01T00:00:00Z"GIT_COMMITTER_DATE: "2025-01-01T00:00:00Z"+ GIT_COMMON_DIR: ""GIT_CONFIG_GLOBAL: "[TEST_GIT_CONFIG]"GIT_CONFIG_SYSTEM: /dev/null- GIT_PAGER: ""+ GIT_DIR: ""+ GIT_EDITOR: ""+ GIT_INDEX_FILE: ""+ GIT_OBJECT_DIRECTORY: ""GIT_TERMINAL_PROMPT: "0"+ GIT_WORK_TREE: ""HOME: "[TEST_HOME]"LANG: CLC_ALL: C+ LLVM_PROFILE_FILE: "[LLVM_PROFILE_FILE]"MOCK_CONFIG_DIR: "[MOCK_CONFIG_DIR]"NO_COLOR: ""OPENCODE_CONFIG_DIR: "[TEST_OPENCODE_CONFIG]"@@ -33,14 +39,18 @@ info:WORKTRUNK_APPROVALS_PATH: "[TEST_APPROVALS]"WORKTRUNK_CONFIG_PATH: "[TEST_CONFIG]"WORKTRUNK_SYSTEM_CONFIG_PATH: "[TEST_SYSTEM_CONFIG]"+ WORKTRUNK_TEST_BASH_INSTALLED: "0"WORKTRUNK_TEST_CLAUDE_INSTALLED: "0"WORKTRUNK_TEST_CODEX_INSTALLED: "1"WORKTRUNK_TEST_DELAYED_STREAM_MS: "-1"WORKTRUNK_TEST_EPOCH: "1735776000"+ WORKTRUNK_TEST_FISH_INSTALLED: "0"WORKTRUNK_TEST_NUSHELL_ENV: "0"WORKTRUNK_TEST_OPENCODE_INSTALLED: "0"WORKTRUNK_TEST_POWERSHELL_ENV: "0"+ WORKTRUNK_TEST_POWERSHELL_INSTALLED: "0"WORKTRUNK_TEST_SKIP_URL_HEALTH_CHECK: "1"+ WORKTRUNK_TEST_ZSH_INSTALLED: "0"XDG_CONFIG_HOME: "[TEST_CONFIG_HOME]"---success: true@@ -50,4 +60,4 @@ exit_code: 0----- stderr -----[36m◎[39m [36mRemoving Codex plugin marketplace...[39m[32m✓[39m [32mCodex marketplace removed[39m-[2m↳[22m [2mInstalled plugins and global Codex hook feature flags are left unchanged[22m+[2m↳[22m [2mInstalled plugins are left unchanged[22mdiff --git a/tests/snapshots/integration__integration_tests__help__help_config_plugins.snap b/tests/snapshots/integration__integration_tests__help__help_config_plugins.snapindex 416356ccb..319b01b3c 100644--- a/tests/snapshots/integration__integration_tests__help__help_config_plugins.snap+++ b/tests/snapshots/integration__integration_tests__help__help_config_plugins.snap@@ -9,25 +9,30 @@ info:env:CLICOLOR_FORCE: "1"COLUMNS: "500"- GIT_PAGER: ""+ GIT_EDITOR: ""LANG: CLC_ALL: C+ LLVM_PROFILE_FILE: /var/folders/v3/8k5q0_6j3_q6gl4h8czr66sh0000gn/T/wt-test-profraw/cov-%m_%p.profrawNO_COLOR: ""PSModulePath: ""RUST_LOG: warnSHELL: ""TERM: alacritty- WORKTRUNK_APPROVALS_PATH: /nonexistent/test/approvals.toml- WORKTRUNK_CONFIG_PATH: /nonexistent/test/config.toml+ WORKTRUNK_APPROVALS_PATH: /nonexistent/wt/approvals.toml+ WORKTRUNK_CONFIG_PATH: /nonexistent/wt/config.tomlWORKTRUNK_SYSTEM_CONFIG_PATH: /etc/xdg/worktrunk/config.toml+ WORKTRUNK_TEST_BASH_INSTALLED: "0"WORKTRUNK_TEST_CLAUDE_INSTALLED: "0"WORKTRUNK_TEST_CODEX_INSTALLED: "0"WORKTRUNK_TEST_DELAYED_STREAM_MS: "-1"WORKTRUNK_TEST_EPOCH: "1735776000"+ WORKTRUNK_TEST_FISH_INSTALLED: "0"WORKTRUNK_TEST_NUSHELL_ENV: "0"WORKTRUNK_TEST_OPENCODE_INSTALLED: "0"WORKTRUNK_TEST_POWERSHELL_ENV: "0"+ WORKTRUNK_TEST_POWERSHELL_INSTALLED: "0"WORKTRUNK_TEST_SKIP_URL_HEALTH_CHECK: "1"+ WORKTRUNK_TEST_ZSH_INSTALLED: "0"---success: trueexit_code: 0@@ -63,7 +68,7 @@ Install and manage Worktrunk plugins for AI coding tools.[1m[32mSupported tools[0m- [1mclaude[0m — Claude Code plugin (activity tracking + statusline)-- [1mcodex[0m — Codex plugin (Worktrunk skill + bundled activity hooks)+- [1mcodex[0m — Codex plugin (Worktrunk configuration skill)- [1mopencode[0m — OpenCode plugin (activity tracking)[1m[32mExamples[0mdiff --git a/tests/snapshots/integration__integration_tests__help__help_config_plugins_codex.snap b/tests/snapshots/integration__integration_tests__help__help_config_plugins_codex.snapindex a75c941e9..114d8491a 100644--- a/tests/snapshots/integration__integration_tests__help__help_config_plugins_codex.snap+++ b/tests/snapshots/integration__integration_tests__help__help_config_plugins_codex.snap@@ -10,25 +10,30 @@ info:env:CLICOLOR_FORCE: "1"COLUMNS: "500"- GIT_PAGER: ""+ GIT_EDITOR: ""LANG: CLC_ALL: C+ LLVM_PROFILE_FILE: /var/folders/v3/8k5q0_6j3_q6gl4h8czr66sh0000gn/T/wt-test-profraw/cov-%m_%p.profrawNO_COLOR: ""PSModulePath: ""RUST_LOG: warnSHELL: ""TERM: alacritty- WORKTRUNK_APPROVALS_PATH: /nonexistent/test/approvals.toml- WORKTRUNK_CONFIG_PATH: /nonexistent/test/config.toml+ WORKTRUNK_APPROVALS_PATH: /nonexistent/wt/approvals.toml+ WORKTRUNK_CONFIG_PATH: /nonexistent/wt/config.tomlWORKTRUNK_SYSTEM_CONFIG_PATH: /etc/xdg/worktrunk/config.toml+ WORKTRUNK_TEST_BASH_INSTALLED: "0"WORKTRUNK_TEST_CLAUDE_INSTALLED: "0"WORKTRUNK_TEST_CODEX_INSTALLED: "0"WORKTRUNK_TEST_DELAYED_STREAM_MS: "-1"WORKTRUNK_TEST_EPOCH: "1735776000"+ WORKTRUNK_TEST_FISH_INSTALLED: "0"WORKTRUNK_TEST_NUSHELL_ENV: "0"WORKTRUNK_TEST_OPENCODE_INSTALLED: "0"WORKTRUNK_TEST_POWERSHELL_ENV: "0"+ WORKTRUNK_TEST_POWERSHELL_INSTALLED: "0"WORKTRUNK_TEST_SKIP_URL_HEALTH_CHECK: "1"+ WORKTRUNK_TEST_ZSH_INSTALLED: "0"---success: trueexit_code: 0@@ -58,9 +63,7 @@ Usage: [1m[36mwt config plugins codex[0m [36m[OPTIONS][0m [36m<COMMAND>[0[1m[36m-y[0m, [1m[36m--yes[0mSkip approval prompts-Bundled activity hooks — can show status markers in [2mwt list[0m when Codex loads plugin hooks:-- 🤖 — Codex is working-- 💬 — Codex is waiting or idle+Bundles a configuration skill — documentation Codex can read to help set up LLM commits, project hooks, and worktree paths. Activity markers in [2mwt list[0m are Claude Code only: Codex exposes no turn-end hook event, so the Codex plugin omits them until it does.[1m[32mExamples[0m