Skip to content

Mode Behavior Matrix

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

ModeBest forKey controlsSafety behavior
ASKExplanation, troubleshooting, planningDebug toggle, Web Search, plan actionsRead-oriented guidance; Debug can generate a read-only Coding Plan
AGENTTool-using investigation, script drafting, layout copy artifacts, read-only reportsProvider/model picker, Web Search where supported, MCP tool loopUses Genie-owned MCP tools for evidence; script output promotes to normal CODE Preview/Copy/Apply
CODEScript generation/refactorPreflight, Preview/Copy/Apply linksMetadata and scope checks before generation; Apply only when Genie has an apply-safe result
LAYOUTFileMaker layout object generation and selected-object revisionsLayout Preflight, copied-object injection, Preview XML, Copy for PasteCopy-only layout XML; paste manually in FileMaker Layout mode
QUERYSQL and result visualizationFormat and chart selectorsRead-oriented output and exports
DATAConfirmed data/schema executionConfirmation linksEntry warning + explicit confirmation + migration-plan stepwise controls for multi-step requests
Local MCP -> WorkbenchExternal IDE-agent script/DATA/layout handoffgenie_get_capabilities, genie_scripts, genie_metadata, purpose-built staging tools, Workbench Run/Copy/RemoveMCP normally stages only; running happens inside Genie and reuses Genie safety flows. The beta auto-create setting can immediately run Create Script for trusted local clients and supported script stages.
Calculation Quick AIOne calculation draft in Specify CalculationNative calculation overlayInserts draft expression text only after calculation draft validation and dialog drift checks

AGENT mode lets Genie use its own local MCP tools before answering. It can inspect FileMaker metadata, current/open files, script context, script catalogs, calculation behavior, and read-only query rows.

For script-build or script-edit requests, AGENT gathers evidence, authors public Script Schema, validates when useful, then returns an agent_script_build artifact. Genie promotes that artifact into the same CODE Preview/Copy/Apply card used by CODE mode. AGENT does not get a separate hidden apply path.

If AGENT is unsure about intent, target identity, destructive scope, or whether a draft would be safe, it should ask one concrete clarification instead of fabricating a confident artifact.

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 script work arrives from Local MCP Workbench, the same rules apply. Workbench script items should be one new FileMaker script or one active-script edit staged with genie_scripts using Script Schema JSON.

If Automatically create scripts in FileMaker is enabled in Local MCP settings, supported successful script stages from authenticated local clients can immediately run Genie’s Create Script path. Existing scripts are never replaced.

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.

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_scripts for one new FileMaker script or one edit to the active script
  • use genie_stage_data for one reviewed DATA request
  • use genie_stage_layout for copy-only layout objects

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

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.

  • 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.

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.

DataModeWarning.png

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

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