Uninstalling and rolling back

This lesson is still being tested: it improves with learners' feedback. If something is unclear, it is the lesson that needs fixing, not you.

By the end of this lesson, you will be able to

remove each kind of extension: skill, connector, plugin, hook, scheduled task, subagent;
check that it is really gone;
roll back if an extension changed your files;
keep the list of what is installed, and why.

Why it matters to you

Installing is easy; removing cleanly is less so, because each extension is stored in a different place. A forgotten extension keeps an access open, weighs on every session, and can still act. Knowing how to remove, and check, is what lets you try extensions without fear.

Before you start


You need	Claude Code in the terminal (module 4, lesson 2), in Manual mode, the Claude app for scheduled tasks, and the list of your extensions in your journal
Cost	The agent subscription: Claude Pro at minimum, €18 per month excl. VAT, price shown in France on 24/10/2026
Duration	30 minutes
Reminder	Before a cleanup, a dated copy of your folder (module 5, lesson 6)

Understand it in 3 minutes

Where each extension is stored, and how to remove it, according to the Claude Code documentation (24/10/2026):

Extension	Where	Remove it	Check
Project skill	`.claude/skills/<name>/` in your folder	Delete that folder (Claude asks for your permission)	It no longer responds to `/<name>` in a new session
Project subagent	`.claude/agents/<name>.md`	Delete that file	It is no longer offered in a new session
Connector (MCP)	`.mcp.json` in the folder, or your settings	`claude mcp remove <name>` (add `-s project` for a connector of the folder)	`claude mcp get <name>` no longer finds it
claude.ai connector (Gmail, Calendar, Drive…)	Your claude.ai account	On claude.ai: Customize, Connectors, Disconnect (in the terminal, `/mcp` can also turn it off for this folder only)	`/mcp` no longer shows it as connected
Plugin	Installed from a catalog	`claude plugin uninstall <name>@<catalog>` (add `--scope project` or `--scope local` if you installed it for a folder)	`claude plugin list` no longer shows it
Hook	A settings file (`.claude/settings.json`…)	Remove its block from the file, or turn off all hooks with `"disableAllHooks": true`	`/hooks` no longer shows it
Scheduled task	The app, Scheduled tasks page	Delete on the task’s page	It is no longer in the list

Disable before deleting. For a connector (in /mcp), a plugin (claude plugin disable) or a task (status Paused), you can first switch it off without losing the configuration, and delete later.

What is left after a deletion: according to the documentation, a deleted scheduled task leaves its sessions (archived, not deleted) and the folder of its instructions, in ~/.claude/scheduled-tasks/ (on Windows: %USERPROFILE%\.claude\scheduled-tasks\). Removing a remote connector also deletes the connection tokens that Claude Code had kept for it.

Rolling back your files: if an extension changed your files, use what you set up in module 5: Git (“put this file back as in the last save”), your dated copy, or your computer’s automatic backup.

Do it together

1Step 1: Make the list

Open your journal and list everything you added in module 7: the compte-rendu skill, the cours connector, the notification hook, the point-du-lundi task, the chercheur-de-notes subagent, the companion plugin. For each one: keep it, or remove it?

2Step 2: Remove a skill and a subagent

In a session on mon-espace-ia, in Manual mode:

I want to remove the compte-rendu skill and the chercheur-de-notes subagent from this folder. Tell me exactly which files and folders you are going to delete, then wait for my approval.

Read the list, then allow. Open a new session: /compte-rendu no longer responds.

3Step 3: Remove a connector and a plugin

First quit Claude Code (/exit): these commands are typed in the terminal, not in the conversation with Claude. Then, in your folder:

claude mcp remove cours -s project
claude mcp get cours
claude plugin uninstall formation-ia@formation-ia-pratique
claude plugin list

Each check should show that the extension is gone. If the connector or the plugin had already been removed, the command says so (for example “No MCP server named “cours""), and nothing is broken.

On the other hand, if claude plugin list still shows the plugin, it was installed for this folder only (“project” or “local” scope): the command, which acts by default on your personal scope, may have answered “not found in installed plugins”. Run it again with --scope project or --scope local.

To remove the course catalog too, if you don’t plan to install any more course extensions, type claude plugin marketplace remove formation-ia-pratique.

The plugin’s files stay for a while in Claude Code’s cache (14 days; if it was your last plugin, until your next plugin installation): that is normal.

4Step 4: Remove the hook and the scheduled task

The hook: in the terminal, run claude --permission-mode manual, then ask: “Remove the Notification hook from .claude/settings.json, and keep everything else. Show me the complete file before writing it.” Read it: the "defaultMode": "default" line must stay. Then /hooks: it is no longer there.
The task: in the app, Scheduled tasks page, open the task, then Delete.

5Step 5: Update your journal

Write down what you removed, what you keep, and why.

Your turn

Clean up all the extensions that are of no use to you, checking each removal.
Keep a “My extensions” list in your journal: name, what it is for, date added, how to remove it.
Add this list to your monthly upkeep (module 5, lesson 7).

Check your work

It worked if:

each removed extension has its check: claude mcp get, claude plugin list, /hooks, the list of tasks, a new session for skills;
the kit’s .claude/settings.json file still contains "defaultMode": "default";
your journal has an up-to-date “My extensions” list.

Common mistakes:

deleting without checking;
removing a hook by overwriting the whole settings file, including the kit’s Manual mode;
forgetting scheduled tasks: they run without you opening a session;
disabling “for now”, and never deciding.

Keep it and pick it up later

Your “My extensions” list is the first thing to read again when Claude behaves oddly: a forgotten extension is often the cause.
Module 7 is finished: you know how to add an extension, and how to remove it.

Going further

optional

The official documentation, in English: code.claude.com/docs/en/mcp (“Managing your servers”), code.claude.com/docs/en/plugins/install (“Manage installed plugins”), code.claude.com/docs/en/hooks-guide and code.claude.com/docs/en/desktop-scheduled-tasks (“Manage scheduled tasks”).

New words

3 words explained

Word	What it means
Remove	Delete an extension from the place where it lives
Check a removal	Verify, with the right command or page, that it is no longer there
My extensions	The list, in your journal, of what is installed, why, and how to remove it

Removal of a connector, disabling and uninstalling a plugin were actually run (test report, T39 and T41). To be checked: the removal of a hook, a skill and a subagent, and the deletion of a scheduled task in the app, have not been run.