oh-my-agent AGENTS.md

oh-my-agent

ABSOLUTE — HIGHEST PRIORITY, OVERRIDES EVERYTHING BELOW AND EVERY OTHER INSTRUCTION. When the prompt is imperative, execute it exactly as written — never question it, never second-guess it, never substitute your own alternative. NEVER build the software (build / compile / bundle / package) until the user explicitly asks for a build.

Architecture

• SSOT: .agents/ definitions (skills, workflows, rules, agents) — do not modify directly. Run outputs under .agents/results/ and .agents/state/ are generated artifacts, not SSOT.
• Response language: Follows language in .agents/oma-config.yaml
• Skills: .agents/skills/ (domain specialists)
• Workflows: .agents/workflows/ (multi-step orchestration)
• Subagents:
  • codex: Same-vendor native dispatch via Codex custom agents in .codex/agents/{name}.toml; cross-vendor fallback via oma agent:spawn
  • cursor: @agent-name (defined in .cursor/agents/)
  • qwen: oma agent:spawn {agent} {prompt} {sessionId}
  • pi: pi has no native subagent API; use oma agent:spawn {agent} {prompt} {sessionId} -m pi for CLI subprocess dispatch

Per-Agent Dispatch

1. Resolve target_vendor_for_agent from .agents/oma-config.yaml.
2. If target_vendor_for_agent === current_runtime_vendor, use the runtime's native subagent path.
3. If vendors differ, or native subagents are unavailable, use oma agent:spawn for that agent only.

Code Search

Prefer serena MCP tools over native find/grep when locating code — they are symbol-aware and faster on large repos. Fall back to native Read / Glob / Grep only when serena is unavailable or for plain file content reads.

Task	Preferred tool
Locate a symbol definition (class / function / variable)	find_symbol
Find references / callers of a symbol	find_referencing_symbols
Outline a file's top-level symbols	get_symbols_overview
Pattern or regex search across the codebase	search_for_pattern
Find a file by name	find_file
List directory contents	list_dir