deauthorize

Revoke Edit/Write authorization by deleting a session-specific auth file.

3|1|Updated Oct 9, 2025

Search Tags:#authorization #security #session management #workflow control #revoke

Ready to run

npx skills add https://github.com/OmniNode-ai/omniclaude --skill deauthorize

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deauthorize
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/deauthorize
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill deauthorize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows users to revoke authorization for sensitive operations like editing or writing within the current session, enhancing security and control.

Core Features & Use Cases

Session-Specific Revocation: Limits the scope of authorization removal to the active session.
Security Enhancement: Provides a quick way to disable Edit/Write capabilities when no longer needed or if security is a concern.
Use Case: After completing a sensitive code modification, you can use /deauthorize to ensure no further unintended changes can be made without explicit re-authorization.

Quick Start

Run the deauthorize skill to revoke your current session's work authorization.

Frequently Asked Questions about deauthorize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I revoke session authorization for Claude Code edit and write operations?▼

Revoking session authorization involves deleting the session-specific authorization file located in the /tmp/omniclaude-auth/ directory. This action immediately disables Edit/Write operation capabilities within the active Claude Code session.

When should I remove write permissions during an active coding session?▼

You should remove write permissions during an active session after completing sensitive code modifications. This security measure ensures no further unintended changes can be made without explicit re-authorization.

Does revoking work authorization affect the entire environment or just the current session?▼

Revoking work authorization affects only the current Claude Code session. It targets and deletes a session-specific authorization file, limiting the scope of the security restriction to the active environment.

What is the best way to disable edit capabilities after a sensitive workflow?▼

The best way to disable edit capabilities after a sensitive workflow is to execute a session-specific revocation command. This removes the authorization file from the temporary directory, instantly halting edit operations.

Why does my session still allow edits after I tried to restrict workflow control?▼

If your session still allows edits, the authorization file in /tmp/omniclaude-auth/ may not have been successfully deleted. You must ensure the revocation command properly executes to restore workflow control restrictions.

Can I re-enable write operations after revoking session authorization?▼

Yes, you can re-enable write operations after revoking session authorization by explicitly re-authorizing the session. The revocation simply deletes the current file, requiring a new authorization to perform edit operations again.