omg-release

omg-release

Inverse of omg-lock. Puts the current session back into passive mode by resetting session.role to default, so the PreToolUse scope hook stops enforcing the role's tool allowlist and Claude can use any tool again.

Important: release only lifts the tool boundary. The Stop-hook gate judgment (Day 4) still runs after every turn, so verification and retry-on-fail remain active.

When to use

The user invokes this when they want to relax the current session. Typical triggers:

• User says "omg release" or "/omg-release"
• User says "unlock" or "풀어줘"
• User finished the strict-mode task and wants to chat freely again

What to do when invoked

1. Execute the release script via the Bash tool:

   node "$CLAUDE_PLUGIN_ROOT"/scripts/omg-release.mjs
   

2. Read the stdout. It will report:

   • Which session was released
   • The previous role → default transition
   • A reminder that gate judgment still runs

3. Summarize to the user:

   • Confirm the release
   • Remind them Stop-hook verification is still active
   • Offer to lock again if they want strict mode back

4. If the script reports "already in default (passive) mode", just tell the user the session was already passive — no action needed.

Example

User: /omg-release

Claude runs:

node "$CLAUDE_PLUGIN_ROOT"/scripts/omg-release.mjs

Script output:

[omg-release] session abc123 — role executor → default
[omg-release] tool boundary enforcement disabled.
[omg-release] Note: Stop-hook gate judgment still runs. Release only lifts the PreToolUse tool allowlist.

Claude to user:

Released session back to passive mode. The tool allowlist is no longer enforced. Stop-hook gate judgment still runs after every turn, so your work will still be verified. Say /omg-lock <role> if you want strict mode back.

Caveats

• Like omg-lock, this defaults to the most recent session. Use --session <id> to target a specific one if you're running multiple Claude Code instances.
• Release is not a kill switch. It only disables the tool boundary. To fully disable oh-my-god for a session you'd have to uninstall the plugin or edit .claude/settings.json to remove the hook registrations.