OmO
Oh My OpenAgentv4.7.5

Agents

The OmO agent catalog and how the work is split.

Sisyphus orchestrating tasks in parallel

OmO ships a small cast. Four agents are the lanes you enter on purpose; the rest are specialists Sisyphus calls when it needs them.

Core Ordering

The four primary agents have a stable tab order in OpenCode: Sisyphus, Hephaestus, Prometheus, then Atlas. Other agents follow.

Tool Boundaries

These restrictions are part of the harness. They stop "smart" agents from doing unsafe work in the wrong role.

AgentConstraint
OracleRead-only consultation. No writes, edits, or delegation.
LibrarianResearch-only. No writes, edits, or delegation.
ExploreSearch-only. No writes, edits, or delegation.
Multimodal-LookerMedia analysis, read-focused.
AtlasOrchestrates plan execution but delegates implementation units.
Sisyphus-JuniorImplements one assigned unit and must verify before returning.

Category Workers

When task receives a category, OmO spawns a Sisyphus-Junior-like worker tuned for that domain. The category picks the model profile; skills add instructions and MCPs.

CategoryWorker behavior
visual-engineeringFrontend/UI/design work. Pair with frontend-ui-ux and browser verification.
ultrabrainHard reasoning and architecture. Keep the prompt goal-oriented.
deepAutonomous research plus implementation. Good for hairy but coherent work.
artistryCreative or non-conventional approaches.
quickSmall changes. Don't use it for visual work just because the diff is small.
writingDocumentation and prose.

Background Agents

Run specialists in the background when the main session can keep moving without the result.

task({
  subagent_type: "explore",
  load_skills: [],
  run_in_background: true,
  prompt: "Find all auth policy implementations and summarize file paths.",
});

Use background mode for independent research. Stay synchronous when the result blocks the next implementation decision.

On this page