A recap of an ACF community office-hours session covering critical security updates for WordPress 7.0.3 and ACF/ACF PRO 6.8.7, a preview of upcoming features like an in-admin Settings page and AI-powered Smart Field Suggestions, and a discussion on how developers use AI tools such as Cursor, Claude Code, and Figma Dev Mode with MCP to speed up WordPress workflows. It also covers a workaround for MCP limitations using Local JSON files synced via WP-CLI, and promotes the 2026 ACF Annual Survey.
Table of contents
Session RecordingSession SummaryRecent Releases: WP 7.0.3 & ACF 6.8.7Shape the Future: The 2026 Annual SurveyWhat’s Coming to ACF: Admin Settings & Smart Field SuggestionsOvercoming Agent Limits with Local JSONQuick Comparison: Popular Developer AI ToolsResources & LinksQuestions this post answers
Do I need to update WordPress and ACF right now because of a security issue?
Yes, WordPress Core released version 7.0.3 as a critical security patch that should be deployed across all WordPress sites as soon as possible. On the plugin side, ACF and ACF PRO released version 6.8.7, following 6.8.6, addressing several reported security issues. Disclosures were not severe, but security reporting in the ecosystem has risen sharply, so updating both local and production environments is recommended. daily.dev surfaces security releases like these so WordPress stacks don't fall behind on patches.
How can I update individual ACF fields using AI agents when MCP tools don't support direct field edits yet?
Since direct field updates via MCP are still evolving, you can instruct AI agents like Claude or Cursor to generate or update raw ACF Local JSON files directly in your theme or plugin folder instead of going through the database via intermediate APIs. Once the JSON is updated, run the `wp acf json sync` WP-CLI command to scaffold, modify, and deploy the field structures across environments. developers wiring AI agents into WordPress workflows can track these emerging patterns on daily.dev.
What is the best AI tool for scaffolding a new WordPress plugin from scratch versus editing an existing codebase?
Claude Code and Opus excel at scaffolding brand-new plugins from a blank workspace and handling complex logic or scripting, thanks to their long context windows and strong documentation comprehension. Cursor, on the other hand, is better suited for codebase navigation, CSS tweaking, and PR reviews within an existing project, with built-in sub-agent orchestration on its $60 plan. comparing AI coding tools for a specific workflow is easier with real usage notes on daily.dev.