Agentic Coding - Part 3

Your agent can see your data, adjust your table structure, and run your scripts, but the one thing FileMaker developers most want to hand over, writing and improving the script logic itself, is still locked away. The steps you spend hours composing live in a space no external model can simply open, and until you understand how that code leaves FileMaker and returns, every attempt to automate your scripting work runs into the same wall. This video walks every path that script logic currently has between the FileMaker you know and the agent world you are building into.

Watch each route in action, from the moment a copied script lands on the clipboard as XML, to a full export of the solution that gets split into individual files an agent can read by name, to a local companion server that carries modified logic back into the script workspace without you ever touching a paste key. You will see the tradeoffs of each method, what the agent actually receives, how much noise travels with it, and how an in-FileMaker plugin can shrink the entire round trip to a single conversation, complete with switches that decide whether the agent may execute scripts, modify them, or leave data alone.

This video goes into the decisions that make direct script work safe and repeatable, how to keep your instruction file from becoming a dumping ground, which guardrails belong on an agent with direct access to your machine, and how context windows change as you move from single scripts to long-running operations. It also maps what the platform itself is shipping, including the patch file approach for offline files and where direct integration for hosted solutions stands, so you know exactly what you can rely on today and what is coming down the road.

Click the title or link to this article to view the video.

View the full article