DEV Community: gracefullight

oh-my-agent: session trajectories and skill compatibility checks

gracefullight — Mon, 12 Oct 2026 15:54:38 +0000

Agent runs can span several CLIs, tool calls, and completion checks. Following that sequence means opening more than one log. This week's oh-my-agent changes add a session trajectory viewer, an HTML explanation renderer, and checks for how skills are read by different runtimes.

This is the delayed update for October 8, 2026. It covers changes available by 12:00 Australia/Sydney that day, through CLI 15.9.0. Later changes are outside this report.

What's new

Session trajectories. The viewer joins OMA lifecycle events with vendor transcripts. Terminal and dashboard views help you follow a session's sequence of messages, tool calls, and checks. The implementation was extended to eleven runtimes during the week. Implementation.
Markdown explanations. oma explain render turns a structured Markdown draft into a self-contained HTML page. Choose a panel grid or a document layout, then use oma explain lint to check the prose. This gives reviewers a file they can open without running the project. Implementation.
Skill compatibility checks. oma skills matrix plans checks for skill discovery, relative references, and final JSON output through native Claude and Codex CLIs. Installed-skill audits also support the body injection format used by agent-valley. These audits measure file access, not whether a skill can complete every task. Scope and commands.

The matrix defaults to planning. The following command prints a plan without starting vendor processes:

oma skills matrix --vendors codex --cases discovery,reference

A live run requires --live and authenticated CLIs.

What's fixed

Schedule manifest updates are serialized to prevent concurrent writers from losing changes. Scheduled dispatch also resolves the CLI runtime.
Verification evidence is bound to the exact task and run receipts, so evidence from another run cannot stand in for the selected work.
Managed hook upgrades preserve user scripts, and uninstall preserves skills that lack OMA-managed ownership.

What's better

oma bridge loads only the bridge command instead of the full CLI command tree. Shared Serena daemon logs are bounded, and oma doctor warns when PATH contains different OMA versions. These changes address startup work, log growth, and version confusion.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

If you use OMA across runtimes, start with a session trajectory to inspect what ran, then use the matrix to check how a selected runtime reads skill files.

https://github.com/first-fluke/oh-my-agent

What OMA returns when its test gate fails

gracefullight — Sat, 03 Oct 2026 02:41:47 +0000

oh-my-agent (OMA) can rerun a configured test script when an active workflow
tries to stop. This example exercises that behavior with manual hook calls and
a deliberately broken expiry check. It uses the OMA 15.0.13 source CLI.

The fixture defines an item as expired at now === expiresAt. Its implementation
used >, so the boundary test failed. The test process exited with code 1.
This excerpt comes from the actual output:

not ok 2 - at expiry: expired
# pass 2
# fail 1

The fixture's active Ralph workflow had a test completion gate. A manual
call to OMA's Stop hook reran the package's test script. The response contained
"decision":"block" and this reason:

Stop gate 'test' FAILED (reinforcement 1/5).

The oma hook run process itself exited with code 0. Its JSON decision carries
the block; treating that exit code as a successful test would be incorrect.

The fix changed one comparison:

-  return now > expiresAt;
+  return now >= expiresAt;

Rerunning the tests produced:

# pass 3
# fail 0

The next Stop call ran the same gate and returned empty stdout. OMA removed the
fixture's workflow state and recorded gate.passed, followed by session.ended
with reason completion_gate_passed.

The demo, receipts, and reproduction script contain the full
commands, timestamps, and output. Download reproduce.py and run it against an
OMA source checkout with its CLI dependencies already available:

python3 reproduce.py --oma-source /path/to/oh-my-agent --output /path/to/new-demo-run

Download demo.html from the Gist to watch the 45-second explanation locally. GitHub displays its source rather than playing it on the page.

The script requires Python 3, Git, Node, and Bun. It creates an isolated fixture
and session store; it does not change your project's workflow state.

This is a local fixture with manually invoked hooks, not a recorded autonomous
agent session or a production incident. It demonstrates this configured gate
on these tests. It does not establish general correctness or a comparison with
another tool.

The full harness supplies the CLI and hooks used here. A skills-only install
does not. Start with one scoped task in the
Quick Start,
then inspect its diff and checks. The source is on
GitHub.

oh-my-agent: shared Serena daemons, bounded retry loops

gracefullight — Thu, 01 Oct 2026 02:00:47 +0000

Five CLI releases, 15.0.2 through 15.0.6, shipped this week. The theme is long-running agents that stay well-behaved: fewer stray processes, bounded memory, and retry loops that know when to stop.

20 commits, 69 files, roughly 3,700 lines added. Most of it went into how oh-my-agent manages Serena, the code-search backend that every agent leans on.

What's new

Managed Serena runtime: version-gated Serena adapters are installed with a per-file SQLite symbol cache. Python no longer holds full workspace symbol trees in memory.
oma serena check: a new command that validates the Serena config and runs Dart checks against the shared daemon, with exit codes you can script against.
Scheduled daemon cleanup: a separate periodic task reaps idle shared Serena daemons. It verifies process identity before signaling a registered PID, so a recycled PID never gets killed by mistake.
Managed Dart diagnostics: package diagnostics reuse the managed Dart language server. Adapter revisions are tracked whenever a shared daemon starts or is replaced.
Doctor reporting: oma doctor now reports the Serena adapter state, in both the terminal footer and the JSON report.

What's fixed

Duplicate Serena stacks: when the shared server is unreachable, oma now reports the connection failure instead of spawning a private Serena stack. Managed contexts are normalized before registry lookup.
Daemon replacement under load: if the runtime revision changes while clients are attached, the loaded daemon is reused and the replacement waits until every client detaches. Active, busy, and legacy-revision cases are covered by tests.
Eager Dart analysis: Dart now defaults to analysis on file open, and uses the local stable SDK version when none is configured.
Unbounded orchestration retries: plans are pinned when dispatched, and retries are counted by workflow lineage and logical goal. Evidence failures are now separate from product failures, and a missing-metadata problem gets one bounded repair without restarting product planning.
Flaky checks: the bridge timeout test asserts the protected bridge's response instead of wall time. Boundary scanning retries transient TypeScript worker exits.

What's better

Quieter updates: oma update shows the changed Hyperframes components, deduplicates repaired links, and ends with one version summary. The inaccurate file totals and routine notices are gone.
Cleaner module boundaries: Serena config validation moved into the shared I/O layer, so serena check and setup no longer import the bridge command slice. Behavior is unchanged.
Verification: the duplicate-server fix was checked with 211 affected tests, type checking, lint, boundary checks, and a smoke test of symbol and definition lookup on Serena 1.7.0 with Dart 3.13.4.
Docs and tests: integrations/serena/README.md is expanded, with new Python tests for the Dart adapter, installer, and symbol cache.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

Links

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: tighter guardrails around long-running orchestration runs, so a stuck goal fails fast instead of looping.

https://github.com/first-fluke/oh-my-agent

oh-my-agent 15: HyperFrames replaces Remotion, Serena guard ships

gracefullight — Thu, 24 Sep 2026 02:01:01 +0000

oh-my-agent CLI 15.0.0 just shipped, and oma-video now renders with HyperFrames instead of Remotion. It is a breaking change, so it took a major version. The week also brought a hook that stops agents from bypassing your code-intelligence provider, and a batch of fixes for Serena daemons and schedules.

The numbers: 67 commits, 230 files touched, CLI 15.0.1 and web 7.0.0.

What's new

HyperFrames compositor: the managed video toolchain moves from Remotion to HyperFrames (heygen-com/hyperframes) across the video CLI, the oma-video skill resources, oma update refresh, and docs. Migration is two renames: the video.remotion config key is now video.hyperframes, and --compositor remotion becomes --compositor hyperframes.
Code-intelligence guard: a new PreToolUse handler denies native Grep/Glob and recursive shell search (rg, ag, fd, grep -r, find -name, git grep) while providers.code_intelligence is configured. The deny reason names the Serena or Gortex tool to use instead. Set providers.code_intelligence_guard to off in a local overlay to disable it, or prefix a command with OMA_CI_ALLOW_NATIVE=1 when the provider is down. It is registered in all seven hook variants (claude, codex, cursor, grok, kimi, kiro, qwen).
AGENTS.md only: Claude Code 2.1.277 and later reads AGENTS.md natively, so oma now writes its block there and never into CLAUDE.md. Migration 031 strips the legacy block, deletes the file only if the block was its sole content, and leaves an @AGENTS.md import line for user-owned files. oma doctor warns when a CLAUDE.md without the import would shadow AGENTS.md.
Legacy Gemini MCP cleanup: migration 030 removes matching OMA default Serena and browser entries from old project Gemini settings once Antigravity is selected. Custom settings and symlinks are preserved.

What's fixed

Serena daemon sprawl: a bridge that could not probe a busy daemon within 2 seconds used to start a rival on the same port. The rival died on bind and pruned the live daemon's registry record, leaving three daemons per project on one machine. Bridges now wait on a registered daemon whose pid is alive, and registry operations run under the file lock.
Stranded schedules: registrations written before the command rename still invoked oma schedule:run, failed on every fire, and still showed as synced. Drift detection now reads the registered command from launchd, crontab and systemd, reports a stale state, and oma schedule sync and oma update rewrite those jobs.
Global settings clobbered: cd $HOME && oma link claude treated HOME as a project root and rewrote the user's global hook commands. link and update now refuse project mode from HOME and point at oma link --global (closes #788).
Secrets check: oma verify detects hardcoded secrets more reliably.
Native search false positives: the guard now allows scoped searches inside provider-excluded and external paths, with Windows path normalization.
Repeated Serena migration: migration 007 no longer re-triggers a same-version download after browser MCP selection.

What's better

Import boundaries: check-boundaries now enforces every literal import. Schedule adapters and video internals moved into cli/io/schedule and cli/io/video, and agent dispatch preparation is shared between spawn and parallel.
Tests: the scripts/ suite (41 tests) now runs under vitest, so bun run test covers it. It previously used the bun runner, which no npm script executed.
Cross-post pipeline: the vendor JSON envelope is unwrapped before parsing, which fixes the weekly job failing on every run, and translated titles must now carry the same claim as the English source.
Docs: Korean, Japanese and Chinese harness-evolution guides landed, which unblocked the locale docs builds. Spawn docs now say --vendor instead of the removed -m/--model flag.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

Links

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: more hooks that enforce what the session primer only advises.

https://github.com/first-fluke/oh-my-agent

oh-my-agent: failed runs now turn into skill regression tests

gracefullight — Sat, 19 Sep 2026 00:53:24 +0000

A failed agent run used to end with a log and a shrug. This week oh-my-agent closed that loop: a failure can be captured as an incident, promoted to a skill fixture, and fed to an optimizer that edits the skill under a dispatch budget. It took 131 commits and moved the CLI from 14.7.11 to 14.13.1.

What's new

Incident capture and promotion: oma harness incident scan lists failed, blocked, and partial runs that no incident references. oma harness incident promote derives a regression fixture for the skill the agent used, and admits it only when the recorded failing output fails it. oma harness feedback --scan-runs chains capture, promote, and optimize. Finished runs now keep the last 64 KiB of runner log so the fixture can be validated against what the agent actually said.
Budgeted skill evolution: oma skill optimize accepts an edit only when neither the validation nor the training split regresses and at least one improves. constitution.budget.max_dispatches_per_run is now enforced: the call that would exceed it is refused and promotion is blocked. Every applied edit records lineage, and oma skill promotions and oma skill rollback read it back.
Meta-optimization: oma skill meta-optimize treats the optimizer prompt itself as the candidate. Promotion needs a seeded paired bootstrap 95% interval above zero and at least three pairs. The first adopted procedure beat the current one by 0.27 on average, interval [0.04, 0.54], and added three grounding rules for proposed skill edits.
Routing eval: oma skill eval --routing shows the model every installed skill description and records whether it picks the target, a neighbor, or nothing. It separates "the body helps" from "the skill gets selected".
Code-intelligence guard: a PreToolUse hook denies native Grep, Glob, and recursive shell search (rg, grep -r, find -name, git grep) while a provider is configured. The deny message names the Serena tool to use. OMA_CI_ALLOW_NATIVE=1 is the escape hatch, and providers.code_intelligence_guard: off disables it.
Session-start notices: the state snapshot now announces skill and procedure promotions once, one line each with the edit and the lifts. oma doctor gained an Evolution note.
Orca reporting: spawned child agents report their lifecycle to Orca. Qwen gained native agent definitions.

What's fixed

The weekly cross-post job failed on every run after model_preset moved to auto. claude --output-format json wraps the answer in an envelope, and runAgent returned it raw. It now unwraps the configured response_jq path and falls through to raw stdout for vendors without one.
OS jobs registered before the command rename kept calling oma schedule:run <id> and failed on every fire, while schedule list reported them as synced. The legacy spelling is accepted when the OS invokes it, drift detection has a new stale state, and oma schedule sync and oma update rewrite stale registrations.
cd $HOME && oma link claude treated HOME as a project and rewrote the global Claude hook commands. link and update now refuse project mode from HOME (#788).
The skill judge parsed PASS/FAIL from the raw Claude envelope, where "failed":0 came before the verdict, so every judge verdict read FAIL. Outputs are unwrapped before scoring, and stale recordings are discarded.
--repeats 3 parsed to NaN because bare parseInt received the previous value as its radix. Variadic option values (--skill a b) no longer trip the stray-positional guard.
Projects synced before v11 still ran their own Serena per session. Migration 029 rewrites those launchers to the shared oma bridge entry in each vendor's native form.
oma update respects an explicit vendor list instead of detecting from project directories.

What's better

One optimization epoch with four candidates took forty minutes because every arm and judge ran serially. Live dispatches now run through a bounded pool (OMA_SKILL_EVAL_CONCURRENCY, default 4), and meta-optimization overlaps inner runs across skills (OMA_META_CONCURRENCY, up to 4). The per-dispatch timeout is 180s, with one retry on timeout.
Fixtures test what the body states. The oma-debug set was rewritten after the first version scored 89% without the skill. The new twelve score 25% baseline and 100% with the skill. oma-refactor went from 16.7% to 100% the same way. oma-docs, oma-scm, and oma-qa also have twelve body-aligned fixtures each.
The first loop-verified edit landed in oma-docs: held-in 55.6% to 77.8%, held-out validation unchanged at 100%.
Cost is visible. Runs report model calls per verified improvement, so a procedure that wins on gain by spending more shows up as such.
Gortex is out and code intelligence is back on the Serena bridge. It pinned the CPU re-patching a 4 GB index and exposed no cap.
Skill and shared prompt files were trimmed to cut unconditional preflight, scoring, and approval rules. Incident guides shipped in all 11 doc locales.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

Links

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: running the feedback loop on a schedule against real project runs, so skill edits arrive with their evidence attached.

https://github.com/first-fluke/oh-my-agent

oh-my-agent: managed skill caches and WikiSkill evolution

gracefullight — Thu, 03 Sep 2026 02:06:18 +0000

The market, diagram, and video pipelines just moved to always-latest managed skill caches. When you orchestrate external tools, you want them at HEAD without dragging down your repository.

This week introduces a shared caching layer for third-party skills, meaning your agents always resolve the latest logic for generating architecture diagrams, market research, or video compositions.

What's new

Managed skill layer: Introduced a shared caching system for external skills. Diagram, market, and video tools now resolve and update from GitHub Releases or upstream engines directly into local cache.
Diagram engine: Added oma diagram subcommands powered by the external archify skill for generating architecture diagrams.
Upstream market engine: Replaced the in-house market pipeline with the upstream last30days engine. The oma market run command now passes arguments straight to the source.
Dynamic video authoring: Stopped shipping vendored Remotion code. The new oma video compose command scaffolds compositions dynamically against the latest Remotion toolchain.
WikiSkill evolution: Added persistent rollout knowledge across optimization runs, complete with sandboxed live evaluations and validation gating.

Pushing skill resolution to runtime keeps the core CLI lean while giving agents the best available tools.

What's fixed

Enforced literal UTF-8 output for Claude tool-call parameters to prevent unicode escape display corruption in interactive terminal prompts.
Disabled memory tools at the Serena MCP boundary to strictly enforce state safety during managed launches.

What's better

State decoupling: Decoupled coordination state from Serena by routing session summaries through a neutral exporter.
Unified intelligence: Routed all managed clients through a single fixed Serena capability surface for context gathering.
Documentation structure: Moved the Quick Start section above the control boundary explanations in all README files to reduce time-to-action.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: exposing the managed skill layer to custom user workflows.

https://github.com/first-fluke/oh-my-agent

oh-my-agent: strict commit attribution and capability routing

gracefullight — Thu, 27 Aug 2026 02:05:51 +0000

When you tell an agent to write code, getting it to commit with the right attribution is surprisingly brittle. A typo in a co-author address survives a history rewrite and ruins contributor graphs forever. This week, we fixed that and tightened up how capabilities are routed across the system.

What's new

Added a native commit-msg hook to enforce exact Co-authored-by addresses, guaranteeing correct GitHub attribution for agent commits.
Granted oma and ls blanket permissions for Claude and Qwen, cutting down on repetitive confirmation prompts during long runs.
Updated Ralph to lock criteria autonomously without stopping for user confirmation in persistent mode.

The git hook checks against your allowed addresses before the commit writes to disk. If you already use husky or lefthook, it politely provides the one line you need to add instead of taking over your configuration.

What's fixed

Pointed the default serena configuration at the shared bridge daemon, saving memory by preventing duplicate server processes per session.
Included pi and opencode extension vendors in the default linking path so they generate and document correctly out of the box.
Replaced bare trigger words with multi-word phrases for French and Portuguese queries to eliminate false-positive workflow activations.

What's better

Renamed 5 actor-style skill identifiers to capability nouns for clearer routing. Migration 023 handles the transition automatically.
Upgraded the keyword detector to safely ignore multiline bug and error inquiries, keeping memory coordination focused on actual state changes.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: expanding capability discovery across distributed teams.

https://github.com/first-fluke/oh-my-agent

oh-my-agent: cross-vendor refactor guards and isolated eval

gracefullight — Thu, 20 Aug 2026 02:01:06 +0000

oh-my-agent 12.4.0 just shipped with a cross-vendor refactor guard and isolated harness evaluation. When an agent edits too many lines in a single file without refactoring, the runtime now blocks the stop event and dispatches a dedicated refactor engineer to clean up the mess before returning control.

What's new

Cross-vendor refactor guard: A new refactor_guard hook tracks line budgets across edit tools. If an agent exceeds 500 lines in a single file, the hook blocks termination and dispatches refactor-engineer. This works across all 9 supported vendors.
Isolated harness evaluation: The oma harness command now compares scoped .agents overlays in paired temporary workspaces, using deterministic artifact checks and hash-bound record and replay.
Agent Plugins support: A standard git clone of the repository now acts as an installable Agent Plugins 1.0.0 package, exposing plugin.json, mcp.json, and the skills tree directly at the repository root.
Translation profiles: oma-translator now uses per-language profiles (en, ko, ja, zh) to isolate register systems and typography rules from the shared pattern taxonomy.

Controlling an agent's context requires precision. The new refactor guard ensures that large changes are forced into a refactoring phase before the session ends, keeping files maintainable.

What's fixed

SCM decisions like commit splits and merges are no longer recorded as durable facts in the agent memory store. They are already in git history, and skipping them prevents repository metadata from crowding out real cross-session decisions.
oma link now renders the union of vendor hooks and subagents for shared files like AGENTS.md, preventing the file from flip-flopping when different vendors trigger the merge.
User-added MCP servers in .cursor/mcp.json are preserved during updates. The CLI now merges its managed servers rather than overwriting the entire file.
OpenCode authentication checks now correctly derive the provider from the row's model specification, resolving false offline reports when users authenticated with alternative providers.

What's better

Replaced unreachable context budget claims in the documentation with measured, reproducible token costs. The two-layer skill design avoids roughly 75 percent of skill-loading overhead on complex tasks.
Scoped Single Source of Truth (SSOT) protection strictly to definition files. Agents are now explicitly instructed that run outputs in .agents/results/ are expected, preventing them from deleting session handoff state to restore protection.
Korean translations across all 22 pages are synced to parity with the English source, normalizing instruction registers and fixing legacy structural drift.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: multi-turn rollback primitives for stalled reasoning loops.

https://github.com/first-fluke/oh-my-agent

oh-my-agent: mechanical stop gates and unified configuration

gracefullight — Thu, 13 Aug 2026 02:01:03 +0000

When you leave an autonomous agent running overnight, you need to know it will actually stop when the work is done. It should not stop because it hit an arbitrary loop limit. This week brings mechanical stop gates to persistent workflows, unifies configuration into a single file, and ships portable agent plugin exports.

What's new

Mechanical stop gates: oma goal:set establishes a completion contract for persistent mode. Map keywords like typecheck or lint to local scripts. A pass allows the workflow to stop. A failure blocks the stop and counts toward the MAX_REINFORCEMENTS threshold.
Unified skill configuration: We dropped the scattered legacy config files. .agents/skills/*/config/*.yaml and models.yaml are gone. oma-config.yaml is now the single source of truth. Run oma update and migration 022 will carry over any user-diverged keys automatically.
Agent Plugins 1.0.0: Run oma emit --target agent-plugin to export a self-contained archive. This outputs a closed-schema plugin.json conformant with the agent-plugins.org specification.
TDD evidence checks: oma verify now supports an opt-in per-task test approach. Tasks marked tdd require a TDD_EVIDENCE block in the result file showing a focused test command, a red failure, and a green pass.
Harness refine signals: oma retro now analyzes the event trail. Repeated gate failures or raised blockers are aggregated into a new section with one-line edit proposals for your harness.
Dry-run linking: oma link --dry-run previews every target before mutating your workspace. It shares the exact same vendor conditionals as a real pass.

This release also shifts our documentation structure. Artifact verification now leads the pitch over portability.

What's fixed

External vendor CLIs exiting 0 without writing a workspace artifact now fail loud with an exit code of 3. You will no longer mistake a silent misdirected write for success.
The HUD statusline no longer hangs indefinitely when stdin is kept open. It now falls back to an 800ms asynchronous read timeout.
Generated file writes are now fully atomic. A crash mid-write will no longer leave corrupted partial files in vendor directories.
Uninstalling no longer inadvertently deletes home-consent symlinks belonging to other installations.

What's better

Skill evaluation is now grounded in real data. We seeded offline --mock replay coverage for oma-scm, oma-market, and oma-docs using recorded live rollouts.
The unit coverage floor stays hard. Omitting a test approach value in the PM plan will never waive the >= 80% coverage gate.
Trigger keywords are no longer strictly gated by the configured language. A Korean prompt in an English project will correctly fire its workflow.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: automated rollback triggers for failed verification gates.

https://github.com/first-fluke/oh-my-agent

oh-my-agent: inline plan creation and Node 26

gracefullight — Thu, 06 Aug 2026 02:01:10 +0000

When you tell an agent to build a complex feature, it usually needs a plan. When you do not provide one, the orchestrator should not just hand the request back to you.

Until this week, oma orchestrate required an existing plan file to proceed. Now, it generates one on the fly.

What's new

oma orchestrate creates a plan inline when no usable plan exists, using the same session ID so artifacts do not diverge.
Node 26 is now the required runtime for all workspaces and local shells.
The OMA block enforces an absolute top-priority directive: execute imperative prompts verbatim and never build until explicitly asked.
Qwen Code generation requests now run with a 5-minute timeout ceiling to prevent long agent turns from aborting mid-stream.

Global installations need to know where they live, not just where you are currently standing in the terminal.

What's fixed

oma doctor --global and oma link --global now correctly resolve the global install root instead of process.cwd(), fixing silent failures during global operations.
Serena search hits no longer truncate due to low character limits on initial installs.
Removed short Korean keywords that falsely activated persistent modes and blocked session termination.

We also tweaked how the frontend skill handles default Next.js behaviors to protect your container CPU.

What's better

The oma-frontend skill defaults next/link prefetch to false, cutting down on RSC payload requests for nav-heavy pages.
Over 40 vendor writers now use safeGetInstallRoot(), making the CLI more resilient when .agents directories are missing.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: refined memory controls for long-running sessions.

https://github.com/first-fluke/oh-my-agent

oh-my-agent: shared MCP daemons and offline BGM rendering

gracefullight — Thu, 30 Jul 2026 02:01:19 +0000

We just merged a complete overhaul of how oh-my-agent manages MCP processes. Previously, every agent session spawned its own copy of every stdio MCP server. We measured 65 processes and 800MB of RAM across six sessions. Now, serena daemons are shared per-project by default.

What's new

BGM rendering: The video agent now supports --music <preset> to render background music beds offline.
Strudel integration: Music is generated via Strudel in a headless Chrome instance without adding npm dependencies to the CLI.
Unified config: Source control management configurations are now consolidated into a single .agents/oma-config.yaml file.

The music presets are arranged rather than looped, using scale degrees and per-bar gain ramps to build a proper bed over the specified duration.

What's fixed

Global install scope: Fixed a bug where oma install --global registered the home directory as a project, preventing the language detection scanner from walking up to 20,000 irrelevant files.
Hook paths: The oma-hook.sh wrapper no longer bakes in the absolute path of the installer, keeping version-controlled hooks clean across teams.
Model probing: Fixed the model:probe command to correctly resolve custom registered slugs instead of always falling back to the owner prefix.
MCP bridge paths: Stopped the bridge from writing machine-specific absolute paths into the committed .mcp.json file.

These fixes prevent local installation environments from leaking into version control and breaking workflows when shared across different machines.

What's better

Daemon lifecycle: The new bridge mode starts a single serena HTTP daemon per project and shares it across sessions. The daemon shuts down automatically after a 10-minute idle grace period.
Artifact footprint: Removed 298 files and 4.8MB of duplicated skill artifacts from the repository by dropping the generated/ tracking directory.
Prompt engineering: Dropped explicit self-verification instructions and output-shape examples from core skills to align with Anthropic's new context guidance.
Skill length linting: Added a warning when a skill body exceeds the 500-line limit recommended by prompt engineering guides.

The prompt reductions were validated across 20 agent runs, proving that removing explicit examples actually improved the agent's ability to fix mutable sort keys without introducing false positives.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: expanding the video compositor with custom branded layers.

https://github.com/first-fluke/oh-my-agent

oh-my-agent: cross-context reviews and trigger accuracy testing

gracefullight — Thu, 16 Jul 2026 02:01:44 +0000

When you ask a model to review its own design, it usually gives itself an A. We merged a fix for authorship bias this week.

What's new

Trigger accuracy harness: oma verify triggers now measures keyword false-fire and missed-fire rates against a 167-entry labeled corpus with zero LLM calls.
Standards emission: oma emit generates conformant Agent Skills spec folders, a .claude-plugin marketplace manifest, and an AGENTS.md index directly from the .agents single source of truth.
Skills linting: oma skills lint enforces deterministic authoring-smell checks based on Anatomy-to-Smells research.
Bundle sprawl warnings: oma skills audit now flags skills that exceed 20 reference files or 25,000 characters.

We also wired up SessionStart hooks for Claude Code to reload skills dynamically and handle session compaction without dropping context.

What's fixed

Keyword matching now ranks by specificity. Longest keyword wins, then multi-word, then declaration order. This resolves self-suppression collisions.
Relayed inter-agent messages no longer trigger false workflow keyword detections.
Windows atomicWriteJson failures (EPERM) are resolved by opening the temp file with read-write permissions.
The opencode bridge is completely rewritten to honor the new plugin API mutation contract, restoring true persistent mode.

What's better

Cross-context reviews: All 11 ultrawork review steps now dispatch to fresh reviewer subagents that receive only durable artifacts and the review guide. Same-session self-review is removed because isolated reviews catch more defects.
High-stakes blind review: Brainstorm workflows now escalate to independent subagents for design artifact critique, completely removing authorship bias.
Marketplace consolidation: The repository root .claude-plugin directory is now the single source of truth for the Claude plugin marketplace.

Installation

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash

# Windows (PowerShell)
irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex

oh-my-agent is built for teams who orchestrate more than they prompt. Next up: native Antigravity plugin emission.

https://github.com/first-fluke/oh-my-agent