OMO teammode requires missing codex_app thread tools on Codex CLI 0.144.1

[ashmoonori-afk]

Summary

$omo:teammode cannot currently be used in Codex CLI 0.144.1 because the OMO teammode skill still requires legacy codex_app.* thread tools, but the current local Codex app tool surface exposes no codex_app namespace and none of the required thread tools.

The user-visible result is that teammode can load and its helper script runs, but Codex cannot create/bind durable team members because codex_app.create_thread, codex_app.read_thread, codex_app.send_message_to_thread, codex_app.set_thread_title, and codex_app.set_thread_archived are unavailable.

Environment

• LazyCodex / OMO version: omo@sisyphuslabs 4.16.2
• Latest LazyCodex source checked: 132a61da36e2, latest tag v4.16.2
• Codex version: codex-cli 0.144.1
• Latest upstream Codex source checked: 1f0566d3f592
• OS: Windows, Git Bash on native Windows
• Auth mode: ChatGPT auth
• Install method: npm global package @openai/codex@0.144.1
• Relevant config/features:
  • apps stable true
  • multi_agent stable true
  • enable_mcp_apps under development false
  • remote_control removed false

Repository Decision

• Target repository: code-yeongyu/lazycodex
• Why this belongs there: The failing contract is in the LazyCodex/OMO teammode skill and hook. Upstream Codex 0.144.1 has an app-server / remote-control surface, but the agent-visible tool namespace required by OMO teammode is not present locally. This is a LazyCodex compatibility/integration issue unless upstream reintroduces those exact agent tools.
• LazyCodex evidence:
  • Installed OMO is 4.16.2, matching latest source plugins/omo/.codex-plugin/plugin.json.
  • Installed and latest plugins/omo/skills/teammode/SKILL.md require codex_app.create_thread for every member.
  • The teammode hook matcher is still ^(create_thread|codex_app\\.create_thread)$.
  • components/teammode/src/codex-hook.ts still uses CREATE_THREAD_TOOL_NAMES = new Set(["create_thread", "codex_app.create_thread"]) and tells Codex to call codex_app.set_thread_title.
• Upstream Codex evidence:
  • codex --help still exposes experimental app-server and remote-control commands.
  • codex features list reports multi_agent stable true, but the current agent app-tool cache has no codex_app namespace and no thread-control tools.

Reproduction

1. In a Codex CLI 0.144.1 session with OMO 4.16.2 installed, ask Codex to use $omo:teammode.
2. Load the teammode skill. It requires durable members created with codex_app.create_thread.
3. Inspect available tools / local app tool cache.

Observed cache evidence:

cache_file=20adcd02af5127639e5ba2177d51c567cece6433.json
tool_count=173
namespaces=codex_apps__bethem,codex_apps__codex_document_control,codex_apps__github,codex_apps__gmail,codex_apps__hotline,codex_apps__notion,codex_apps__sites
has_codex_app_namespace=false
wanted_thread_tools_count=0

The missing required tools are:

codex_app.create_thread
codex_app.read_thread
codex_app.send_message_to_thread
codex_app.set_thread_title
codex_app.set_thread_archived

Expected Behavior

$omo:teammode should either:

1. create durable cooperating Codex member threads using the currently supported Codex app-server / thread API, or
2. detect that the required thread-control surface is unavailable and fail early with a clear fallback path.

Actual Behavior

The skill requires tools that are not available in the current Codex session. The helper script can run, and normal Codex execution works, but teammode cannot create real durable members.

Runtime sanity check:

codex_version=codex-cli 0.144.1
npm_latest=0.144.1
exec_probe
exit=0
codex
ok

codex doctor --json also reported codexVersion="0.144.1" and overallStatus=warning; the warning was unrelated rollout-store hygiene, not a failed install.

Evidence

Hypotheses investigated:

1. Installation is corrupted.
   • Refuted: codex exec --skip-git-repo-check --sandbox read-only "Say ONLY: ok" returned exit 0 and ok.
   • Refuted: codex doctor showed no install/auth/connectivity failure relevant to this symptom.
2. Local OMO is stale.
   • Refuted: installed OMO is 4.16.2, matching latest LazyCodex source and latest tag v4.16.2.
3. Codex 0.144.1 no longer exposes the agent-visible codex_app.* thread tools expected by teammode.
   • Confirmed: app tool cache contains 173 tools, no codex_app namespace, and 0 exact required thread tools.

Source references observed locally:

C:/Users/lg/.codex/plugins/cache/sisyphuslabs/omo/4.16.2/skills/teammode/SKILL.md:93
C:/Users/lg/.codex/plugins/cache/sisyphuslabs/omo/4.16.2/skills/teammode/SKILL.md:123
C:/Users/lg/.codex/plugins/cache/sisyphuslabs/omo/4.16.2/components/teammode/src/codex-hook.ts:26
C:/Users/lg/.codex/plugins/cache/sisyphuslabs/omo/4.16.2/hooks/post-tool-use-checking-thread-title-hygiene.json:5

Duplicate searches returned no open matches:

gh issue list --repo code-yeongyu/lazycodex --search "teammode codex_app create_thread" --state open
gh issue list --repo code-yeongyu/lazycodex --search "codex_app" --state open
gh issue list --repo openai/codex --search "codex_app create_thread remote_control" --state open

Root Cause

OMO teammode still encodes the old codex_app.* durable-thread contract, but the current Codex CLI 0.144.1 agent-visible app tool surface does not expose that namespace or those exact thread tools. The installed plugin is current, so reinstalling the same Codex/OMO versions does not restore the missing tools.

Proposed Fix

Update OMO teammode to support the current Codex thread/control surface, or fail early with an actionable compatibility message.

Likely files/components:

• plugins/omo/skills/teammode/SKILL.md
• plugins/omo/components/teammode/src/codex-hook.ts
• plugins/omo/components/teammode/hooks/hooks.json
• plugins/omo/skills/teammode/scripts/team.mjs

Suggested implementation path:

1. Detect whether codex_app.* thread tools are present before requiring team creation.
2. If they are present, keep the existing durable-thread flow.
3. If they are absent but a supported app-server / remote-control thread API is available, adapt team member creation, message sending, reading, title setting, and archival to that API.
4. If neither surface is available, emit a clear incompatibility message and recommend multi_agent_v1.spawn_agent only as a non-durable fallback, not as teammode.

Verification Plan

• On Codex CLI 0.144.1 with OMO 4.16.2+, run $omo:teammode and confirm it no longer requests unavailable codex_app.* tools.
• Confirm a team can create at least one durable member thread, bind it, read it, send it a message, and archive it.
• Confirm the current title hook still sets descriptive titles when the selected thread API supports title updates.
• Confirm the fallback path clearly reports unsupported durable teammode when no durable-thread API is available.
• Regression check: multi_agent_v1.spawn_agent should not be presented as equivalent to teammode, because it does not satisfy durable cross-thread communication.

---

This issue or PR was generated by LazyCodex.
Tag: lazycodex-generated