fix(teammode): degrade when thread tools are unavailable#102
Conversation
|
Thanks for the PR! Changes to LazyCodex land through oh-my-openagent — could you open this against omo-codex over there instead? PRs in this repository can't be merged. If you're working with a coding agent, prompt it like this:
|
There was a problem hiding this comment.
Pull request overview
This PR updates the teammode skill guidance so it only applies when the current Codex runtime exposes the durable thread tools it depends on, and adds a degraded “non-team” execution path so implementation requests can proceed even when thread tooling is unavailable.
Changes:
- Update
teammodeSKILL.md frontmatter + guidance to preflight required thread tools and degrade gracefully when missing. - Clarify the “real team members must be real Codex threads” invariant while avoiding “stop before any work” for ordinary implementation requests.
- Add a regression test that pins the presence of the new degraded-path guidance in the skill doc.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| plugins/omo/components/teammode/test/skill-tool-preflight.test.ts | Adds a doc-content regression test ensuring degraded-path guidance is present. |
| plugins/omo/components/teammode/skills/teammode/SKILL.md | Adds runtime tool preflight + degraded non-team guidance; updates strict thread-member rule and stop rules accordingly. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| - create a thread: `codex_app.create_thread` or `create_thread` | ||
| - send to a thread: `codex_app.send_message_to_thread` or equivalent thread-send tool | ||
| - read a thread: `codex_app.read_thread` or equivalent thread-read tool |
| --- | ||
| name: teammode | ||
| description: "Codex-only team orchestration: run a named team of cooperating Codex threads with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of threads/sessions, or to work on something as a team in parallel. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps, or when a task still needs exploration under a clear goal; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team, delete the team." | ||
| description: "Codex-only team orchestration: run a named team of cooperating Codex threads with durable, script-managed state. Use when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of threads/sessions, or to work on something as a team in parallel, but only when the current Codex runtime exposes the required thread tools. If create/read/send thread tools are unavailable, do not stop ordinary implementation work just because the user mentioned teammode; explain that durable Codex-thread teammode is unavailable in this surface and continue with the best available non-team workflow. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps, or when a task still needs exploration under a clear goal; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team, delete the team." | ||
| --- |
Summary
Fixes #101.
Verification
Summary by cubic
Degrades teammode to a non-team workflow when Codex thread tools are unavailable, so implementation continues instead of stopping, and preserves the rule that team members must be real Codex threads. Fixes #101.
SKILL.md: require create/read/send thread tools; if missing, explain unavailability and continue with the best non-team workflow (no fake teams, nomulti_agent_v1.spawn_agentas members).plugins/omo/components/teammode/test/skill-tool-preflight.test.tsto enforce the degraded guidance.Written for commit 58d3ba3. Summary will update on new commits.