Oh My Rigel

What Oh My Rigel is

Oh My Rigel is an orchestration layer over OpenCode: it inherits the orchestration and delegation of Oh My OpenCode (OmO) and brings them to the OpenCode V2 plugin runtime. OpenCode stays an independent dependency; Rigel is not a fork or a distribution of OpenCode.

For a programmer it brings planning, delegation to specialists, continuity across long tasks, integrated tools and a more efficient workflow. It is worth it if you already work with OpenCode and want that agent workflow without changing host: a single assistant does not split the work or keep context across sessions.

Verifiable reason it exists: to bring the OmO feature set to OpenCode V2 without dropping surfaces (agents, delegation, skills, permissions, tools, context and continuity); functional compatibility comes first and fork-specific improvements come after. The OmO functionality ported to V2 is confirmed; the additional beta layer (the Judge and the profile skills) is polished separately.

Catalogue

Rigel brings the full OmO feature set to OpenCode V2. Instead of one assistant doing everything, you get a small team that plans, delegates and keeps its own context.

• Delegate to specialists

  Hand a task to the right agent (planner, researcher, reviewer) and get a result checked before it is called done.

• Keep going on long tasks

  Context and pending work survive compaction, so a long job continues instead of restarting.

• Work in the background

  Slow jobs keep running while you move on, and wake you when they finish.

• Use your own models

  Mix frontier and cheap models; the OmO agents in the inventory carry a default model and a fallback chain when they are declared.

Browse the full catalogue: every function and area in detail.

Relationship with Oh My OpenCode

Oh My OpenCode (OmO) is the parent project. Oh My Rigel (OMR) is a community fork that migrates the OmO feature set to the OpenCode V2 runtime. OpenCode is the host program and stays separate from OMR. The installation also adds an extra beta layer, kept apart in its own profile, to be polished later. OMR keeps attribution to the parent project.

Install

Install from the repository source route.

The OmO functionality on OpenCode V2 is complete and confirmed. The installation additionally includes an external BETA layer of agents (including a Judge) and skills from the profile, to be polished later.

Install and run the Oh My Rigel V2 developer preview from its public source.

Safety requirements:
- Inspect the checkout, AGENTS.md files, repository rules, README.md,
  OH-MY-RIGEL.md, FORK.md, CONTRIBUTING.md, script/agent/setup.sh,
  profiles/gabo/validate-profile.mjs, profiles/gabo/apply-v2-agent-layer.mjs,
  profiles/gabo/switch-live-plugin-to-native-v2.mjs, and
  profiles/gabo/materialize-v2-skills.mjs before changing anything.
- Rigel targets OpenCode V2 only. Detect the installed OpenCode version and
  stop unless it is V2. If OpenCode must be updated, use the current official
  OpenCode installation method and verify the resulting version.
- Confirm that no OpenCode process is running and that this installation will
  not reuse an active V1 installation. Do not create a parallel V1/V2 setup.
- Discover the actual OpenCode V2 config, data, state, cache, plugin, skills,
  and goal-state paths on this machine. Do not assume paths, services,
  credentials, or package managers. Stop and ask for help if ownership or
  isolation is uncertain.
- Never print, copy, or commit credentials or private configuration.

Scope note:
- The Oh My Rigel V2 runtime is the OmO functionality ported to OpenCode V2 and
  confirmed on V2; that ported set is complete.
- The installation additionally includes an external BETA layer of agents
  (including a Judge) and skills from profiles/gabo, which is being polished.
  Keep that extra layer distinct from the confirmed OmO set.

Installation requirements:
1. Use the v2-mirror branch of https://github.com/GaboEI/oh-my-rigel.
2. From the checkout root, run script/agent/setup.sh to verify tools, install
   dependencies, and build.
3. From the checkout root, run node profiles/gabo/validate-profile.mjs.
4. Set RIGEL_V2_HOME to the confirmed V2 home, RIGEL_V2_CONFIG to the absolute
   path of the active V2 JSON config, and RIGEL_V2_USER_ROOT to a dedicated
   Rigel state directory. The variable name RIGEL_V2_LAB_ROOT is a historical
   spelling of that state directory: do not create or require a laboratory or
   service.
5. With those explicit variables, from the checkout root run the user lifecycle
   installer: node profiles/gabo/rigel-v2-user-install.mjs install --version 1.
   It materializes the native runtime and generated agent manifest, exposes the
   V2 skills, and registers the runtime in the selected V2 config. It refuses
   any path that resolves under a V1 root and never launches OpenCode.
6. Verify that the V2 config registers the generated Rigel runtime, launch the
   normal OpenCode V2 command, and confirm that Rigel reports its native V2
   runtime as active. Do not claim unavailable features.

Constraints:
- Do not remove OpenCode V1, the host program, and do not run any destructive
  action without explicit approval from the operator: first report what you
  would do and wait.
- Preserve unrelated and foreign configuration, plugins, skills, and state.
  Only Rigel-owned entries and state may be created, changed, or removed.
- Do not invent commands. Use only the commands in this prompt and the
  canonical guide. If a step is unclear, stop and ask.

Report the detected OpenCode version, resolved non-secret paths, commands run,
checks passed, and remaining limitations. If any safety condition cannot be
demonstrated, do not install or launch anything; explain the blocker and ask
for help.

GitHub

• The omo setup command configures the parent Oh My OpenCode product, not Oh My Rigel.
• rigel setup does not exist yet.

Installing OpenCode V2 for the first time? The official guide requires removing OpenCode V1 and its remnants before a clean V2 install. OpenCode V1/V2 (the host program) and Oh My Rigel V1/V2 (this plugin) are distinct. OpenCode migration guide

Basic configuration

Configuration is declarative and layered.

~/.omo/omo.jsonc

• The omo setup command configures the parent Oh My OpenCode product, not Oh My Rigel.
• rigel setup does not exist yet.

Agent configuration

See each agent's default model (the beta-layer Judge declares none), the selection criteria and how to change an agent's model in the detailed guide.

Open the detailed models, skills and commands guide

Agents, skills and commands

Agents: the team that plans, delegates and runs tasks. The OmO agents in the inventory carry a default model and a fallback chain when they are declared; that is the detail of which AI runs them.

Skills: specialized instructions that extend how the agent works on specific tasks, without changing the product's core.

Commands: invocable actions for concrete flows; you run them when you need them. Each guide card details what it does and what it touches.

Open the models, skills and commands guide

Plugin lifecycle

Check status, reinstall, update, roll back or uninstall Oh My Rigel without touching OpenCode V2 or unrelated plugins.

Lifecycle commands

Run from the checkout root. These are the installer's real operations; none removes OpenCode V2 or unrelated plugins.

1. Status and health

   node profiles/gabo/rigel-v2-user-install.mjs status

2. Idempotent reinstall

   node profiles/gabo/rigel-v2-user-install.mjs install --version 1

3. Version transition and state migration

   node profiles/gabo/rigel-v2-user-install.mjs upgrade --version 2

4. Byte-identical revert to the previous version

   node profiles/gabo/rigel-v2-user-install.mjs rollback

5. Uninstall: removes only Rigel state

   node profiles/gabo/rigel-v2-user-install.mjs uninstall

These commands use the same variables you verified in Install (RIGEL_V2_HOME, RIGEL_V2_CONFIG and RIGEL_V2_USER_ROOT). If you open a new shell, export them again before running.

Uninstall removes only the Oh My Rigel entries and skills; it preserves OpenCode V2, your configuration and other plugins.

Not to be confused with removing OpenCode V1 (the host) to migrate to V2. OpenCode migration guide

Help

If something fails: check the status with the lifecycle command shown above, review the OpenCode (host) version and paths, and follow the repository guide. Never share keys or credentials in any report.

GitHub issues (v2-mirror branch)