Remove ADT components from a file

Removing ADT components deletes ADT-owned custom functions, layouts, and scripts from one FileMaker file. It does not delete Web Viewer app source stored in persistent data, remove the source from your project, or change FileMaker objects outside the Agentic Development Toolkit folders.

Before removing the components

Removing these components can stop a Web Viewer app from working because the app may call scripts or custom functions installed by ADT. It also removes the layouts and scripts that the coding agent uses to work through your FileMaker Pro session. The app source stored in persistent data remains in the file.

Make a backup of the FileMaker file before removal. If you have customized an ADT-owned component, decide whether you need to preserve that work outside the Agentic Development Toolkit folders.

Remove the components

Ask your coding agent to preview the removal first:

Copy 
Show me which ADT components would be removed from this FileMaker file. Do not remove them yet.

Review the custom functions, layouts, and scripts in the agent's report. Then ask the agent to remove them:

Copy 
Remove the ADT components from this FileMaker file and verify that they are gone.

ADT requires explicit confirmation before it writes the removal. Components that have changed since ADT installed them require an additional confirmation so that customized work is not deleted silently.

What remains

Removal leaves these items unchanged:

  • Web Viewer app source stored in persistent data

  • Web Viewer app source and the vendored @adt/fmdapi JavaScript library in the project

  • Tables, fields, layouts, scripts, and custom functions that ADT does not own

  • The global ADT installation on your computer

To remove the global installation as well, follow Uninstall ADT after you remove the file components.