How to Disable i-Have-ADHD Mode and Return to Normal Output

To turn off i-have-adhd mode, say "stop adhd mode" or "normal mode" in chat, disable the plugin with claude plugin disable i-have-adhd, or remove the always-on flag file at ~/.claude/.i-have-adhd-always.

The i-have-adhd skill modifies AI assistant output to be more ADHD-friendly with shorter paragraphs, bullet points, and visual structure. When you need standard formatting again, the ayghri/i-have-adhd repository provides multiple exit paths depending on how you activated the mode.

Disable with Voice Commands

The simplest method requires no terminal access. Just type the trigger phrase directly in your chat session.

According to skills/i-have-adhd/SKILL.md lines 21-23, the skill monitors for these exact phrases:

• stop adhd mode
• normal mode

When detected, the skill confirms the change in one line and immediately reverts the assistant to its default output style. This works for temporary ADHD mode activations and always-on sessions alike.

# Type in any active chat session

stop adhd mode

Disable the Plugin Entirely

For users who installed i-have-adhd as a plugin, disable it through your agent's CLI. As documented in INSTALL.md lines 34-35 and 42, commands vary by platform:

Claude Code:

claude plugin disable i-have-adhd

Codex:

codex plugin remove i-have-adhd

This removes the skill from availability until explicitly re-enabled. The plugin.json file registers the skill under the exact name i-have-adhd, which must match your disable command.

Remove the Always-On Flag

If you previously enabled permanent ADHD mode at session start, remove the persistence flag. The hooks/always-on.sh script checks for this file on launch and loads the skill automatically when present.

For Claude Code:

rm ~/.claude/.i-have-adhd-always

This returns you to on-demand mode — the skill remains installed but inactive until you:

• Re-create the flag: touch ~/.claude/.i-have-adhd-always
• Or manually trigger ADHD mode in chat

As shown in INSTALL.md lines 38-42, the flag file is the same one created during always-on setup, making the toggle fully reversible.

Which Method Should You Use?

Situation	Recommended Action
Temporary switch	Say "stop adhd mode" in chat
Done using the skill	claude plugin disable i-have-adhd or codex plugin remove i-have-adhd
Want control per session	rm ~/.claude/.i-have-adhd-always

All three methods are persistent within their scope: voice commands affect the current session, plugin disable affects all future sessions until re-installed, and flag removal affects session start behavior until the flag is recreated.

Summary

• Say "stop adhd mode" or "normal mode" for instant deactivation without leaving chat — defined in SKILL.md lines 21-23
• Run claude plugin disable i-have-adhd or codex plugin remove i-have-adhd to completely uninstall plugin functionality — documented in INSTALL.md lines 34-35
• Delete ~/.claude/.i-have-adhd-always to disable session-start persistence while keeping the skill available — controlled by hooks/always-on.sh

Frequently Asked Questions

How do I know if i-have-adhd mode is currently active?

The assistant's output style indicates status. ADHD mode produces short paragraphs with heavy bullet structure and visual separators. Normal mode uses standard paragraph formatting. If uncertain, saying "stop adhd mode" causes no harm — the skill simply confirms you're already in normal mode if no change is needed.

Can I re-enable i-have-adhd mode after disabling it?

Yes. After voice-command deactivation, say "adhd mode" or your configured trigger to reactivate. After plugin disable, re-run your install command. After flag removal, run touch ~/.claude/.i-have-adhd-always again. The skill never deletes itself; all disable methods are reversible.

Does removing the always-on flag uninstall the skill?

No. The flag only controls automatic loading at session start. The skill remains installed and available for manual activation. This distinction lets you choose between convenience (always-on), control (flag removed, manual trigger), or complete removal (plugin disable).

Will disable commands work if I installed from source instead of as a plugin?

Source installations without plugin packaging require manual cleanup: remove the skill directory from your agent's skills path and restart the session. The claude plugin disable and codex plugin remove commands only operate on formally registered plugins listed in plugin.json.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}