oh-my-opencode 5.1.47 → 5.1.51

package/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lcx-contribute-bug-fix
-description: "Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect."
+description: "Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. LazyCodex-owned defects get a fork PR against code-yeongyu/oh-my-openagent (base dev, source-tree paths under packages/omo-codex/plugin, with the changelog fragment); upstream Codex bugs get a fork PR against openai/codex. code-yeongyu/lazycodex is a generated distribution mirror and never gets a PR. Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect."
 metadata:
   short-description: Contribute verified LazyCodex or Codex bug fixes
 ---
@@ -11,12 +11,12 @@ Use this skill to debug a concrete LazyCodex or Codex defect, implement the smal
 
 Route ownership the same way as `$lcx-report-bug`, but the deliverable differs by target:
 
-- `code-yeongyu/lazycodex` for LazyCodex, lazycodex-ai, omo-codex, bundled skills, hooks, MCP wiring, installer behavior, marketplace sync, docs, or packaging. Deliverable: a verified-fix issue with the patch embedded. NEVER open a PR or push a branch against this repo — its contents are regenerated from the source tree on every release, so PRs there cannot be merged and will be closed.
+- `code-yeongyu/oh-my-openagent` (base branch `dev`) for LazyCodex, lazycodex-ai, omo-codex, bundled skills, hooks, MCP wiring, installer behavior, marketplace sync, docs, or packaging. Deliverable: a PR from a fork that edits the source-tree paths under `packages/omo-codex/plugin/` and carries the changelog fragment that repo requires. `code-yeongyu/lazycodex` is a distribution mirror generated from it (its `plugins/omo/` tree is synced from `packages/omo-codex/plugin/`), and the maintainer lands LazyCodex fixes from PRs against oh-my-openagent. NEVER open a PR or push a branch against `code-yeongyu/lazycodex`: its contents are regenerated on every release, so a PR there cannot be merged and will be closed. At most file a short issue there (symptom plus failing input) that links the oh-my-openagent PR; never embed a patch.
 - `openai/codex` for upstream Codex CLI bugs that reproduce without LazyCodex or come from Codex core behavior. Deliverable: a PR from a fork.
 
 ## Required Outcome
 
-For `openai/codex`, create a fork PR that includes:
+For `code-yeongyu/oh-my-openagent` and `openai/codex`, create a fork PR that includes:
 
 - a focused branch from a fresh `${TMPDIR:-/tmp}` clone/worktree
 - reproduction logs from before the fix
@@ -24,22 +24,24 @@ For `openai/codex`, create a fork PR that includes:
 - verification logs from after the fix
 - apply `lazycodex-generated` when label management is available
 - the required LazyCodex footer tag `Tag: lazycodex-generated`
+- for `code-yeongyu/oh-my-openagent`: base `dev`, edits at `packages/omo-codex/plugin/...` (never the mirror's `plugins/omo/...` paths), and the changelog fragment `changes/unreleased/<pr-number>.md` that the repo's AGENTS.md describes
 - cleanup of temporary worktrees and clones
 
-For `code-yeongyu/lazycodex`, create an issue (never a PR) that includes:
-
-- reproduction logs from before the fix
-- the root cause with source evidence
-- the verified patch as a unified diff, produced and tested in a fresh `${TMPDIR:-/tmp}` clone/worktree
-- verification logs from after the fix
-- the `lazycodex-generated` label and the footer tag `Tag: lazycodex-generated`
-- cleanup of temporary worktrees and clones
+For `code-yeongyu/lazycodex`, deliver no PR and no patch. When a pointer is useful there, file a short issue (symptom plus failing input, the `lazycodex-generated` label and the footer tag `Tag: lazycodex-generated`) that links the oh-my-openagent PR.
 
 ## Required Workflow
 
 1. Read the user's bug report and identify the affected surface. Before commands, apply the bundled ultrawork directive’s Task resources and todo rules; read those sections if absent from context.
 2. Invoke `$omo:debugging` for the investigation. If only unqualified skill names are exposed, invoke `$debugging` and state that it is the OMO debugging skill.
-3. Materialize the latest sources under `LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}"`, then decide the target repository. Sync both checkouts on every run and compare them before choosing. Validate cached checkouts before reuse so an incomplete `.git` directory cannot route the fix to the wrong repo:
+3. Search for an existing lead PR before anything is filed. Search your own open PRs across all repos by the symptom or the changed symbol, then the target repo's open PRs, so a fix that already exists is found first and gets new evidence instead of a duplicate:
+
+```bash
+gh search prs --author @me --state open "<symbol or error text>"
+gh search prs --repo code-yeongyu/oh-my-openagent --state open "<symbol or error text>"
+```
+
+If a matching open PR exists, add evidence to it or report it instead of opening a second one.
+4. Materialize the latest sources under `LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}"`, then decide the target repository. Sync the checkouts on every run and compare them before choosing. Validate cached checkouts before reuse so an incomplete `.git` directory cannot route the fix to the wrong repo:
 
 ```bash
 # The default checkout cache is per-task under TMPDIR=$RUN_TMP.
@@ -85,12 +87,13 @@ sync_latest_source() {
   git -C "$DEST" checkout -B "$DEFAULT_BRANCH" FETCH_HEAD
 }
 sync_latest_source code-yeongyu/lazycodex "$LAZYCODEX_SOURCE_ROOT/lazycodex-source"
+sync_latest_source code-yeongyu/oh-my-openagent "$LAZYCODEX_SOURCE_ROOT/oh-my-openagent-source"
 sync_latest_source openai/codex "$LAZYCODEX_SOURCE_ROOT/chatgpt-subscription-source"
 ```
-4. Create a fresh temporary clone and branch under `${TMPDIR:-/tmp}`. Do not modify the user's current repository for the target fix unless the current repository is itself the requested target and the user explicitly asked for local edits. Apply those resource rules at clone/worktree creation.
+5. Create a fresh temporary clone and branch under `${TMPDIR:-/tmp}`. Do not modify the user's current repository for the target fix unless the current repository is itself the requested target and the user explicitly asked for local edits. Apply those resource rules at clone/worktree creation.
 
 ```bash
-TARGET_REPO="code-yeongyu/lazycodex" # or openai/codex
+TARGET_REPO="code-yeongyu/oh-my-openagent" # or openai/codex
 WORK_ROOT="${RUN_TMP:?apply ultrawork Task resources first}"
 gh repo clone "$TARGET_REPO" "$WORK_ROOT/repo" -- --depth=1
 cd "$WORK_ROOT/repo"
@@ -103,11 +106,11 @@ cd "$WORK_ROOT/worktree"
 
 If `gh` cannot clone, use `git clone --depth=1 "https://github.com/$TARGET_REPO" "$WORK_ROOT/repo"` and continue with the same worktree flow.
 
-5. Reproduce the bug in the worktree through the real surface. Save exact command output to `${TMPDIR:-/tmp}/lazycodex-fix-<short-slug>-repro.log`.
-6. Write or update a failing regression test before production changes. Confirm it fails for the bug, not for a missing fixture or typo.
-7. Implement the smallest correct fix. Avoid refactors unless the fix cannot be made safely without one.
-8. Run the regression test, adjacent tests, and the smallest real-surface QA command that proves the user-visible behavior changed.
-9. Commit the verified fix in the worktree. Inspect the status first so the delivered diff cannot be empty or stale:
+6. Reproduce the bug in the worktree through the real surface. Save exact command output to `${TMPDIR:-/tmp}/lazycodex-fix-<short-slug>-repro.log`.
+7. Write or update a failing regression test before production changes. Confirm it fails for the bug, not for a missing fixture or typo.
+8. Implement the smallest correct fix. Avoid refactors unless the fix cannot be made safely without one.
+9. Run the regression test, adjacent tests, and the smallest real-surface QA command that proves the user-visible behavior changed.
+10. Commit the verified fix in the worktree. Inspect the status first so the delivered diff cannot be empty or stale:
 
 ```bash
 git status --short
@@ -116,16 +119,11 @@ git commit -m "fix: <short bug-fix summary>"
 git log --oneline "origin/$BASE_BRANCH..HEAD"
 ```
 
-10. Build the delivery body for the target:
-   - `openai/codex`: generate the PR body with `scripts/create-pr-body.mjs`.
-   - `code-yeongyu/lazycodex`: export the verified patch and write the issue body from the Verified-Fix Issue Template below:
-
-```bash
-PATCH_FILE="${TMPDIR:-/tmp}/lazycodex-fix-<short-slug>.patch"
-git diff "origin/$BASE_BRANCH"..HEAD > "$PATCH_FILE"
-```
+11. Build the delivery body for the target:
+   - `code-yeongyu/oh-my-openagent` and `openai/codex`: generate the PR body with `scripts/create-pr-body.mjs` (set `targetRepository` to the repo you are filing against).
+   - `code-yeongyu/oh-my-openagent` only: add the changelog fragment `changes/unreleased/<pr-number>.md` once the PR number exists, in the format `docs/reference/changelog-fragments.md` of that repo defines, and commit it to the same branch.
 
-11. Ensure the generated label exists when the target repo allows label management. Keep the footer tag even when label creation is unavailable:
+12. Ensure the generated label exists when the target repo allows label management. Keep the footer tag even when label creation is unavailable:
 
 ```bash
 LABEL_ARGS=()
@@ -136,8 +134,17 @@ else
 fi
 ```
 
-12. Deliver the fix.
-   - `code-yeongyu/lazycodex`: create the verified-fix issue. Never push a branch to this repo and never run `gh pr create` against it:
+13. Deliver the fix.
+   - `code-yeongyu/oh-my-openagent`: fork, push the branch to the fork, and create the PR against base `dev`. Never push a branch to or run `gh pr create` against `code-yeongyu/lazycodex`:
+
+```bash
+gh repo fork code-yeongyu/oh-my-openagent --remote --remote-name fork
+GH_USER="$(gh api user --jq .login)"
+git push -u fork "$BRANCH_NAME"
+gh pr create --repo code-yeongyu/oh-my-openagent --base dev --head "$GH_USER:$BRANCH_NAME" --title "<short fix title>" "${LABEL_ARGS[@]}" --body-file "$PR_BODY"
+```
+
+   - `code-yeongyu/lazycodex` (optional pointer): a short issue with the symptom, the failing input and a link to the oh-my-openagent PR, never a diff:
 
 ```bash
 ISSUE_BODY="${TMPDIR:-/tmp}/lazycodex-fix-<short-slug>-issue.md"
@@ -153,7 +160,7 @@ git push -u fork "$BRANCH_NAME"
 gh pr create --repo openai/codex --base "$BASE_BRANCH" --head "$GH_USER:$BRANCH_NAME" --title "<short fix title>" "${LABEL_ARGS[@]}" --body-file "$PR_BODY"
 ```
 
-13. Finish cleanup per Task resources. Run this only when that rule permits removing the worktree and run root; otherwise retain them and report the outstanding cleanup todo:
+14. Finish cleanup per Task resources. Run this only when that rule permits removing the worktree and run root; otherwise retain them and report the outstanding cleanup todo:
 
 ```bash
 cd /
@@ -166,34 +173,22 @@ test ! -e "$WORK_ROOT" && printf 'cleanup: worktree and caches REMOVED\n'
 
 Return the PR or issue URL, the reproduction command, the verification command, and the cleanup receipt.
 
-## Verified-Fix Issue Template (code-yeongyu/lazycodex)
+## Pointer Issue Template (code-yeongyu/lazycodex, optional)
 
-Write the issue body in English. Embed the patch verbatim so a maintainer can apply it to the source tree:
+Write the issue body in English. It names the symptom and the failing input and links the oh-my-openagent PR; the fix itself lives in that PR:
 
 ````markdown
-## Problem Situation
+## Symptom
 [What failed for the user.]
 
-## Reproduction Logs
-[Exact failing command and relevant log excerpt.]
-
-## Root Cause
-[Confirmed cause with runtime and source evidence.]
+## Failing Input
+[Exact failing command and the shortest log excerpt.]
 
-## Verified Fix
-[What changed and why this is the smallest correct fix.]
-
-```diff
-[Contents of $PATCH_FILE.]
-```
-
-## Verification
-- [RED test output or repro before the fix]
-- [GREEN test output after the fix]
-- [Manual QA command and result]
+## Fix
+[Link to the code-yeongyu/oh-my-openagent PR.]
 
 ---
-This fix was debugged, implemented, and verified with [LazyCodex](https://github.com/code-yeongyu/lazycodex).
+This issue was generated by LazyCodex.
 Tag: lazycodex-generated
 ````
 
@@ -267,10 +262,11 @@ Stop and ask one narrow question only when:
 
 Do not open:
 
-- a PR or pushed branch targeting `code-yeongyu/lazycodex` — deliver the verified-fix issue instead, always
-- a PR or verified-fix issue without a failing-before and passing-after test
-- a PR or verified-fix issue without a real-surface QA command
+- a PR or pushed branch targeting `code-yeongyu/lazycodex` — send the fix as a PR against `code-yeongyu/oh-my-openagent` instead, always
+- a PR for a defect that already has an open lead PR found by the search in step 3
+- a PR without a failing-before and passing-after test
+- a PR without a real-surface QA command
 - a PR or issue without the `Tag: lazycodex-generated` footer
-- a verified-fix issue without the patch embedded in a `diff` block
+- an issue on `code-yeongyu/lazycodex` that embeds a patch
 - a vague fix that does not identify the root cause
 - a broad refactor disguised as a bug fix

package/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix/agents/openai.yaml

@@ -9,4 +9,4 @@ interface:
     - "lazycodex fix"
     - "omo-codex bug fix"
     - "codex bug fix pr"
-  default_prompt: "Use $lcx-contribute-bug-fix to debug this LazyCodex or Codex bug, work from a fresh ${TMPDIR:-/tmp} clone and worktree, implement the smallest verified fix, apply the lazycodex-generated label, deliver it (verified-fix issue on code-yeongyu/lazycodex — never a PR there; fork PR only for openai/codex), and clean up."
+  default_prompt: "Use $lcx-contribute-bug-fix to debug this LazyCodex or Codex bug, search my open PRs for an existing lead PR first, work from a fresh ${TMPDIR:-/tmp} clone and worktree, implement the smallest verified fix, apply the lazycodex-generated label, deliver it as a fork PR (code-yeongyu/oh-my-openagent base dev for LazyCodex defects, openai/codex for upstream; never a PR on the code-yeongyu/lazycodex mirror), and clean up."

package/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug/SKILL.md

@@ -9,8 +9,8 @@ metadata:
 
 You are a LazyCodex bug router and reporter. Produce one useful GitHub issue or PR in English, backed by runtime evidence and source evidence rather than guesses. Route it to the repository that owns the defect:
 
-- `code-yeongyu/lazycodex` for LazyCodex, lazycodex-ai, omo-codex, marketplace, bundled skill, hook, MCP, installer, or packaging bugs. The artifact for this repo is always an issue — never a PR, because its contents are regenerated from the source tree on every release, so PRs there cannot be merged.
-- `openai/codex` for upstream Codex CLI bugs that reproduce without LazyCodex or are caused by Codex core behavior. This is the only repo where this skill may create a PR.
+- `code-yeongyu/lazycodex` for LazyCodex, lazycodex-ai, omo-codex, marketplace, bundled skill, hook, MCP, installer, or packaging bugs. The artifact for this repo is always an issue, never a PR: it is a distribution mirror generated from `code-yeongyu/oh-my-openagent` (its `plugins/omo/` tree is synced from `packages/omo-codex/plugin/`), so PRs there cannot be merged. A fix for these defects goes to `code-yeongyu/oh-my-openagent` as a fork PR (base `dev`, source-tree paths, changelog fragment) through `$lcx-contribute-bug-fix`; the mirror issue stays short and links that PR.
+- `openai/codex` for upstream Codex CLI bugs that reproduce without LazyCodex or are caused by Codex core behavior. A PR may be created here.
 
 Use GPT-5.5 style: outcome first, concise, evidence-bound. Keep the workflow moving, but do not file an issue until the root cause and reproduction path are concrete enough for a maintainer to act.
 
@@ -90,7 +90,7 @@ sync_latest_source openai/codex "$LAZYCODEX_SOURCE_ROOT/chatgpt-subscription-sou
    - Use `code-yeongyu/lazycodex` when the bug is in LazyCodex integration, distribution, bundled plugin code, skills, hooks, MCP wiring, installer behavior, aliases, marketplace sync, docs, or any behavior that disappears in clean upstream Codex.
    - Use `openai/codex` when the bug reproduces in clean upstream Codex without LazyCodex, or the failing behavior comes from Codex CLI core, plugin API contracts, sandboxing, approvals, config loading, or built-in tool behavior.
    - If ownership remains ambiguous after evidence gathering, do not guess. Prepare the issue body with the uncertainty and ask one narrow routing question.
-7. Search for an existing issue in the selected repo before creating a new one. Search the other repo too when the ownership boundary is close:
+7. Search for an existing issue or lead PR before creating anything new. Search your own open PRs across all repos first (`gh search prs --author @me --state open "<symbol or error text>"`), then the selected repo, and the other repo too when the ownership boundary is close:
 
 ```bash
 TARGET_REPO="code-yeongyu/lazycodex" # or openai/codex
@@ -111,7 +111,7 @@ fi
 
 If the selected repo is `openai/codex` and label management is not available, still include the footer tag in the body and continue without claiming label creation succeeded.
 10. If no matching issue exists, create the issue with `gh` and apply the `lazycodex-generated` label.
-11. Create a PR only when the target repo is `openai/codex` AND the user asked for a PR, the fix is already implemented on a branch, or the smallest correct fix can be safely made there. Never create a PR or push a branch against `code-yeongyu/lazycodex` — always file an issue there, embedding the verified patch in the Proposed Fix section when one exists. Apply the `lazycodex-generated` label to every PR created by this skill. Otherwise create an issue with fix guidance.
+11. Create a PR only when the target repo is `openai/codex` or `code-yeongyu/oh-my-openagent` (the source of the LazyCodex mirror, base `dev`) AND the user asked for a PR, the fix is already implemented on a branch, or the smallest correct fix can be safely made there; use `$lcx-contribute-bug-fix` for the fix workflow. Never create a PR or push a branch against `code-yeongyu/lazycodex`: file a short issue there (symptom and failing input) that links the oh-my-openagent PR, with no patch. Apply the `lazycodex-generated` label to every PR created by this skill. Otherwise create an issue with fix guidance.
 
 ## Required Label And Footer
 
@@ -176,7 +176,7 @@ Tag: lazycodex-generated
 
 ## PR Body Template
 
-Use this only when a PR is the right artifact, which is only ever for `openai/codex`:
+Use this only when a PR is the right artifact, which is only ever for `openai/codex` or `code-yeongyu/oh-my-openagent`:
 
 ```markdown
 ## Summary
@@ -226,7 +226,7 @@ if [ "${#LABEL_ARGS[@]}" -gt 0 ]; then
 fi
 ```
 
-For a PR from a branch pushed to a fork — `openai/codex` only, never `code-yeongyu/lazycodex`:
+For a PR from a branch pushed to a fork, against `openai/codex` or `code-yeongyu/oh-my-openagent` (never `code-yeongyu/lazycodex`):
 
 ```bash
 PR_BODY="${TMPDIR:-/tmp}/lcx-report-bug-pr-$(date +%Y%m%d-%H%M%S).md"
@@ -259,7 +259,7 @@ Stop and ask one narrow question only when the missing fact changes the issue ma
 
 Do not file:
 
-- a PR or pushed branch targeting `code-yeongyu/lazycodex` — file the issue instead, always
+- a PR or pushed branch targeting `code-yeongyu/lazycodex` — send a fix PR to `code-yeongyu/oh-my-openagent` and keep any mirror issue short, always
 - a vague issue without reproduction steps
 - an issue that claims a root cause not supported by runtime evidence
 - a duplicate when commenting on an existing issue is enough

package/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug/agents/openai.yaml

@@ -8,4 +8,4 @@ interface:
     - "omo-codex bug"
     - "openai codex bug"
     - "codex upstream issue"
-  default_prompt: "Use $lcx-report-bug to investigate this LazyCodex or Codex bug, compare LazyCodex evidence with sources under LAZYCODEX_SOURCE_ROOT or ${TMPDIR:-/tmp}/lazycodex-sources, choose the correct GitHub repo, and file an issue (or, for openai/codex only, a PR — never a PR on code-yeongyu/lazycodex) with reproduction, root cause, fix guidance, and the lazycodex-generated label and footer."
+  default_prompt: "Use $lcx-report-bug to investigate this LazyCodex or Codex bug, compare LazyCodex evidence with sources under LAZYCODEX_SOURCE_ROOT or ${TMPDIR:-/tmp}/lazycodex-sources, choose the correct GitHub repo, and file an issue (or a PR on code-yeongyu/oh-my-openagent or openai/codex when the fix is ready — never a PR on the code-yeongyu/lazycodex mirror) with reproduction, root cause, fix guidance, and the lazycodex-generated label and footer."

package/packages/omo-codex/plugin/components/lsp/dist/.omo-runtime-manifest.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
-  "version": "5.1.47",
-  "inputDigest": "sha256:6cabf483e0820d8ebb42944ea3df97bedb1fcc9362a46f2659007ffa48225e10",
+  "version": "5.1.51",
+  "inputDigest": "sha256:39638ec3ebc26f2042f36d305d73e0414c185f68ab8cf5120a82774b425697ec",
   "outputs": [
     {
       "path": "cli.d.ts",

package/packages/omo-codex/plugin/components/lsp/hooks/hooks.json

@@ -8,7 +8,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
 						"timeout": 60,
-						"statusMessage": "(OmO 5.1.47) Checking LSP Diagnostics"
+						"statusMessage": "(OmO 5.1.51) Checking LSP Diagnostics"
 					}
 				]
 			}
@@ -21,7 +21,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-compact",
 						"timeout": 5,
-						"statusMessage": "(OmO 5.1.47) Resetting LSP Diagnostics Cache"
+						"statusMessage": "(OmO 5.1.51) Resetting LSP Diagnostics Cache"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/lsp/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@code-yeongyu/codex-lsp",
-	"version": "5.1.47",
+	"version": "5.1.51",
 	"description": "Codex plugin that exposes Language Server Protocol tools and post-edit diagnostics.",
 	"type": "module",
 	"packageManager": "npm@11.12.1",

package/packages/omo-codex/plugin/components/rules/hooks/hooks.json

@@ -7,7 +7,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook session-start",
 						"timeout": 10,
-						"statusMessage": "(OmO 5.1.47) Loading Project Rules"
+						"statusMessage": "(OmO 5.1.51) Loading Project Rules"
 					}
 				]
 			}
@@ -19,7 +19,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook user-prompt-submit",
 						"timeout": 10,
-						"statusMessage": "(OmO 5.1.47) Loading Project Rules"
+						"statusMessage": "(OmO 5.1.51) Loading Project Rules"
 					}
 				]
 			}
@@ -32,7 +32,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
 						"timeout": 10,
-						"statusMessage": "(OmO 5.1.47) Matching Project Rules"
+						"statusMessage": "(OmO 5.1.51) Matching Project Rules"
 					}
 				]
 			}
@@ -45,7 +45,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-compact",
 						"timeout": 10,
-						"statusMessage": "(OmO 5.1.47) Resetting Project Rule Cache"
+						"statusMessage": "(OmO 5.1.51) Resetting Project Rule Cache"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/rules/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@code-yeongyu/codex-rules",
-	"version": "5.1.47",
+	"version": "5.1.51",
 	"description": "Codex plugin that injects project rule files into model context through lifecycle hooks.",
 	"type": "module",
 	"packageManager": "npm@11.12.1",

package/packages/omo-codex/plugin/components/teammode/hooks/hooks.json

@@ -8,7 +8,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
 						"timeout": 10,
-						"statusMessage": "(OmO 5.1.47) Checking Thread Title Hygiene"
+						"statusMessage": "(OmO 5.1.51) Checking Thread Title Hygiene"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/teammode/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@sisyphuslabs/codex-teammode",
-	"version": "5.1.47",
+	"version": "5.1.51",
 	"description": "Codex team-mode hook component that keeps background thread titles descriptive after create_thread.",
 	"type": "module",
 	"private": true,
@@ -17,7 +17,7 @@
 	"devDependencies": {
 		"@vitest/coverage-v8": "5.0.1",
 		"@types/node": "^26.6.2",
-		"bun-types": "^1.4.3",
+		"bun-types": "1.4.4",
 		"typescript": "^7.0.2",
 		"vitest": "5.0.1"
 	},

package/packages/omo-codex/plugin/components/telemetry/README.md

@@ -2,7 +2,7 @@
 
 Codex plugin component that emits a single anonymous daily-active event (`omo_codex_daily_active`) to PostHog whenever a Codex session starts.
 
-The event is sent **at most once per UTC day per machine**. It uses a SHA256-hashed installation identifier derived from `omo-codex:${hostname}` and never sends the raw hostname. PostHog person profiles are explicitly disabled.
+The event is sent **at most once per UTC day per machine**. Its distinct id is `sha256` of a random install id created on the first send and stored as `install-id` in the telemetry state directory; nothing about the machine or user is used to build it. PostHog person profiles are explicitly disabled.
 
 ## Hook Wiring
 
@@ -33,7 +33,7 @@ The aggregate `plugin/hooks/hooks.json` mounts this hook alongside `rules` and `
 A single PostHog `capture` call with:
 
 - `event: "omo_codex_daily_active"`
-- `distinctId: sha256("omo-codex:" + hostname)`
+- `distinctId: sha256(install id)`
 - `properties`:
   - `platform`, `product_name`, `package_name`, `package_version`
   - `runtime` (`"node"`), `runtime_version`

package/packages/omo-codex/plugin/components/telemetry/dist/cli.js

@@ -464,14 +464,10 @@ function getTelemetryHost(env = process.env, defaultHost = DEFAULT_POSTHOG_HOST)
 }
 
 // ../../telemetry-core/src/machine-id.ts
-import { createHash } from "node:crypto";
 import os2 from "node:os";
 function getDefaultTelemetryOsProvider() {
   return os2;
 }
-function getTelemetryDistinctId(machineIdPrefix, osProvider = getDefaultTelemetryOsProvider()) {
-  return createHash("sha256").update(`${machineIdPrefix}${osProvider.hostname()}`).digest("hex");
-}
 
 // ../../telemetry-core/src/injected-client.ts
 var NO_OP_CLIENT = {
@@ -9714,26 +9710,72 @@ function createDefaultPostHogTransport(apiKey, options) {
   return new PostHogTelemetryTransport(apiKey, options);
 }
 
+// ../../telemetry-core/src/install-id.ts
+import { createHash, randomBytes } from "node:crypto";
+import { mkdirSync as mkdirSync5, readFileSync as readFileSync3, writeFileSync as writeFileSync2 } from "node:fs";
+import { dirname as dirname3, join as join4 } from "node:path";
+var TELEMETRY_INSTALL_ID_FILE_NAME = "install-id";
+var INSTALL_ID_PATTERN = /^[0-9a-f]{64}$/;
+var fallbackInstallIds = new Map;
+function getTelemetryInstallDistinctId(stateDir) {
+  return createHash("sha256").update(readOrCreateInstallId(join4(stateDir, TELEMETRY_INSTALL_ID_FILE_NAME))).digest("hex");
+}
+function readOrCreateInstallId(path) {
+  const persisted = readInstallId(path);
+  if (persisted !== undefined)
+    return persisted;
+  const installId = randomBytes(32).toString("hex");
+  try {
+    mkdirSync5(dirname3(path), { recursive: true });
+    writeFileSync2(path, `${installId}
+`, { flag: "wx", mode: 384 });
+    fallbackInstallIds.delete(path);
+    return installId;
+  } catch {
+    const concurrentlyCreated = readInstallId(path);
+    if (concurrentlyCreated !== undefined)
+      return concurrentlyCreated;
+    try {
+      writeFileSync2(path, `${installId}
+`, { flag: "w", mode: 384 });
+      fallbackInstallIds.delete(path);
+      return installId;
+    } catch {}
+    const fallback = fallbackInstallIds.get(path);
+    if (fallback !== undefined)
+      return fallback;
+    fallbackInstallIds.set(path, installId);
+    return installId;
+  }
+}
+function readInstallId(path) {
+  try {
+    const value = readFileSync3(path, "utf8").trim();
+    return INSTALL_ID_PATTERN.test(value) ? value : undefined;
+  } catch {
+    return;
+  }
+}
+
 // ../../telemetry-core/src/posthog-client.ts
 function createTelemetryClient2(input) {
   return createTelemetryClient({ ...input, transportFactory: input.transportFactory ?? createDefaultPostHogTransport });
 }
 
 // components/telemetry/src/product-identity.ts
-import { readFileSync as readFileSync3 } from "node:fs";
+import { readFileSync as readFileSync4 } from "node:fs";
 var PRODUCT_NAME = "omo-codex";
 var PACKAGE_NAME = "@oh-my-opencode/omo-codex";
 var CACHE_DIR_NAME = "omo-codex";
 var EVENT_NAME = "omo_codex_daily_active";
 var PRODUCT_ENV_PREFIX = "OMO_CODEX";
-var MACHINE_ID_PREFIX = "omo-codex:";
 function isComponentPackageManifest(value) {
   return value !== null && typeof value === "object" && !Array.isArray(value);
 }
 function readComponentVersionFromManifest() {
   try {
     const manifestUrl = new URL("../package.json", import.meta.url);
-    const manifestText = readFileSync3(manifestUrl, "utf-8");
+    const manifestText = readFileSync4(manifestUrl, "utf-8");
     const parsed = JSON.parse(manifestText);
     if (isComponentPackageManifest(parsed) && typeof parsed.version === "string") {
       return parsed.version;
@@ -9756,7 +9798,6 @@ function createComponentTelemetryProductConfig(additionalProperties) {
     defaultApiKey: DEFAULT_POSTHOG_API_KEY,
     defaultHost: DEFAULT_POSTHOG_HOST,
     eventName: EVENT_NAME,
-    machineIdPrefix: MACHINE_ID_PREFIX,
     packageName: PACKAGE_NAME,
     packageVersion: getComponentVersion(),
     platform: "omo-codex",
@@ -9835,14 +9876,14 @@ function createPluginPostHogClient(options = {}) {
   }
   const activityStateProvider = resolveActivityStateProvider(options);
   return {
-    trackActive: (distinctId, reason) => {
+    trackActive: (reason) => {
       const activityState = activityStateProvider();
       if (!activityState.captureDaily) {
         return;
       }
       client.trackActive({
         dayUTC: activityState.dayUTC,
-        distinctId,
+        distinctId: getTelemetryInstallDistinctId(options.stateDir ?? getComponentTelemetryStateDir()),
         reason
       });
     },
@@ -9854,9 +9895,6 @@ function createPluginPostHogClient(options = {}) {
 async function createPluginPostHog() {
   return createPluginPostHogClient();
 }
-function getPostHogDistinctId() {
-  return getTelemetryDistinctId(MACHINE_ID_PREFIX, getDefaultTelemetryOsProvider());
-}
 
 // components/telemetry/src/codex-hook.ts
 var SESSION_START_REASON = "session_start";
@@ -9870,7 +9908,6 @@ function writeHookDiagnostic(event, error, errorKind) {
 }
 async function runSessionStartHook(_input, options = {}) {
   const createClient = options.createClient ?? createPluginPostHog;
-  const getDistinctId = options.getDistinctId ?? getPostHogDistinctId;
   let client;
   try {
     client = await createClient();
@@ -9879,7 +9916,7 @@ async function runSessionStartHook(_input, options = {}) {
     return "";
   }
   try {
-    client.trackActive(getDistinctId(), SESSION_START_REASON);
+    client.trackActive(SESSION_START_REASON);
   } catch (error) {
     writeHookDiagnostic("telemetry_capture_failed", error, error instanceof Error ? "error" : "non_error");
     await safeShutdown(client);