Genie Product Tour
This tour gives you the big picture before you start using Genie day to day.
Genie is the FileMaker-native AI workbench. It lives beside FileMaker Script Workspace, reaches into calculation and metadata workflows, connects to local IDE agents through MCP, and keeps generated work reviewable before it changes your file.
1. Start from the main window
Section titled “1. Start from the main window”The main window has three working areas:
- Header: provider/model status, history, support, and Settings.
- Tool belt: Add Scripts, Add Selection, Clear Context, New Chat, Project Rules, and Metadata Explorer.
- Composer: mode selector, web search, prompt field, file attachment, dictation, send, and stop.
Use the header to check your current model setup. Use the tool belt to control what Genie can see. Use the composer for the actual request.
2. Capture the right FileMaker context
Section titled “2. Capture the right FileMaker context”Start with Add Selection when the current script or selected rows are the target. Use Add Scripts when several open Script Workspace tabs matter together.
When context is active, Genie shows badges above the composer. A live badge represents the current Script Workspace capture. File badges represent text-based reference files you attached for the current chat.
Attached files are useful for examples, notes, logs, XML, JSON, CSV, SQL, or requirements. They help Genie understand the request, but they do not become editable FileMaker targets.
3. Choose the right mode
Section titled “3. Choose the right mode”Pick the mode that matches your intent:
| Mode | Use it for | What to expect |
|---|---|---|
| ASK | Explanation, troubleshooting, and planning. | Read-only answers, Debug analysis, and optional Coding Plans. |
| CODE | Creating or changing scripts. | Preflight, generated script output, Preview, Copy, and Apply when safe. |
| QUERY | Read-only SQL questions and results. | Tables, charts, raw output, CSV export, and chart image actions. |
| DATA | Confirmed data or schema operations. | Warnings, explicit confirmations, and staged execution controls. |
For normal coding work, capture context first, then use CODE.
For calculation formulas, use Calculation Quick AI from FileMaker’s Specify Calculation dialog. It drafts one expression from the current dialog context instead of entering the full chat composer or CODE pipeline.
4. Use dictation when typing is slower
Section titled “4. Use dictation when typing is slower”The mic button records only after you press it.
Press the mic again to stop. Genie transcribes the recording and inserts editable text into the composer.
Dictation does not send automatically. Review the text, adjust it if needed, then send.
5. Reference known steps, functions, and metadata
Section titled “5. Reference known steps, functions, and metadata”Type / to autocomplete known FileMaker steps and functions. If the MBS or BaseElements dictionaries are enabled in Settings, Genie can also suggest those plugin functions.
Type # to reference selected Metadata Explorer items such as tables, fields, layouts, scripts, and custom functions. If a metadata item is missing, refresh or select it in Metadata Explorer before sending.
6. Review CODE output before anything changes
Section titled “6. Review CODE output before anything changes”CODE responses can include structured assistant text, assumption or warning cards, and action buttons.
Use the buttons in order:
- Preview opens the generated script output or apply plan for inspection.
- Copy copies the generated output so you can recover it manually if needed.
- Apply writes back to Script Workspace only when Genie has an apply-safe result.
If Genie can show a useful draft but cannot safely apply it, Apply stays unavailable. Preview and Copy may still be available for review and recovery.
7. Configure providers, local tools, and plugin dictionaries
Section titled “7. Configure providers, local tools, and plugin dictionaries”Open Settings to manage activation, permissions, personalization, provider routing, model choices, reasoning effort, hosted provider keys, Custom / Local endpoints, Local MCP Bridge, and plugin dictionaries.
Enable BaseElements plugin or MBS plugin only when your FileMaker solution uses those plugins and you want Genie to recognize their functions during CODE grounding.
Provider routing supports hosted OpenAI, Anthropic, xAI / Grok, and Google accounts, plus Custom / Local OpenAI-compatible endpoints. xAI / Grok uses its own saved key and Grok model dropdown; Web Search is not wired for xAI in this release.
Local MCP Bridge is for external editors and agents on the same Mac. It exposes metadata/context resources, read-only inspection and query tools, and Workbench staging for supported CODE or DATA handoff. It does not replace Genie’s in-app safety flow.
8. Activation and recovery
Section titled “8. Activation and recovery”Genie activation is separate from provider API keys. A valid provider key does not unlock a locked Genie UI.
If a key is rejected, Genie shows the failure inline so you can correct the key or retry activation.
Start troubleshooting activation first when the UI is locked. Check provider settings only after Genie itself is active or trialing.
9. Day-one workflow
Section titled “9. Day-one workflow”For a normal script change:
- Open the target script in Script Workspace.
- Select the rows you want to change, or leave no multi-row selection to capture the current script.
- Click Add Selection.
- Attach supporting text files if they matter.
- Use CODE and ask for the change.
- Read assumptions and warnings.
- Preview the generated code.
- Apply only when the result matches your intent.
For questions, use ASK. For read-only data questions, use QUERY. For high-impact data or schema work, use DATA and follow the confirmation prompts. For formulas inside Specify Calculation, use Calculation Quick AI and review the inserted draft before accepting the dialog.