DEV Community: gracefullight

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

oh-my-agent: Angular support and stateful configuration merges

gracefullight — Thu, 09 Jul 2026 03:03:54 +0000

Shared tool configurations drift when developers run local agents. Adding a new MCP server to a team setup usually fails to reach existing local configurations, leaving developers with outdated toolsets. We resolved this in our latest CLI release by introducing stateful configuration back-filling. The update merges new servers into local environments while preserving custom developer adjustments.

What's new

Angular stack integration: Added frontend domain detection for angular.json and @angular/* packages in the /stack-set command. The oma-frontend skill now includes angular-rules.md to enforce standalone components, OnPush change detection, and signals.
API evolution patterns: Added API lifecycle patterns based on the MAP framework to oma-architecture. This includes Sajaniemi's 11 variable-role taxonomy to guide naming rules in oma-refactor.
Windows scheduling updates: The schtasks adapter now maps weekly cron ranges like 1-5 or lists like 1,3,5 directly to Windows task scheduler formats.
Model validation: Added vendor validation to the schedule:add command. The CLI now rejects unknown models at registration time rather than failing during execution.

Keeping local environments synchronized across diverse OS targets requires strict validation. These fixes ensure configuration changes flow correctly without disrupting developer-specific settings.

What's fixed

MCP server synchronization: Fixed an issue where SSOT servers added to .agents/mcp.json were only copied if .mcp.json was entirely absent. The CLI now reads the source of truth on every run and merges missing entries.
Test execution reliability: Restructured the project root resolution tests to mock the filesystem walk. This isolates test runs from ambient files on CI runners and avoids false failures.
Market diversity flags: Corrected the --diversity-threshold flag documentation to reflect that the default threshold is not enforced unless the flag is explicitly set.

Cleaning up obsolete protocols reduces token usage and limits agent distraction. Moving to automated dependency management ensures developers stay on current agent APIs without manual maintenance.

What's better

Serena auto-update defaults: Changed serena.auto_update to default to true. The system automatically upgrades the agent via uv on update commands, keeping the memories CLI fallback active.
Codebase cleanup: Removed the unused evaluator-tuning.md protocol file. Project instances are migrated automatically through database migration 016 to reduce project directory clutter.

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: deeper telemetry integration for local agent runs.

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

oh-my-agent: Bluesky broadcasts and Claude workspace auto-trust

gracefullight — Thu, 02 Jul 2026 03:02:26 +0000

When you tell an agent to handle a complex backend migration, hitting a hard cutoff 20 steps in ruins the workflow. We bumped the ceiling and smoothed out the integration edges.

What's new

Bluesky syndication: Release announcements now fan out to Bluesky with rich text tags and external link cards.
Claude auto-trust: Project linking now directly mutates your ~/.claude.json to pre-accept workspace trust, skipping the interactive dialog entirely.
Serena auto-install: The Serena MCP binary now self-installs during project setup and is actively probed by the doctor command.

What's fixed

Premature cutoffs: We raised the max agent turns from 20 up to 40 for backend, frontend, and mobile implementation agents to prevent mid-task failures.
Monorepo state leaks: Running commands from inside a sub-package no longer leaves stray .agents/ directories behind. State is correctly anchored to the project root.
Fragile JSON parsing: Agent publishing steps now use jsonrepair with a 3x retry loop, preventing trailing commas or unclosed braces from aborting a release.
OpenCode dispatch: Subagents now properly inherit the user's default model instead of a hardcoded slug, and routing correctly falls back to native task tools.

What's better

Smarter MCP resolution: Serena now uses --project-from-cwd to gracefully handle execution from nested subdirectories.
Installation UX: The install flow detects native OpenCode tasks and gracefully defaults to a mixed preset when a strict single-vendor lock is unnecessary.
Context isolation: The Antigravity MCP transport now correctly stamps its own context instead of bleeding the Claude Code defaults.

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 our deepsec vulnerability scanner capabilities.

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

oh-my-agent: ZCode workflows and zero-prompt Claude Code trust

gracefullight — Fri, 26 Jun 2026 14:36:55 +0000

oh-my-agent CLI 10.5.0 just shipped. We added native support for ZCode and automated the workspace trust flow for Claude Code.

What's new

ZCode integration: ZCode is now registered as a workflow vendor. Workspace slash-commands in .agents/workflows/*.md are automatically symlinked to .zcode/commands/<name>.md.
Claude Code zero-prompt trust: Project-level installs surgically inject hasTrustDialogAccepted=true into ~/.claude.json. Claude Code applies your workspace permissions immediately instead of blocking on a trust dialog.
Serena binary auto-install: oma install now automatically provisions serena-agent via uv if missing. oma doctor explicitly probes the binary state.
OpenCode picker: OpenCode is available directly in the oma link picker (and you can skip selection entirely if you just want the CLI).

These integrations remove friction for teams spinning up new projects from scratch.

What's fixed

OpenCode model fallback: Removed the hardcoded model slug. OpenCode variants now inherit your configured default model.
OpenCode tools validation: Fixed a ConfigInvalidError on bootstrap by omitting empty tools arrays.
Serena subdirectory execution: Replaced the hardcoded CWD flag with --project-from-cwd so agents can run reliably from any subfolder.
Antigravity MCP context: Prevented the Claude Code context from leaking into the Antigravity runtime during tool execution.
Persistent mode crossover: Fixed a bug where untracked sessions shared state hooks under a generic unknown session ID.

We also gave agents more breathing room to complete complex tasks without premature termination.

What's better

Turn limits raised: Implementation agents (backend, frontend, mobile) now have a 40-turn cap to prevent stopping in the middle of long tasks.
Contract separation: Generated API contracts are written to docs/plans/contracts/ to keep the skill directories pristine.
Cache exclusion: The .serena/cache directory is excluded from default project scans to reduce UTF-8 decoding noise.

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: deeper control over persistent state execution.

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

oh-my-agent: cross-vendor scheduling, Kimi and OpenCode land

gracefullight — Wed, 17 Jun 2026 13:34:11 +0000

Two new vendors and an OS-level scheduler merged into oh-my-agent this week, which means your agents can now run on a clock instead of only when you prompt them. 135 commits, and the theme underneath most of them is the same: stop pinning the agent to a single runtime, and stop leaking resources between sessions.

oh-my-agent is a cross-vendor harness. The point is that a workflow, a skill, or a subagent dispatch should not care which CLI is underneath it. This week pushed hard on that promise.

What's new

Kimi Code CLI is now a first-class vendor: OAuth/KIMI_API_KEY auth, TOML hook install into ~/.kimi-code/config.toml, mode-aware Serena and chrome-devtools MCP, and external dispatch via kimi -p.
OpenCode lands as an extension-class vendor with in-process plugin bridging. Subagent dispatch runs through opencode run --agent <id>, and model slugs are validated against opencode models rather than a hardcoded catalog.
oma schedule:* adds time-based recurring agent jobs that fire independently of any runtime. One SchedulerPort abstracts launchd, systemd --user, crontab, and Windows schtasks, with --cron or natural-language --every intervals.
oma serena reap kills idle language servers. Serena keeps a per-project LSP stack warm with no idle shutdown, so a few open projects pin 1.5GB or more; the reaper trims them and Serena respawns on the next tool call.
oma memory:gc prunes project-local session state and aged Serena run artifacts (defaults: keep 100 sessions, 50 days), while curated knowledge like decisions and designs is never touched.
Two new agents: refactor-engineer (budget-funded, behavior-preserving refactoring) and research-explorer (cited, trust-labeled cross-source synthesis), backed by the new oma-refactor skill.
oma-mobile gains full Flutter and React Native variants, each with a mandated repository-layer response cache (Drift offline-first, TanStack Query plus MMKV).

What's fixed

oma update no longer bulk-deletes vendor skill symlinks on every run, so a mid-update download failure can no longer leave the skills directory empty.
Updates stopped pruning skills that a shipped agent depends on, closing a gap where refactor-engineer could arrive without oma-refactor.
cleanupPeriodDays moved to the top level of Claude Code settings, where it was a no-op nested under env.
Antigravity hooks registered through the /hooks UI are now preserved instead of clobbered on link and update.

What's better

Docs verification got far less noisy: full-repo oma docs verify drops from 6,611 to 394 broken refs (and the web/docs subset from 491 to 29), so the remainder is real drift.
oma hook fires on every prompt, so it now takes an argv fast path and lazy-loads the command tree: invocation went from about 0.54s to 0.32s.
UserPromptSubmit handler budgets were retuned against a p95 of 373ms, dropping the aggregate timeout ceiling from 21s to 15s while keeping headroom over the 2s AgentMemory recall budget.
A large structural pass split all 28 non-test files over 500 lines into focused modules (largest remaining is 491) and consolidated duplicated helpers (type guards, safe writes, vendor unions, exit codes) with no behavior change.
AgentMemory recall now drops facts older than 30 days by default, so long-resolved decisions stop rehydrating into the boundary snapshot.

Gemini CLI is on its sunset path (June 18, 2026), so GEMINI.md generation and the standalone gemini preset were removed, with legacy configs soft-redirecting to antigravity.

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 run the same workflows across whichever CLI they happen to have authenticated. Next up: deeper per-agent model routing across the newly added vendors.

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