@r3dlex/oh-my-auggie

oh-my-auggie

Multi-agent orchestration for Augment Code's auggie CLI — the "oh-my-*" experience for auggie. OMA remains the plugin/workflow layer, and super-oma is being shipped as an optional tmux/HUD supervisor shell on top without rewriting existing OMA semantics.

Installation

Prerequisites

• auggie >= 0.22.0 — install docs
• node >= 18 (for the MCP state server)

Marketplace Install (recommended)

auggie plugin marketplace add r3dlex/oh-my-auggie
auggie plugin install oma@oh-my-auggie

Then initialize OMA in your project:

/oma:setup

Optionally configure MCP servers (adds state persistence and advanced tooling):

/oma:mcp-setup

super-oma roadmap snapshot

super-oma is being delivered as an additive wrapper around Auggie + OMA:

• Wrapper, not rewrite — existing /oma:* workflows stay intact.
• Optional tmux supervisor UX — HUD, activity panes, attach/reconcile ergonomics.
• Graceful degraded mode — status/doctor flows continue to work from .oma state even when tmux is unavailable.

OMA remains the stable entrypoint and compatibility layer while super-oma rollout continues.

Manual Install

git clone https://github.com/r3dlex/oh-my-auggie.git
cd oh-my-auggie
auggie plugin install --source ./plugins/oma oma@oh-my-auggie

Then initialize OMA in your project:

/oma:setup

Optionally configure MCP servers (adds state persistence and advanced tooling):

/oma:mcp-setup

OMA — installed and ready. What do you want to build?

Commands

Once installed, these slash commands are available:

Command	Description
/oma:autopilot	Full autonomous pipeline — expand, plan, implement, QA, validate
/oma:ralph	Persistence loop — keeps working until all acceptance criteria pass
/oma:ultrawork	High-throughput parallel execution via concurrent subagents
/oma:team	Coordinated team of N agents
/oma:ultraqa	QA cycling: test, verify, fix, repeat
/oma:ralplan	Consensus planning with Architect + Critic review
/oma:plan	Strategic planning with analyst/architect review
/oma:cancel	Cancel active mode and clear state
/oma:status	Show current mode and state
/oma:ask <model>	Query with a specific model
/oma:note	Write to notepad (priority, working, manual)
/oma:doctor	Diagnose installation issues

Keyword Triggers

Drop the /oma: prefix — these activate automatically when detected in conversation:

Keyword	Activates
autopilot	/oma:autopilot
ralph, "don't stop"	/oma:ralph
ulw, ultrawork	/oma:ultrawork
ultraqa	/oma:ultraqa
ralplan	/oma:ralplan
team N:agent	/oma:team
canceloma	/oma:cancel
deslop, "anti-slop"	/oma:deslop
ccg	/oma:ccg
deep interview	/oma:interview

OMA — parallel agents, persistent state, zero dependency overhead

Architecture

oh-my-auggie/
├── plugins/oma/
│   ├── agents/          # 19 agents: architect, executor, explorer, planner, verifier, etc.
│   ├── commands/        # 44 commands: autopilot, ralph, ultrawork, team, ultraqa, etc.
│   ├── hooks/           # 10 hooks: session-start, delegation-enforce, stop-gate, cost-track, keyword-detect, etc.
│   ├── skills/          # 36 skills: ralph, ultrawork, ultraqa, ralplan, ccg, etc.
│   └── mcp/
│       └── state-server.mjs   # MCP state server (12 tools: state, notepad, skill, intent)
└── .augment-plugin/
    └── plugin.json      # Auggie plugin manifest

State files (stored in .oma/ — git-ignored):

File	Purpose
.oma/state.json	mode, active, iteration
.oma/notepad.json	priority, working, manual sections
.oma/task.log.json	architect/executor verdict history

Profiles

Profile	Description
Community (default)	Full parallelization, no approval gates
Enterprise	Cost-aware model routing, ADR requirements, approval gates

Enterprise is activated by creating .oma/config.json with { "profile": "enterprise" }. Enterprise only adds rules — it never removes community features.

Hook Context Injection

Two hooks can inject context into the agent after each tool call. Both are disabled by default:

Key	Default	Description
hooks.costTracking	false	Per-tool credit/cost estimates logged to .oma/cost-log.json
hooks.statusMessages	false	OMA mode, task progress, and notepad injected into agent context

Enable via /oma:config set hooks.costTracking true or in .oma/config.json:

{ "hooks": { "costTracking": true, "statusMessages": true } }

Development

# Run typecheck, build, unit+coverage, and CLI e2e
npm run typecheck
npm run build
npm run test:coverage
bats e2e/oma-cli.bats e2e/super-oma-cli.bats

# Validate all manifests
node -e "
  const fs = require('fs');
  const files = [
    '.augment-plugin/marketplace.json',
    'plugins/oma/.augment-plugin/plugin.json',
    'plugins/oma/.augment-plugin/.mcp.json',
    'plugins/oma/hooks/hooks.json',
    '.claude-plugin/plugin.json'
  ];
  for (const f of files) {
    try { JSON.parse(fs.readFileSync(f)); console.log('OK: ' + f); }
    catch(e) { console.error('FAIL: ' + f + ' - ' + e.message); process.exit(1); }
  }
"

Security

Please review our Security Policy for supported versions and vulnerability reporting guidelines.

Links

Resource	URL
Augment Code	https://www.augmentcode.com
auggie CLI docs	https://www.augmentcode.com/docs/cli
Plugin docs	https://www.augmentcode.com/docs/cli/plugins
Hooks docs	https://www.augmentcode.com/docs/cli/hooks
MCP docs	https://www.augmentcode.com/docs/cli/integrations
oh-my-auggie	https://github.com/r3dlex/oh-my-auggie

Sponsor

:heart: Love oh-my-auggie? Consider sponsoring its development.

Your sponsorship directly funds the time and energy poured into making multi-agent orchestration accessible to every developer on the Augment Code platform. Every contribution — no matter the size — helps keep the project alive, responsive, and improving.

👉 Sponsor on GitHub

One-time and recurring options available. Sponsors get recognized in the project README and release notes.

oh-my-auggie is not affiliated with Augment Code. "auggie" and "Augment Code" are trademarks of their respective owners.