Settings Guide
Use Settings to control app language, theme, activation, permissions, personalization, model routing, advanced options, and Local MCP Bridge.

Layout
Section titled “Layout”Settings uses a left navigation rail with focused pages:
- General: language, theme, activation, and permissions
- Personalization: assistant tone and custom instructions
- Models: provider keys, model routing, reasoning effort, and custom endpoints
- Advanced: clarification budget, plugin function dictionaries, Agent / MCP guidance packs, and privacy-first analytics
- Local MCP: local bridge setup snippets and connection status
The Docs entry in the rail opens this documentation.
General
Section titled “General”General includes product access and local system permissions.
| Setting | Description |
|---|---|
| App Language | Chooses the Settings and UI language when a manual override is needed. |
| Theme | Chooses light or dark UI. |
| Activation | Enter an activation key, buy, activate, deactivate, and read activation status inline. |
| Permissions | Shows Microphone and Accessibility status for the app currently running Genie. |
Permissions
Section titled “Permissions”Permissions are shown where activation lives so recovery is visible before users reach CODE or capture actions.
- Microphone enables dictation in the composer.
- Accessibility lets Genie read FileMaker Script Workspace and apply changes.
- Open Settings takes the user to macOS settings when a permission is missing.
Personalization
Section titled “Personalization”Use Personalization to configure global guidance and active-project guidance from one place. Build 53 replaces the separate Project Rules toolbar modal with this consolidated Settings surface.

Generic scope
Section titled “Generic scope”Generic contains defaults Genie can use across projects:
| Setting | Description |
|---|---|
| Personality | Chooses a friendly, balanced, or pragmatic response style. |
| Custom instructions | Sends style and workflow preferences with model requests. Do not store secrets here. |
| Naming conventions | Defines global naming preferences, such as script naming style or variable casing. |
| Patterns | Captures reusable implementation patterns, contracts, error handling, and preferred techniques. |
| Script template | Provides the default structure Genie should follow for new or substantially revised scripts. |

Project scope
Section titled “Project scope”Project contains configuration for the active FileMaker file:
| Setting | Description |
|---|---|
| Project name | Display name for the active FileMaker solution. |
| Description | Project-specific summary of the solution, users, purpose, and important operating constraints. |
| Project rules | Enabled or disabled guidance rules for this FileMaker file. |
| Naming convention override | Optional project-specific naming guidance. Empty values inherit Generic naming conventions. |
| Pattern override | Optional project-specific implementation patterns. Empty values inherit Generic patterns. |
| Script template override | Optional project-specific script structure. Empty values inherit the Generic script template. |

Project description and Project Rules are project-specific and do not inherit Generic values. Generic values are app preferences, not copied into every project profile.
The effective configuration is included in project_context for standard Genie modes, embedded AGENT, Script Workspace AGENT, and Local MCP. It can influence naming, comments, implementation patterns, and script structure, but it never expands tool access, target scope, Workbench staging, Apply, Stage A/B scope, or mutation authority.
Models
Section titled “Models”Models controls provider credentials and routing for Coding and Logistics.

| Setting | Description |
|---|---|
| OpenAI / Anthropic / Google / xAI keys | Saved credentials for each cloud provider family. |
| Use one model | When on, Coding also handles questions, refinement, and coordination. Turn it off to choose a separate Logistics route. |
| Coding Provider | Provider family for code generation: Custom / Local, OpenAI, Anthropic, xAI / Grok, or Google. |
| Coding Model | Selected model for coding work. |
| Coding Reasoning Effort | Depth vs speed for the coding role. |
| Logistics Provider | Provider family for planning, refinement, QUERY, DATA, and ASK coordination. |
| Logistics Model | Selected model for the logistics route. |
| Logistics Reasoning Effort | Planning/refinement depth for the logistics route. |
| Custom Token | Credential for an OpenAI-compatible local or custom provider. |
| Coding Endpoint | OpenAI-compatible endpoint used when Coding provider is Custom / Local. |
| Logistics Endpoint | OpenAI-compatible endpoint used when Logistics provider is Custom / Local. |
| Test Connection | Checks a configured custom endpoint before saving. |
xAI / Grok
Section titled “xAI / Grok”Choose xAI / Grok when you want a hosted Grok model for Coding, Logistics, or both roles.
- xAI uses its own saved API key in Settings.
- Grok models appear in the normal model dropdown.
- Genie routes xAI traffic through xAI’s OpenAI-compatible cloud API path.
- The custom model id, endpoint, and connection-test fields are only for
Custom / Local; they are not shown for xAI. - Web Search is not wired for xAI in this release.
Advanced
Section titled “Advanced”Advanced contains controls that affect request handling and optional diagnostics.
| Setting | Description |
|---|---|
| Preflight Questions | Shared clarification budget for CODE, QUERY, and DATA. 0 keeps preflight active but prevents follow-up clarification prompts. |
| BaseElements plugin | Allows Genie to use the BaseElements plugin function dictionary when resolving and planning CODE. |
| MBS plugin | Allows Genie to use the MBS plugin function dictionary when resolving and planning CODE. |
| Agent / MCP: Expose Klai hook guidance | Adds Klai / BetterForms hook guidance for Genie AGENT and connected MCP clients. |
| Send Analytics | Allows private operational diagnostics. Prompts, scripts, and database metadata are not included. |
Leave a dictionary off when the plugin is not installed or when you do not want generated code to rely on that plugin. Disabled dictionaries are ignored during function resolution.
Agent / MCP guidance packs
Section titled “Agent / MCP guidance packs”The Agent / MCP subsection exposes optional guidance packs to Genie AGENT and connected Local MCP clients.
Turn on Expose Klai hook guidance when you want Klai / BetterForms hook guidance available through genie_get_guides and genie://guides/klai-* resources. This is a teaching/resource pack only. It does not add hidden FileMaker mutation tools and does not bypass CODE, DATA, Workbench, or Apply review.
Reconnect MCP clients after changing this setting so they refresh their guide index.

Local MCP Bridge
Section titled “Local MCP Bridge”Use Local MCP Bridge when you want external MCP clients on the same machine to consume Genie metadata/context and stage reviewed work into Workbench.

Use Local MCP Bridge for the dedicated guide and troubleshooting entry points.
What you configure
Section titled “What you configure”| Setting | Description |
|---|---|
| Enable Local MCP Bridge | Starts or stops the local bridge. |
| Automatically create scripts in FileMaker | Beta. Lets trusted Local MCP clients immediately run Genie’s Create Script flow for supported successful script stages. Existing scripts are never replaced; edits create a new version. |
| Port | Local port for the MCP server. The host is shown inline as 127.0.0.1. |
| Status | Running, disabled, or startup/error state. |
| Setup guide | Shows Codex Streamable HTTP, Cursor/generic JSON, endpoint URL, or bearer-token setup. |
| Copy snippet | Copies the selected setup snippet with the current local bearer token. |
Leave Automatically create scripts in FileMaker off unless you trust the connected local client and want supported script stages to create scripts immediately through Genie’s existing Create Script path. The bridge is localhost-only, but every authenticated client with the current token can use the beta while it is enabled.
Token behavior
Section titled “Token behavior”- The auth token is generated and stored by Genie.
- The token field is not directly edited in the visible UI.
- Visible previews mask the token when appropriate.
- Copy snippet includes the real current bearer token automatically.
Local MCP resources
Section titled “Local MCP resources”Essential + slim anchors (guide-first model):
genie://schemas/script-schemagenie://schemas/script-cataloggenie://schemas/layout-schemagenie://context/projectgenie://context/scripts- Guides:
genie://guides/*(delta editing, metadata selection, stage contract, relationships, what-not-to-stage) - Session:
genie://session/files,genie://session/open-files-metadata - Slim metadata:
genie://metadata/all,genie://metadata/selected,genie://metadata/relationships,genie://metadata/relationship-graph
Use genie_metadata for table, layout, script, field, and custom-function discovery.
genie://context/project exposes the effective Generic/Project Personalization guidance for connected AGENT and MCP clients. It is guidance only and does not widen mutation authority.
Current MCP tools
Section titled “Current MCP tools”genie_get_capabilitiesgenie_filesgenie_scriptsgenie_metadatagenie_get_guidesgenie_evaluategenie_querygenie_stage_datagenie_stage_layoutgenie_workbench
These tools are intended for external agents and IDE workflows. They do not replace the in-app UI.
Workbench staging normally does not run providers or apply changes during the MCP call. The user reviews staged script, DATA, layout, or XML items in Genie and runs or copies them through the matching safety flow. If the beta Automatically create scripts in FileMaker setting is enabled, supported successful script stages from authenticated local clients can immediately run the reviewed Create Script flow; existing scripts are never replaced. QUERY uses genie_query outside Workbench, and ASK/planning stays in the IDE or normal chat.
Example Codex configuration
Section titled “Example Codex configuration”# Genie uses Streamable HTTP. Do not configure stdio for this bridge.
[mcp_servers.genie_filemaker]
enabled = true
url = "http://127.0.0.1:3845/mcp"
[mcp_servers.genie_filemaker.http_headers]
Authorization = "Bearer <generated-token>"Example Cursor or generic JSON configuration
Section titled “Example Cursor or generic JSON configuration”Copy snippet can also produce a JSON payload shaped like:
{
"mcpServers": {
"genie_filemaker": {
"url": "http://127.0.0.1:3845/mcp",
"headers": {
"Authorization": "Bearer <generated-token>"
}
}
}
}Activation access
Section titled “Activation access”Activation lives in Settings > General.
- Activation state applies across ASK, CODE, QUERY, DATA, Workbench runs, and most capture actions.
- Support remains available for activation recovery.
- Provider credentials do not unlock the product by themselves.
Save behavior
Section titled “Save behavior”- Save applies the current changes.
- Cancel or close discards unsaved changes.