Video summary

Community Live 53: Agentic development in practice

Main summary

Key takeaways

Technology

Summary

Ernest Koe of Proof demonstrated agentic development for FileMaker by refactoring FM Spark, a legacy, multi-file solution dating to around 2011. FM Spark handles contact-based email and mail-merge workflows. The demo showed an AI coding agent analyzing the existing solution, changing scripts and layouts, and replacing an obsolete email integration.

ADT: How the Toolkit Works

The Agent Development Toolkit (ADT) is not a traditional FileMaker plug-in. It combines agent skills and tools with a local command-line interface and a configured MCP connection. ADT installs FileMaker components, such as scripts and layouts, that let an agent work with a solution.

The demo described two broad kinds of operations:

  • Schema changes, including layouts, tables, relationships, and fields, are handled through a local FileMaker CLI.
  • Data and script work uses a separate FileMaker agent-access path.

ADT is intended to work with different coding-agent environments, not just Claude. Examples mentioned included Cursor, VS Code, and Codex. Files do not have to be stored in the project folder or exclusively on the developer’s computer, but they need to be accessible and open for the full range of operations.

Live Demo: Analyzing and Refactoring FM Spark

Koe began by asking the agent to inspect the solution and identify its structure, workflows, and potential problems. The agent examined the files, scripts, layouts, and data model, then produced a detailed structural report and a proposed refactoring plan. It also used background agents to investigate areas such as the data model, screens, and workflows.

The refactoring goals included:

  • Removing an obsolete email plug-in dependency.
  • Replacing it with transactional email through Resend’s API.
  • Addressing a broken utility file for which the password had been lost.
  • Modernizing the interface and its older themes and controls.

In the demonstrated result, the agent added an email settings screen, updated email-related scripts across the solution, and enabled test emails. Koe sent a test message and confirmed that it arrived.

Native Layout Editing and Iterative Design

The agent also updated a FileMaker layout directly, creating a modernized user-settings screen with native FileMaker objects and a minimalist theme. Koe started with a broad request, reviewed the result, and then asked for refinements such as an eight-point spacing grid and better buttons. He used screenshots to help identify alignment issues and make further corrections.

The example illustrated an iterative workflow: start with a goal, inspect what the agent produces, refine the result, and—once a useful approach is established—turn it into a more reusable prompt. ADT can also apply configured development standards, including company-specific standards.

The agent made changes to the existing solution rather than creating a separate application. As with development by another person, simultaneous edits can cause conflicts; FileMaker reports when a resource, such as a layout, is already being edited.

Working Practices and Considerations

Koe’s preferred workflow is to investigate first, develop a plan, and then have the agent carry it out. He also noted that developers can work more conversationally and refine their approach as they learn what is possible. He recommended using clones and test data, not production or sensitive data.

The speakers emphasized that privacy, compliance, and intellectual-property concerns require organization-specific decisions. One possible approach for teams that need more control over model use is to use locally hosted or otherwise privately controlled models. They also noted that agent usage has costs: Koe estimated roughly $4–5 in API token costs for the deep analysis shown, separate from subscription pricing, and cautioned that usage-based plans need to be budgeted.

For developers considering older conversions, the session said ADT does not directly migrate a FileMaker 6 solution. The suggested route is to convert it to FMP12 first and then proceed with migration.

Availability and Preparation

At the time of the session, ADT was in limited testing with a closed group, and its beta was available only for Mac. The speakers said public release depended on FileMaker 26.1 and making installation and operation work on both Mac and Windows. They offered no firm date, describing the outlook as weeks to months rather than quarters to years.

To prepare, Koe recommended trying ProofKit at proof.sh or other agent-development tools to gain experience with agent workflows. Rosemary Teeji also recommended moving to FileMaker 2026 and planning deployments of FileMaker 26 clients and servers.

Demonstrations and Guidance Shown

  1. Checking ADT installation and project configuration.
  2. Analyzing a legacy FileMaker solution and generating a structural report.
  3. Planning a refactor before executing it.
  4. Replacing plug-in-based email sending with a Resend transactional-email API.
  5. Creating and refining native FileMaker layouts.
  6. Using screenshots, test data, and iterative prompts to review agent output.

Main speakers: Ernest Koe, CEO of Proof, presented the demonstrations; Rosemary Teeji, Claris Community Manager, hosted the session and handled audience questions.

Rate this summary

Your feedback will help improve summaries.

Improve this summary

Reprocess with a stronger model when the summary feels incomplete or inaccurate.

Pro

Translate summary in another language

Pro

Ask questions to this video

Chat for follow-up questions, clarifications, and source-backed answers.

Coming soon

Share this summary

Original video