The Agency of Orchestrated Agentic Coding
- Darrin Southern
- Apr 24
- 5 min read
Updated: 5 days ago
We're living in exciting times for coding . . .
For long-time FileMaker Developers - not un-like yours truly - this rapid evolution - I really should say revolution - presents both a challenge and opportunity.
Every new dawn presents a deluge of features and functions from Anthropic and alike, along with Claris FileMaker centric solutions appearing from our esteemed community legends.
The Agency of FM Vibe Coding
The word 'agency' comes from the Latin 'agere' (to do, to act). Now is the time to act and start your journey of Developing and Coding with AI, if you have not already.
I'm in awe of how quickly I've been able to set up Claude Code to build a Web App front-end talking to the FileMaker Database backend via the Data API.
I'll have the option of publishing this Web App via the Web Viewer within the current FileMaker Pro environment. The FileMaker Platform provides a security layer that removes one of the main issues plaguing Agentic Development currently.
And not to mention the new plugins and add-ons for FileMaker Agentic Coding such as Matt's Agentic FileMaker plug-in - I've had a chance to beta test with Matt, and the experience completely changes how we will be 'coding in the 80's'.
Note: It's been pointed out that not everyone will know the reference to this song by an Aussie Band from 1980. In this context - I'm referencing the fact that some of the FileMaker tools we've been coding with have not changed since the '80s . . .
I've also begun to play with proofkit filemaker plugin and its platform of local services to tie the Agentic Coding environment to the node and typegen coding options for not only creation of Web Apps, also the ability to generate and paste schema elements from a prompt. Bonus: Check out Todd's Proofkit Initial Setup video.
Context Engineer
The role of Context Engineer has evolved in the last few months, and will continue to.
If you haven't read my earlier post on the subject, the Context Engineer bridges business needs and technical execution – knowing the solution inside and out, and ensuring the right context is applied at every layer.
The next step in that evolution is the 'Orchestrator' - the Developer who steps back from hand-crafting every element of code and interface, and instead directs the process: knowing what to ask, what to review, and when to ship.
If anyone has attempted the process of mentoring a new Developer - with the need to explain every feature and function of a project, including the review and quality assurance - it's a similar sensation. All at an accelerated rate that can become intoxicating.
The methodology doesn't change. The velocity does.
Development Methodology with AI
One of the key factors in the adoption and continued growth will be the methodologies applied to Development 'aided' with AI.
Sure, Anthropic have claimed that Claude is now writing itself, with human oversight. This reminds me of Consultancy firms that solely rely on the 'interns' to write the code, with minimal intervention from the Senior Developers.
I see a clear entry point for AI aided code where the guardrails only allow AI to recommend the next code change, to be applied to the Development system, with very clear QA Testing processes before being applied to Live - which is how we are all coding now, aren't we ?
FileMaker Development with AI
I've listed a number of upcoming options that are 'in the works' for FileMaker Developers to adopt Vibe Coding - Orchestrated Agentic Coding - as a glimpse of our collective current future, which also has the benefit of breathing new life to the Claris Platform, before we are exposed to what Claris has in the works . . .
It's worth noting some still require copy and paste between the FileMaker Platform and the Agentic Coding Environment, others have bridged this gap. That said, this copy and paste does create a form of guardrails . . .
Matt is building a platform and plugin to analyse solutions, generate/update scripts, design layouts, build schema & more — all through AI that understands your live FileMaker environment. (em dashes optional)
Bruno has created his own plugin to generate scripts, debug logic, ask questions, run structured queries against your file, and work with schema using context grounded in your live solution.
Dimitris has released AI2FM - a plugin and service that connects AI models with FileMaker via copy and paste. The plugin supports natural language prompts to generate scripts and automate tasks.
Alberto has released a Mac app - Windows to come - generate, copy/paste elements - scripts, custom functions, etc for coding via your favourite AI Agent, with usage based on 'credits' purchased.
Join Ernest and Todd in this episode of the Context Podcast, for a short demo of ProofKit MCP and how you can expose AI agents to FileMaker.
Agnes has published FM Dojo, which provides a comprehensive guide and tools for integrating AI into FileMaker workflows, focusing on practical implementation and best practices. New features and functions are regularly added.
Latest Updates and Podcasts
As mentioned, there's something new each day - two sessions worth catching:
Claris AI Talk Podcast
Changes in the world of Value Pricing in the land of AI with Jonathan Stark Bonus: Kudos to Cristos for sharing a Media Summary of the above Podcast
FileMaker Training Videos with Todd, Ernest, and Eric from Proof.sh
What's Next
I'm excited to see what each 'tomorrow' brings to this list, and of course to the tools and features Claris announces to improve the Developer Experience (DX) for our 'Orchestrated Agentic Coding' journey.
And on that note - here's the link to Ryan's recent blog post 'How Claris is building for what comes next.' on the direction of the Claris FileMaker Platform and AI.
Take Away
The role of the FileMaker Developer is shifting — not disappearing. The Orchestrator is the next evolution of the Context Engineer; the one who knows what to ask, what to review, and when to ship.
Here's a few bullet points to consider
Adopt guardrails first - let AI recommend, you decide
QA doesn't change; the pace does - stay sharp
Know your solution inside and out before handing the wheel to AI
Orchestrated Agentic Coding is opt-in, for now - act while it's still a choice
The tools will keep coming. The methodology is yours to define.
We're living in exciting times for coding . . .
Comments