[KongchangAI]
Productoma

oh-my-agent

A toolchain for AI Agent orchestration that provides security scanning, state management, AgentMemory isolation and workflow extension capabilities, emphasizing auditable agent orchestration and independent verification mechanisms.

Timeline (last 90 days)

Oct 15

oh-my-agent went from 15.10.0 to 20.0.0 in seven days with five consecutive major releases, providing no compatibility layer and directly removing old paths

Unverified50%
Oct 15

This wave of oh-my-agent updates includes 81 commits and 840 file changes, +70,280 lines / -32,120 lines, and the AgentMemory rework ran 1,095 tests

Unverified50%
Oct 15

The security module oma-deepsec was renamed to oma-security, the slash command /deepsec was changed to /security, and no compatibility alias is provided, so the old form stops working immediately

Unverified50%
Oct 15

OMA_HOME now uniformly points to the global data home directory, with a default path of ~/.oma, and definitions, state, scheduling, and backups are all consolidated into this directory

Unverified50%
Oct 15

The state migration strategy is copy-first with conflict checks and running-state checks, old paths are no longer read as a runtime fallback, and project-local state can only be migrated by explicitly running oma state migrate --runtime

Unverified50%
Oct 15

AgentMemory's writes, recalls, retries, and imports are scoped and isolated by the original project and profile, and shared server responses are filtered by ownership; installation and updates automatically prepare the default AgentMemory provider, unless the project explicitly opts out or switches to another provider

Unverified50%
Oct 15

The agent's decisions are recorded as state events (tagged b4d76a71), so choices made during a run can be reviewed after the fact

Unverified50%
Oct 15

The managed commit-msg hook executes each executable file under .githooks/commit-msg.d/ in filename order, and any non-zero exit rejects the commit, and oma never writes to that directory

Unverified50%
Oct 15

This update fixes the issue where oma retro --json printed a banner and spinner before the JSON, and it now outputs a single valid JSON document, which also applies to empty windows

Unverified50%
Oct 15

schedule sync would crash when a manifest line was missing required fields and cause all healthy tasks to go stale, and it has now been changed to discard malformed lines and report them, with schedule list naming these lines

Unverified50%

3 more timeline events

All Facts (13)

Unverified

ralph judge is now described as prompted rather than independent, because nothing is checking the spawn.

50%
Unverified

This wave of oh-my-agent updates includes 81 commits and 840 file changes, +70,280 lines / -32,120 lines, and the AgentMemory rework ran 1,095 tests

50%
Unverified

The security module oma-deepsec was renamed to oma-security, the slash command /deepsec was changed to /security, and no compatibility alias is provided, so the old form stops working immediately

50%
Unverified

OMA_HOME now uniformly points to the global data home directory, with a default path of ~/.oma, and definitions, state, scheduling, and backups are all consolidated into this directory

50%
Unverified

The state migration strategy is copy-first with conflict checks and running-state checks, old paths are no longer read as a runtime fallback, and project-local state can only be migrated by explicitly running oma state migrate --runtime

50%
Unverified

AgentMemory's writes, recalls, retries, and imports are scoped and isolated by the original project and profile, and shared server responses are filtered by ownership; installation and updates automatically prepare the default AgentMemory provider, unless the project explicitly opts out or switches to another provider

50%
Unverified

The agent's decisions are recorded as state events (tagged b4d76a71), so choices made during a run can be reviewed after the fact

50%
Unverified

The managed commit-msg hook executes each executable file under .githooks/commit-msg.d/ in filename order, and any non-zero exit rejects the commit, and oma never writes to that directory

50%
Unverified

The full plugin package now shares a single package-level resource tree, cutting 471 duplicate files, at the cost that root plugin skills depend on this shared tree, so installing via OMA preset is recommended rather than npx skills or APM

50%
Unverified

The documentation is now generated from source: the CLI registry is rendered by oma describe, and the skill catalog is rendered from SKILL.md frontmatter, both with a --check mode that reports outdated blocks; the documentation site includes 11 language versions and 12 README translations

50%
Unverified

oh-my-agent went from 15.10.0 to 20.0.0 in seven days with five consecutive major releases, providing no compatibility layer and directly removing old paths

50%
Unverified

This update fixes the issue where oma retro --json printed a banner and spinner before the JSON, and it now outputs a single valid JSON document, which also applies to empty windows

50%
Unverified

schedule sync would crash when a manifest line was missing required fields and cause all healthy tasks to go stale, and it has now been changed to discard malformed lines and report them, with schedule list naming these lines

50%

Source Articles