Run diagnostics and read logs

Ask your coding agent to run ADT's diagnostics before troubleshooting individual symptoms:

Copy 
Use ADT to check my setup and tell me what, if anything, I need to fix.

The agent checks the parts of ADT required for the task you are trying to complete. It fixes what it can and reports any action that requires you.

Read the result

The diagnostic result uses one of these states:

  • Ready means every required check passed for the selected task and FileMaker file.

  • Degraded means ADT can continue, but the report found a non-blocking problem, such as FileMaker components from an older ADT version.

  • Blocked means a failed check prevents the selected task. Follow the report's remediation and ask the agent to check again.

  • Not diagnosed means a check did not apply to the current project or task. It is not evidence that the unchecked feature works.

Warning  Read the result in context A file name, installed component, or successful partial check does not prove the whole workflow is ready. Use the final state for the task and file you asked the agent to diagnose.

If the project contains several connected files, name the file you want checked. Otherwise, the diagnostic may be unable to select one or may report on a different file.

What the diagnostic checks

The full diagnosis can inspect:

  1. The installed ADT version and required JavaScript tools.

  2. The agent plugin, filemaker CLI, and component bundle.

  3. The project's adt.json, connected files, Web Viewer apps, and Typegen configuration.

  4. Whether the selected FileMaker file is reachable with its saved connection details.

  5. Whether ADT's custom functions, layouts, and scripts are installed and current in that file.

  6. Whether FileMaker Pro's Agent Access is enabled, and a real read-only FileMaker script call when the task requires a FileMaker Pro session.

Some checks apply only to Web Viewer development. A project without a Web Viewer app does not need ADT's FileMaker components, Agent Access, or a JavaScript toolchain.

Let the agent attempt repairs

The diagnostic can record a file that is already open, install missing ADT components when Web Viewer work requires them, and reconnect a file whose grant is missing or was declined.

Try this prompt when the first report is blocked:

Copy 
Fix every ADT setup problem you can, then run the diagnosis again. Tell me only what still requires my action.

You may need to dismiss a FileMaker dialog, answer the grant prompt after a FileMaker Pro restart, enable Agent Access in FileMaker Pro, restart an application after installation, or enable FileMaker sharing for an open file.

Gather a deeper report and logs

Ask the agent to collect the full status, diagnosis, and relevant logs:

Copy 
Gather ADT's full diagnostic report and the logs relevant to this failure. Explain which check failed and where each log came from.

The reports serve different purposes:

  • Status inventories installed versions, files, configured coding agents, and visible FileMaker state. It does not prove that an operation succeeds.

  • Diagnosis performs the live checks required by the current project and task, then returns a ready, degraded, or blocked result.

  • Installer logs record installation and agent-registration work. ADT stores them under ~/Library/Application Support/ADT/MCP/logs/.

See Global installed files for the ADT-owned log directory and other installation paths.

Resolve conflicting results

A status inventory can look complete while a live operation still fails. Trust the live diagnostic for the task you are attempting, then ask the agent to reproduce the failed operation after applying its remediation.

If the agent says the setup is ready but the same operation still fails, ask it to collect:

  • The full diagnostic result for the correct FileMaker file

  • The exact failing operation and error

  • Relevant installer logs

  • ADT, macOS, and FileMaker Pro versions

Continue with Collect information for support if the repeated check and operation disagree.