oh-my-openagent

v4.8.1 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

Published 1mo AI Coding Tools

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai ai-agents anthropic chatgpt claude claude-skills

+9 more

codex cursor gemini ide openai opencode orchestration tui typescript

Summary

AI summary

Updates cli-run, omo-codex, and codex-rules across a mixed release.

Changes in this release

Type	Severity	Summary	CVE
Bugfix
Bugfix	Medium	Codex no longer forces multi_agent_v2 enabled during install and migration. Codex no longer forces multi_agent_v2 enabled during install and migration. Source: llm_adapter@2026-06-09 Confidence: high	—
Bugfix	Medium	`omo run` respects configured agent display names before dispatching prompts. `omo run` respects configured agent display names before dispatching prompts. Source: llm_adapter@2026-06-09 Confidence: high	—
Bugfix	Medium	Hephaestus instructions are no longer truncated in Codex sessions. Hephaestus instructions are no longer truncated in Codex sessions. Source: llm_adapter@2026-06-09 Confidence: low	—
Bugfix	Low	Hephaestus instructions are preserved in Codex sessions without truncation. Hephaestus instructions are preserved in Codex sessions without truncation. Source: granite4.1:30b@2026-06-09-audit Confidence: low	—

Full changelog

Patch Release: Safer Codex Agents and Reliable CLI Runs

This patch makes agent routing safer across both editions.

Codex no longer forces multi-agent v2 on every model

LazyCodex now removes the installer-forced features.multi_agent_v2.enabled = true setting during install and migration. Codex can again choose the correct multi-agent mode from the model catalog, which avoids routing models into unsupported spawn_agent and encrypted-parameter behavior.

Full Hephaestus instructions are preserved in Codex sessions

hephaestus.md is now exempt from rule truncation, so the engineering agent receives the complete project instructions even when SessionStart rule budgets are tight.

`omo run` respects configured agent display names

The OpenCode CLI now resolves custom display names back to registered runnable agent names before sending the prompt. If your config renames an agent, omo run --agent ... now dispatches to the intended agent instead of passing a display-only name.

6ffd2e9cf fix(omo-codex): stop forcing multi_agent_v2 enabled in config
baa59caa6 fix(codex-rules): never truncate hephaestus.md in SessionStart injection
ba677fe8a Merge pull request #5069 from code-yeongyu/fix/4698-run-agent-display-name
ce908a235 fix(cli-run): honor configured agent names
2f8868bed fix(cli-run): dispatch registered agent names

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track oh-my-openagent

Get notified when new releases ship.

About oh-my-openagent

omo; the best agent harness - previously oh-my-opencode

All releases →

Related context

Related tools

Earlier breaking changes

v4.19.0 Removes legacy Ralph Loop wiring; introduces Goal feature with automatic config migration.
v4.6.0 Removed broken direct public binary entrypoints from platform launcher packages, keeping them internal.
v4.6.0 Removed legacy context-window monitor hook path from active hooks and config surfaces.
v4.4.0 Removes top‑level `lsp` config key; migration required to `.opencode/lsp.json`.