oh-my-customcodex 0.4.5 → 0.4.7

package/dist/cli/index.js

@@ -3091,7 +3091,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.4.5",
+    version: "0.4.7",
     description: "Batteries-included agent harness on top of GPT Codex + OMX",
     type: "module",
     bin: {

package/dist/index.js

@@ -2180,7 +2180,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "0.4.5",
+  version: "0.4.7",
   description: "Batteries-included agent harness on top of GPT Codex + OMX",
   type: "module",
   bin: {

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "0.4.5",
+  "version": "0.4.7",
   "description": "Batteries-included agent harness on top of GPT Codex + OMX",
   "type": "module",
   "bin": {

package/templates/.claude/rules/MUST-agent-design.md

@@ -29,6 +29,9 @@ Extended context suffix: `[1m]` (e.g., `claude-opus-4-6[1m]`) — enables 1M tok
 
 ### Optional Frontmatter
 
+Key optional fields: `memory`, `effort`, `skills`, `soul`, `isolation`, `background`, `maxTurns`, `maxTokens`, `mcpServers`, `hooks`, `permissionMode`, `disallowedTools`, `limitations`, `domain`, `disableSkillShellExecution`. Supported since CC v2.1.63+. See full optional frontmatter via Read tool.
+
+<!-- DETAIL: Optional Frontmatter (full yaml block)
 ```yaml
 memory: project            # user | project | local
 effort: high               # low | medium | high | xhigh | default | max
@@ -64,8 +67,7 @@ disableSkillShellExecution: true  # Disable inline shell execution in skills (v2
 ```
 
 > **Note**: When `disableSkillShellExecution` is enabled (v2.1.91+), skills that rely on inline shell execution (e.g., `codex-exec`, `gemini-exec`, `rtk-exec`) will have their shell blocks disabled. This is a security hardening option.
-
-> **Note**: Optional frontmatter fields supported since CC v2.1.63+. Version-specific features listed in HTML comment below — access via Read tool.
+-->
 
 <!-- DETAIL: CC Version Compatibility History
 `isolation`, `background`, `maxTurns`, `maxTokens`, `mcpServers`, `hooks`, `permissionMode`, `disallowedTools`, `limitations` are supported in Claude Code v2.1.63+. Hook types `PostCompact`, `Elicitation`, `ElicitationResult` require v2.1.76+. `CwdChanged`, `FileChanged` hook events and `managed-settings.d/` drop-in directory require v2.1.83+. Conditional `if` field for hooks requires v2.1.85+. `PermissionDenied` hook event requires v2.1.88+. `refreshInterval` setting for status line auto-refresh interval added in v2.1.97+. Monitor tool and subprocess sandboxing (`CLAUDE_CODE_SUBPROCESS_ENV_SCRUB`, `CLAUDE_CODE_SCRIPT_CAPS`) added in v2.1.98+. Settings resilience (unrecognized hook event names no longer cause settings.json to be ignored) improved in v2.1.101+. PreCompact hook block support (exit 2 / `{"decision":"block"}`) added in v2.1.105+. Skill description listing cap raised from 250 to 1,536 characters in v2.1.105+. Plugin `monitors` manifest key for background monitors added in v2.1.105+. `ENABLE_PROMPT_CACHING_1H` and `FORCE_PROMPT_CACHING_5M` env vars for prompt cache TTL control added in v2.1.108+. Skill tool can now discover and invoke built-in slash commands (`/init`, `/review`, `/security-review`) in v2.1.108+. `/recap` session context feature and `/undo` alias for `/rewind` added in v2.1.108+. `/tui` command and `tui` setting for fullscreen rendering added in v2.1.110+. PushNotification tool for mobile push notifications (Remote Control + config required) added in v2.1.110+. `autoScrollEnabled` config for fullscreen mode added in v2.1.110+. SDK/headless `TRACEPARENT`/`TRACESTATE` distributed trace linking added in v2.1.110+. Bash tool maximum timeout enforcement added in v2.1.110+. Write tool IDE diff feedback (informs model when user edits proposed content) added in v2.1.110+. `--resume`/`--continue` now resurrects unexpired scheduled tasks in v2.1.110+. `/focus` command (separated from Ctrl+O) added in v2.1.110+. `xhigh` effort level for Opus 4.7 (between `high` and `max`; other models fall back to `high`) added in v2.1.111+. `/effort` interactive slider with arrow-key navigation (when called without arguments) added in v2.1.111+. Auto mode no longer requires `--enable-auto-mode` in v2.1.111+. PowerShell tool progressive rollout (`CLAUDE_CODE_USE_POWERSHELL_TOOL` env var) added in v2.1.111+. Read-only bash commands with glob patterns (`ls *.ts`) and `cd <project-dir> &&` prefix no longer trigger permission prompt in v2.1.111+. `/less-permission-prompts` built-in skill for permission allowlist scanning added in v2.1.111+. `/ultrareview` parallel multi-agent cloud code review added in v2.1.111+. `/skills` menu sorting by estimated token count (press `t`) added in v2.1.111+. `OTEL_LOG_RAW_API_BODIES` env var for full API request/response body logging added in v2.1.111+. Plan files named after prompt content (not random words) in v2.1.111+. Plugin error handling improvements (dependency conflict errors, stale version recovery, install recovery) in v2.1.111+.
@@ -155,11 +157,7 @@ hooks:
 
 ## Permission Mode Guidance
 
-When spawning agents via the Agent tool, CC applies a default `mode` of `acceptEdits` if not explicitly specified. To maintain consistent permission behavior:
-
-1. **Agent frontmatter `permissionMode`**: Declares the agent's intended permission level. CC respects this when the agent is spawned via Agent tool.
-2. **Agent tool `mode` parameter**: Overrides frontmatter at spawn time. Routing skills should pass this explicitly.
-3. **Recommendation**: For agents that modify files, set `permissionMode: bypassPermissions` in frontmatter if the project uses `bypassPermissions` mode.
+CC defaults `mode` to `acceptEdits` if not specified — always pass `mode: "bypassPermissions"` explicitly in Agent tool calls when the session uses bypass permissions. See guidance details via Read tool.
 
 | Mode | Behavior |
 |------|----------|
@@ -170,6 +168,14 @@ When spawning agents via the Agent tool, CC applies a default `mode` of `acceptE
 | `dontAsk` | Non-interactive, deny unapproved |
 | `auto` | AI decides safety |
 
+<!-- DETAIL: Permission Mode Guidance (reasoning)
+When spawning agents via the Agent tool, CC applies a default `mode` of `acceptEdits` if not explicitly specified. To maintain consistent permission behavior:
+
+1. **Agent frontmatter `permissionMode`**: Declares the agent's intended permission level. CC respects this when the agent is spawned via Agent tool.
+2. **Agent tool `mode` parameter**: Overrides frontmatter at spawn time. Routing skills should pass this explicitly.
+3. **Recommendation**: For agents that modify files, set `permissionMode: bypassPermissions` in frontmatter if the project uses `bypassPermissions` mode.
+-->
+
 <!-- DETAIL: Isolation/Token/Limitations/Escalation details
 ### Isolation Modes
 
@@ -241,6 +247,9 @@ Claude Code treats `.claude/` and `templates/.claude/` as sensitive directories
 
 This Codex port uses `.codex/` as the active runtime surface, but packaged compatibility templates still live under `templates/.claude/`. Any automation that writes those templates must account for Claude Code permission prompts.
 
+**Key rule**: `.claude/` and `templates/.claude/` Bash/Write/Edit targets can trigger sensitive-path prompts regardless of allow rules. In unattended flows, delegated agents must produce artifact bodies in `/tmp/{skill}-{timestamp}.md` first and avoid direct `.claude/**` tool targets.
+
+<!-- DETAIL: Sensitive Path Behavior table and Recommended practice
 | Path pattern | Sensitive in Claude Code? | Affected operations |
 |--------------|---------------------------|---------------------|
 | `.claude/**` | Yes | Bash writes, Write, Edit |
@@ -255,6 +264,7 @@ Recommended practice:
 3. Do not run unattended Claude Code release automation that writes `templates/.claude/**` unless the workflow can handle interactive approval.
 4. In this Codex port, update `.codex/...` source files and their `templates/.claude/...` mirrors deliberately instead of bulk-copying with shell commands.
 5. For unattended Claude compatibility-template writes, use a reviewed temporary script wrapper and verify the resulting diff; direct Bash/Write/Edit targets under `templates/.claude/**` can all trigger the sensitive-path guard.
+-->
 
 Delegation prompt requirement:
 
@@ -282,6 +292,9 @@ Fast Mode uses the same model with faster output. Activated via `/fast` toggle o
 | Output speed | Standard | ~2.5x faster |
 | Reasoning depth | Full | Reduced |
 
+See activation, effort interaction, and default effort change details via Read tool.
+
+<!-- DETAIL: Fast Mode Activation, Effort Interaction, Default Effort Change
 ### Activation
 
 - `/fast` — toggle in current session
@@ -297,6 +310,7 @@ When Fast Mode is active, it reduces effective reasoning depth but does NOT over
 Starting with Claude Code v2.1.94, the default effort level changed from `medium` to `high` for API-key, Bedrock/Vertex/Foundry, Team, and Enterprise users. Console (free-tier) users retain `medium` as the default.
 
 This means agents WITHOUT an explicit `effort` field now run at `high` effort by default on paid tiers. To maintain previous behavior, set `effort: medium` explicitly in agent frontmatter.
+-->
 
 ## Skill Frontmatter
 
@@ -311,6 +325,9 @@ description: Brief desc    # One-line summary
 
 ### Optional Fields
 
+Key optional fields: `scope`, `context`, `version`, `effort`, `model`, `agent`, `hooks`, `paths`, `shell`, `allowed-tools`, `keep-coding-instructions`. Skill `effort` takes precedence over agent `effort` when both specified. See full optional fields via Read tool.
+
+<!-- DETAIL: Skill Optional Fields (full yaml block)
 ```yaml
 scope: core                # core | harness | package (default: core)
 context: fork              # Forked context for isolated execution
@@ -332,6 +349,7 @@ keep-coding-instructions: true     # Preserve coding instructions in plugin outp
 ```
 
 When both an agent and its invoked skill specify `effort`, the skill's value takes precedence (more specific invocation-time setting).
+-->
 
 <!-- DETAIL: Skill Effectiveness Tracking
 Skills can optionally track effectiveness metrics via auto-populated fields:

package/templates/.claude/rules/MUST-agent-teams.md

@@ -271,10 +271,14 @@ When spawning agents that may be blocked:
 
 ## Lifecycle
 
+`TeamCreate → TaskCreate → Agent(spawn members) → SendMessage → TaskUpdate → ... → TeamDelete`. See full lifecycle via Read tool.
+
+<!-- DETAIL: Lifecycle diagram
 ```
 TeamCreate → TaskCreate → Agent(spawn members) → SendMessage(coordinate)
   → TaskUpdate(progress) → ... → shutdown members → TeamDelete
 ```
+-->
 
 ## Fallback
 

package/templates/.claude/rules/MUST-parallel-execution.md

@@ -96,6 +96,9 @@ In that shape, read/search lanes may fan out in parallel, while the push lane re
 
 Runtime detection and splitting of stalled parallel agents. Complements pre-execution parallelization.
 
+See detection signals, splitting rules, and example via Read tool.
+
+<!-- DETAIL: Adaptive Parallel Splitting — Detection, Splitting Rules, Example
 ### Detection
 
 | Signal | Threshold | Action |
@@ -124,9 +127,13 @@ After (adaptive split):
   P4 ████████████████████████████████  (spawned immediately)
   P5 ████████████████████████████████  (spawned immediately)
 ```
+-->
 
 ## Stability Testing Protocol
 
+Soft default: 4 concurrent agents; hard cap: 5. Reduce to 4 if latency >2x, failure rate >10%, or context errors. See full protocol via Read tool.
+
+<!-- DETAIL: Stability Testing Protocol
 When testing 5 concurrent agents (above the soft default of 4):
 
 | Observation | Threshold | Action |
@@ -136,6 +143,7 @@ When testing 5 concurrent agents (above the soft default of 4):
 | Context errors | Any | Reduce to 4 |
 
 5-agent concurrency is supported but should be monitored during initial adoption. Fall back to 4 if instability is observed.
+-->
 
 ## Agent Tool Requirements
 
@@ -157,6 +165,9 @@ Single agent spawns do NOT use the `[N]` prefix.
 
 ## Narrative Announcement Format (Before Spawn)
 
+Use markdown list format, not inline comma-separated text, for parallel dispatch announcements. See correct/incorrect examples via Read tool.
+
+<!-- DETAIL: Narrative Announcement Format (Before Spawn)
 When announcing a parallel dispatch in prose text (not the Agent tool call itself), use a markdown list rather than inline comma-separated description:
 
 ### Correct
@@ -174,6 +185,7 @@ When announcing a parallel dispatch in prose text (not the Agent tool call itsel
 ```
 
 The list form mirrors the tool-call `[N]` prefix pattern and scales better to 3+ concurrent agents.
+-->
 
 ## Result Aggregation
 

package/templates/.claude/rules/SHOULD-memory-integration.md

@@ -288,6 +288,9 @@ Save memory IMMEDIATELY upon surprising discovery — do not defer to session en
 | Subagent false-positive detected | Save `feedback_*.md` now | Prevent repeat in same session |
 | User correction / feedback | Save `feedback_*.md` now | Honor correction immediately |
 
+See rationale and cross-references via Read tool.
+
+<!-- DETAIL: Why Immediate? and Cross-reference
 ### Why Immediate?
 
 Session-end saves lose context: by the time the session ends, multiple discoveries have compounded and nuance is lost. Immediate saves preserve the exact trigger context that makes the memory actionable.
@@ -300,6 +303,7 @@ Related records from session v0.87.2~v0.88.0 (issue #869):
 - `feedback_subagent_pre_existing_claims.md`
 - `feedback_github_workflows_inventory.md`
 - `feedback_bun_mock_module.md`
+-->
 
 ## Session-End Auto-Save
 
@@ -307,6 +311,9 @@ Related records from session v0.87.2~v0.88.0 (issue #869):
 
 Session-end detected when user says: "끝", "종료", "마무리", "done", "wrap up", "end session", or explicitly requests session save.
 
+See flow diagram, responsibility split, and dual-system save table via Read tool.
+
+<!-- DETAIL: Session-End Flow, Responsibility Split, Dual-System Save
 ### Flow
 
 ```
@@ -340,9 +347,13 @@ MCP tools (claude-mem, episodic-memory) are **orchestrator-scoped** and not inhe
 | Native auto-memory | sys-memory-keeper | Write | Update MEMORY.md with session learnings | Yes |
 | claude-mem | Orchestrator | `mcp__plugin_claude-mem_mcp-search__save_memory` | Save session summary with project, tasks, decisions | No (best-effort) |
 | episodic-memory | Automatic | (auto-indexed) | No action needed — conversations are indexed automatically after session ends | N/A |
+-->
 
 ### Session-End Self-Check (MANDATORY)
 
+(1) sys-memory-keeper updated MEMORY.md? (2) claude-mem save attempted? Both are required before confirming session-end to the user. See full self-check via Read tool.
+
+<!-- DETAIL: Session-End Self-Check (MANDATORY)
 ```
 ╔══════════════════════════════════════════════════════════════════╗
 ║  BEFORE CONFIRMING SESSION-END TO USER:                          ║
@@ -363,6 +374,7 @@ MCP tools (claude-mem, episodic-memory) are **orchestrator-scoped** and not inhe
 ║  is NOT.                                                          ║
 ╚══════════════════════════════════════════════════════════════════╝
 ```
+-->
 
 ### Failure Policy
 

package/templates/manifest.json

@@ -1,6 +1,6 @@
 {
-  "version": "0.4.5",
-  "lastUpdated": "2026-04-27T02:00:00.000Z",
+  "version": "0.4.7",
+  "lastUpdated": "2026-04-27T04:55:00.000Z",
   "components": [
     {
       "name": "rules",