kasy remove

Implementation

1. Commit the project first, just in case.

2. Run the command for the feature you want to remove:

   kasy remove ads
   kasy remove revenuecat
   kasy remove notifications

   The CLI removes code, dependencies, and related config entries. Auth, Settings, and Push also work: kasy remove authentication, kasy remove settings, kasy remove notifications (leaves NoOp stubs so the app still compiles).

   It does not delete backend data or a Firebase companion project in GCP (only removes the module from the app).

3. Confirm what's still on:

   kasy add --list

   Via MCP: "what's still on in the project?" (list_features).

Information

What the command undoes

For the removed feature, the CLI:

1. Sets the flag in lib/core/config/features.dart back to false
2. Drops the feature's --dart-define entries from .vscode/launch.json
3. Drops the same entries from the run and run-prod targets in the Makefile
4. Drops the feature's variables from .env.example
5. Drops the feature's dependencies from pubspec.yaml
6. Reverts the flags in kit_setup.json
7. Deletes the files and folders the feature's patch had copied in
8. Regenerates no-op stubs in place of the removed code, so the project still compiles
9. Regenerates router.dart and main.dart without the feature's routes and init
10. Runs flutter pub get and build_runner at the end

Shared dependency

sentry_flutter is used by three features: sentry, revenuecat and facebook. When you remove one of them, the CLI checks whether the others are still on before dropping the dependency from pubspec.yaml. If it's still needed, it says so and keeps it.

Cases that need extra care

Last updated on 08/23/2026