omg-lock

omg-lock

Switches the current Claude Code session from passive observation into strict oh-my-god enforcement mode. The chosen role's tool allowlist is enforced by the PreToolUse hook, so Claude physically cannot call a tool that the role forbids.

When to use

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

• User says "omg lock executor" or "/omg-lock executor"
• User says "강제 모드로 들어가자" followed by a role name
• User says "lock this to read-only" → use role explorer
• User says "let me write but only in src/" → use role executor (Day 7+ adds path constraints; Day 6 just has role-level tool gating)

Available roles

Defined in roles.json at the plugin root:

• executor — Read, Grep, Glob, Edit, Write, Bash, TodoWrite, NotebookEdit. For code implementation work.
• explorer — Read, Grep, Glob. Strict read-only, for codebase tours and analysis.
• architect — Read, Grep, Glob. Same as explorer for now; Day 7 will differentiate.
• reviewer — Read, Grep, Glob, Bash. For code review work with git inspection (Day 7 restricts Bash to git-only subcommands).

What to do when invoked

1. Determine the role from the user's request. If ambiguous, ask the user which role they want before running anything.

2. Execute the lock script via the Bash tool:

   node "$CLAUDE_PLUGIN_ROOT"/scripts/omg-lock.mjs <ROLE>
   

   Replace <ROLE> with the chosen role name.

3. Read the script's stdout. It will report:

   • Which session was locked (the most recent session by default)
   • The previous role → new role transition
   • The role's description
   • The allowed tool list

4. Summarize the result to the user in plain language:

   • Confirm the role name and its allowed tools
   • Mention that tool enforcement is now active for this session
   • Remind them they can call /omg-release to go back to passive

5. If the script exits non-zero, report the error verbatim and suggest the user check roles.json for available role names.

Example

User: /omg-lock explorer

Claude runs:

node "$CLAUDE_PLUGIN_ROOT"/scripts/omg-lock.mjs explorer

Script output:

[omg-lock] session abc123 — role default → explorer
[omg-lock] description: Read-only exploration. No file modification, no shell.
[omg-lock] allowed tools: Read, Grep, Glob
[omg-lock] strict mode is now ACTIVE for this session.

Claude to user:

Locked session to explorer role. I can now only use Read, Grep, and Glob — no file edits, no shell. Say /omg-release when you want to go back to passive mode.

Caveats

• The lock applies to the most recent session in the oh-my-god DB. In a normal Claude Code session that will be the one you're in right now. If you're running multiple Claude Code instances against the same ~/.omg/state.db, pass --session <id> explicitly.
• Locking does NOT retroactively affect tool calls that already happened in this turn. It affects the next PreToolUse check.
• Stop-hook gate judgment runs regardless of role. The tool boundary is orthogonal to the evidence-based gate — lock only decides which tools Claude can call, not whether Claude's work is accepted as complete.