Install ADT components in a file

ADT adds custom functions, layouts, and scripts to a FileMaker file to support Web Viewer development. Each type is grouped in a folder named Agentic Development Toolkit.

When components are required

Components support Typegen, the live browser bridge, FileMaker script calls, record requests routed through the Web Viewer adapter, and storing app source in FileMaker persistent data.

They are not required for native schema, script, or layout work. Do not install them only to let an agent inspect or author a FileMaker file.

Creating a Web Viewer app installs the required components when they are absent. You can also ask the agent to install them without creating an app:

Install ADT's components in this FileMaker file and verify them.

Check or update components

Ask the agent to inspect the file before changing it:

Check the ADT components in this FileMaker file and show me any missing, changed, or outdated items.

The agent reports the proposed changes. If you approve them, ask it to reconcile the file with the installed ADT version. Reconciliation can replace customized ADT-owned components, so preserve intentional changes outside the ADT folders first.

Production files

Installing or reconciling components changes the FileMaker file. Make a backup and use the same review process you use for other production schema changes. Existing FileMaker objects outside the ADT folders are not part of the component operation.

The exact object inventory and naming contract lives in ADT components in a file.