Installation and coding-agent problems

Installation problems affect the global ADT files or the coding-agent plugin before a project or FileMaker file is involved.

Check the installation

Ask the affected coding agent to inspect its ADT installation:

Copy

Check whether the FileMaker Agentic Development plugin and ADT tools are installed and loaded in this application.

The standard agent plugin is installed automatically into Cursor, the Codex CLI, the ChatGPT desktop app, and VS Code. The installer also installs the Claude plugin when it detects Claude Desktop or the Claude Code CLI.

The plugin is missing

Run the ADT .pkg installer again, then quit and reopen the affected application. A running coding agent does not discover a newly installed plugin until it restarts.

After restarting, repeat the check. If a supported application still cannot find the plugin, ask another working agent to gather the installer logs, or see Run diagnostics and read logs.

An unsupported agent cannot load ADT

ADT can work with another coding agent if that agent supports the Agent Plugin standard or the Claude plugin format. Follow Manual configuration to point the agent at the package installed on your computer.

Do not copy individual skills or MCP settings by hand. Loading the complete plugin keeps its tools, skills, and internal paths together.

The plugin is present but stale

Restart the application first. If it still reports an older ADT version, rerun the installer and restart it again. The installer replaces the global plugin package and refreshes registrations for detected applications.

`filemaker` is not found

The filemaker command is installed separately from the coding-agent plugin. If the agent reports that filemaker is missing, ask it to check the launchers and ADT installation paths. A missing shell path entry does not mean the rest of ADT is absent.