Mode Behavior Matrix

Choose mode by intent first, then apply the mode-specific safety flow.

Mode	Best for	Key controls	Safety behavior
ASK	Explanation, troubleshooting, planning	Debug toggle, Web Search, plan actions	Read-oriented guidance; Debug can generate a read-only Coding Plan
CODE	Script generation/refactor	Preflight, Preview/Copy/Apply links	Metadata and scope checks before generation; Apply only when Genie has an apply-safe result
LAYOUT	FileMaker layout object generation and selected-object revisions	Layout Preflight, copied-object injection, Preview XML, Copy for Paste	Copy-only layout XML; paste manually in FileMaker Layout mode
QUERY	SQL and result visualization	Format and chart selectors	Read-oriented output and exports
DATA	Confirmed data/schema execution	Confirmation links	Entry warning + explicit confirmation + migration-plan stepwise controls for multi-step requests
Local MCP -> Workbench	IDE-agent CODE/DATA handoff	`genie_get_capabilities`, metadata tools, purpose-built staging tools, Workbench Run/Copy/Remove	MCP stages only; running happens inside Genie and reuses CODE or DATA safety
Calculation Quick AI	One calculation draft in Specify Calculation	Native calculation overlay	Inserts draft expression text only after calculation draft validation and dialog drift checks

CODE mode safety

CODE starts by checking intent, scope, and metadata. If required field, table, layout, script, custom-function, MBS, or BaseElements references are missing, Genie can pause and ask you to refresh metadata, select the right items, import functions, enable plugin dictionaries, or provide the exact name.

When Genie produces code that is reviewable but not apply-safe, Apply Code remains unavailable. Preview Code and Copy may still be available so you can inspect or recover the draft manually.

When CODE arrives from Local MCP Workbench, the same rules apply. Workbench CODE items should be one new FileMaker script staged with genie_stage_new_script, or one edit to a script already attached/selected in Genie staged with genie_stage_edit_script.

LAYOUT mode safety

LAYOUT mode creates FileMaker layout object XML that you copy and paste manually in FileMaker Layout mode. It can create new object groups or revise copied layout objects, but it does not apply changes automatically, create schema, create scripts, change records, or edit layout parts and themes.

For current-layout edits, copy selected FileMaker layout objects first, then use the LAYOUT copied-object button in the composer. Genie uses those copied objects as the edit set for the next LAYOUT prompt and shows a clearable LAYOUT context chip.

MCP routing

Local MCP clients should choose a route by intent:

use read-only metadata resources and tools to inspect context
use genie_query for read-only SELECT preview or run work outside Workbench
use genie_stage_new_script for one new FileMaker script
use genie_stage_edit_script for one edit to an attached or selected script
use genie_stage_data for one reviewed DATA request

ASK/planning is not a Workbench stage. Keep planning in the IDE or use normal Genie chat.

Calculation Quick AI safety

Calculation Quick AI is outside ASK/CODE/QUERY/DATA mode switching. It uses the Coding provider with a tiny calculation payload and returns a structured calculation draft. Genie rejects script edits, FileMaker script XML, patch-shaped output, and unknown response keys, then inserts only draft calculation text into the open calculation editor when the dialog snapshot still matches.

Mode access and licensing

The same activation state applies across ASK, CODE, QUERY, and DATA.
Genie can be active, trialing, in grace, expired, invalid, or otherwise locked.
Manage activation and deactivation from Manage Activation.
When Genie is locked, the UI surface is disabled until activation or license recovery succeeds.

DATA mode safety

Switching to DATA shows a high-impact warning and requires explicit confirmation before execution. Multi-step migration requests use stepwise cards with Execute Step-by-Step, Execute All, and recovery controls. Standard staged execution uses CONFIRM CHANGE, while full-table or destructive execution requires CONFIRM FULL TABLE CHANGE. CREATE INDEX is blocked in DATA mode and should be handled in FileMaker schema settings instead.

For full migration-plan behavior and guardrails, see DATA Mode.

Learn each mode

Provider note

Provider behavior can differ by account, model family, and endpoint compatibility. For provider strategy and configuration, see AI Providers.