Ecosystem Update — 2026-05-13
Highlights
- No safe harness Quick Win cleared the automatic-edit bar today; the useful signals all require a new script, a new hook surface, a skill audit, or an explicit memory-policy decision
- The strongest near-term queue item is a hook health smoke check: GitHub issue #21639 reports Codex Desktop hook regressions, and this setup depends on
PreToolUse,PostToolUse,SessionStart,Stop, andPreCompact
Quick Wins (implemented today)
-
None safe today hook / skill / memoryNo automatic harness edit: every candidate needed new scripts, new hooks, external skill trust, policy changes, or upstream support
New Tools, Skills & Patterns
-
Codex Desktop hook regression smoke check hookAdd a small local diagnostic that verifies expected hook execution after Codex Desktop or CLI updates
-
Hook parity gap tracker hookTrack upstream hook parity against the local
hooks.jsoncontract, especiallyPostToolUseFailure, subagent lifecycle, config drift, worktree, and post-compaction events. Not a Quick Win because Codex does not expose these hook events locally yet -
Repo-scoped experience compiler intake memory
-
Community Codex skill catalog audit skillAudit individual skills such as
gh-fix-ci,pr-review-ci-fix,sentry-triage,datadog-logs, andwebapp-testingwithcodex-skill-audit --strictbefore considering local installation. Do not wholesale import -
Codex release and changelog watcher Codex-mdCurrent local CLI is
codex-cli 0.130.0; keep the release watcher in the queue rather than auto-upgrading because version changes affect hooks, plugins, app-server behavior, and Desktop compatibility -
Native Codex memories pilot plan mcp
Research Worth Reading
-
Autonomous LLM Agent Worms: Cross-Platform Propagation, Automated Discovery and Temporal Re-Entry DefenseDirectly relevant to this runtime's persistent memory, scheduled state, and off-machine connectors; prioritize typed memory promotion, sealed config, and capability attenuation patterns
-
ASIA: an Autonomous System Identification AgentUseful as a cautionary reference for autonomous experimentation loops: it highlights closed-loop hypothesis/implementation/evaluation, plus risks around test leakage and reproducibility
-
To What Extent Does Agent-generated Code Require Maintenance? An Empirical StudyReinforces the existing maintenance-score queue item: agent-authored files need explicit later review, not only initial green tests
-
Can Coding Agents Reproduce Findings in Computational Materials Science?Supports stronger environment reconstruction and evidence capture before claiming task completion, especially for underspecified workflows
Considered, Not Adopting
Items reviewed and explicitly declined this cycle, with the reason. Curation discipline matters more than coverage.
- Enable native Codex memories immediately
-
Wholesale import from Composio or other community skill catalogs — violates the local outside-skill trust rule; individual skills need
codex-skill-audit --strictand a concrete recurring use case - Adopt full Claude Code hook parity locally — overfits to unimplemented upstream events; keep as a watcher until Codex exposes stable event and payload contracts
- Auto-format hook wiring — requires repo-specific formatters or a new global script, which the ecosystem-update hard limits forbid as an automatic Quick Win
-
Default to
xhighreasoning or Fast Mode globally — changes cost/latency posture and contradicts the current power-user baseline unless requested for a specific route/profile -
Switch to conservative
on-requestapprovals — conflicts with the explicit local runtime posture:approval_policy = "never"andsandbox_mode = "danger-full-access" - Install Deep Agents / LangGraph helper skills — useful only for that external stack; not aligned with the current Codex-owned harness without a concrete project need