Feature request: session-level toggle to suspend OMO and use near-vanilla OpenCode for simple tasks

[smithyyang]

Summary

Please add a session-level toggle / skill / command that can temporarily suspend OMO orchestration and let the current session behave as close as possible to vanilla OpenCode for simple tasks, without uninstalling the plugin or editing config files.

Problem

OMO is extremely valuable for complex, multi-file, multi-stage work, but for very small tasks the extra orchestration can be overkill:

• single-file fixes
• quick grep / lookup
• small docs edits
• simple Q&A or one-shot changes

In those cases, many users would prefer to stay in the same OpenCode installation but temporarily switch to a much lighter execution mode.

Right now the closest option is static config such as sisyphus_agent.disabled = true, but that is not the same as a session-level runtime toggle and is not convenient during an active workflow.

Request

Please support one of these patterns:

1. A session command such as /omo off and /omo on
2. A lightweight skill / mode such as /vanilla, /plain, or /simple-mode
3. A runtime profile switch that disables most OMO orchestration for the current session only

Expected behavior

When the lightweight mode is enabled for the current session:

• suspend Sisyphus takeover / orchestration
• avoid OMO-specific heavy routing where possible
• prefer the base OpenCode build / plan behavior
• disable or minimize OMO-only prompt injections / hooks that are not needed for simple tasks
• keep the plugin installed and re-enableable without restart or config edits

Why this matters

A lot of real workflows alternate between:

• simple low-context tasks, where vanilla OpenCode is faster / cheaper
• complex orchestrated tasks, where OMO is much better

A session-level toggle would let users use both modes naturally instead of choosing one globally.

Related note

This is different from permanently uninstalling OMO, and also different from editing config files like sisyphus_agent.disabled = true before every session. The request is specifically for an in-session switch.

Possible implementation ideas

• /omo off could temporarily disable orchestration hooks for the active session
• /omo off could switch the active session to a minimal compatibility profile
• /omo on could restore the normal OMO stack
• expose this as both a command and a skill so users can opt into it naturally

Thanks - I think this would make OMO much easier to use for mixed workloads.