Uninstall ADT

Uninstalling the Agentic Development Toolkit (ADT) removes its global files and coding-agent integrations from your computer. It does not remove anything from your FileMaker files or project folders.

  • Web Viewer app source remains. Uninstalling ADT does not delete app source stored in persistent data. If you also remove ADT's FileMaker components, an app may stop working because it can depend on ADT-installed scripts and custom functions.

  • Your FileMaker files, schema, and data are untouched. Nothing is removed from a file unless you choose to remove ADT's components in the optional step below.

  • Your project folders remain yours. A project is a plain directory and a git repo. Keep it, archive it, or delete it — nothing about uninstalling touches it.

  1. Optional: remove ADT's components from a FileMaker file.

    Files provisioned for Web Viewer work contain scripts, custom functions, and layouts installed by ADT. You can ask your agent to take them out:

    Copy 
    Remove ADT's components from my connected FileMaker file. Leave everything else in the file alone.

    Removal is surgical: only what ADT owns comes out.

    Warning  Removing components can stop Web Viewer apps A Web Viewer app may depend on scripts or custom functions installed by ADT. Removing those components can stop the app from working, but it does not delete the app source stored in persistent data.

  2. Uninstall ADT from your computer.

    Ask your agent:

    Copy 
    Uninstall ADT from this machine.

    Tell me what you removed and what you left behind.

    The agent runs adt uninstall. It removes ADT's global files, unregisters the standard agent plugin from supported coding agents, and removes the Claude plugin from detected Claude applications. If an ADT.fmplugin from a release before 0.8 is still in FileMaker Pro's Extensions folder, the uninstaller removes it too — 0.8 itself leaves nothing there. Backups of changed configuration are made by default.

    Restart any coding-agent applications or CLI sessions that were open during the uninstall.

  3. Optional: clean up the rest.

    • Delete any project folders you no longer want. They're ordinary directories.

    • Remove stored credentials: connecting a file saved its [Full Access] account to your macOS keychain. Open Keychain Access, search for your FileMaker file's name, and delete the entries you find.

Reinstalling later

Re-run the .pkg installer — it re-applies everything from a first install. Your project folders still work, and a file that kept its components reconnects without provisioning them again. See Install and Connect.