FM Dojo — User Guide

Everything you need to know about FM Dojo's tools and features.

1. Getting Started

FM Dojo is an AI-powered development assistant built specifically for FileMaker developers. It combines a FileMaker-specialized AI chat, a multi-language code editor, and a visual diagram tool — all in one place.

Quick start

  • Create an account or sign in with Google.
  • Choose a subscription plan on the Pricing page — your tokens are loaded instantly.
  • Open Chat, Code Editor, or Diagram from the top navigation.

No installation required. FM Dojo runs entirely in your browser and works on desktop, tablet, and mobile.

2. AI Chat

The AI Chat is a FileMaker-specialized assistant that understands scripts, calculations, ExecuteSQL, relationships, and FileMaker best practices — far more accurately than general-purpose AI tools.

Conversations

  • Start a new conversation from the sidebar or the New Chat button.
  • Your full chat history is saved and searchable in the sidebar panel.
  • Click any previous conversation to continue where you left off.
  • Edit and resend your last message if you want to rephrase a question.

File uploads

Attach files directly to your message using the paperclip icon. Supported formats:

  • Text files — up to 2 MB (.txt, .sql, .json, .xml, .js, .css, .html, .csv, .log)
  • PDF files — up to 10 MB (text is extracted automatically)
  • Up to 10 files per message.
  • UTF-16 encoded files are auto-detected and converted.

Images

Attach or paste images directly into the chat — the AI can see and reason about screenshots, diagrams, and mockups. Supported formats: PNG, JPG, GIF, and WebP. Paste from the clipboard with Cmd+V (Mac) or Ctrl+V (Windows) without needing to save the file first.

FileMaker code in responses

The AI automatically detects FileMaker code in its responses and applies syntax highlighting — script steps, variables, field references, and functions are all color-coded. Every code block has a one-click copy button.

Sensitive data detection

Before sending, FM Dojo scans your message for common sensitive patterns — passwords, API keys, credit card numbers, private keys, and more. If something is detected, you'll be prompted to review and edit before the message is sent. You can also choose to send anyway if the flag is a false positive.

Context awareness

The AI knows about FM Dojo's built-in tools. When relevant, it will suggest using the Code Editor to test a calculation or the Diagram tool to visualize relationships.

Edit in Code Editor

When the AI's response contains code, an Edit in Code Editor button appears at the bottom of the conversation. Click it to send all code blocks from the chat directly to the Code Editor — the last code block's language is detected automatically.

Calculation accuracy

FM Dojo maintains a verified knowledge base of FileMaker calculation function behavior that goes beyond the official documentation. When you ask about edge cases — negative arguments, zero, decimals, empty inputs, overflow — the AI answers from one of three sources, which it cites explicitly:

  • Verified test results — behavior confirmed by running the exact expression against a real FileMaker instance. The AI states the FM version the test was run on.
  • Documented rules — argument constraints recorded in the structured knowledge base but not yet independently tested. Cited as “documented behavior, not yet verified by testing.”
  • Not confirmed — if neither applies, the AI says so and advises you to test directly rather than guessing.

This covers 24 functions and 190 edge cases including calendar overflow (e.g. Date(13; 1; 2024)), divide-by-zero in Mod, negative Sqrt, zero-argument Log, and decimal truncation vs. rounding behavior per function.

Tip: Use the sidebar toggle (panel icon in the header) to hide the chat history and get more screen space for your conversation.

3. Code Editor

A full-featured code editor with syntax highlighting, validation, autocomplete, and snippet management — purpose-built for FileMaker development.

Supported languages

  • FM Calc — FileMaker calculations with function autocomplete
  • FM Script — FileMaker script steps with autocomplete
  • FM Schema — define tables, fields, and relationships in a readable plain-text format
  • SQL — with syntax validation, formatting, and an in-browser SQL Fiddle
  • JavaScript — with linting, formatting, and a Web Viewer Fiddle
  • JSON — with validation and pretty-print
  • YAML — with validation and formatting (supports multi-document files separated by ---)
  • XML — with validation and formatting

FM Schema

FM Schema is a plain-English format for defining your FileMaker database structure. Write table and field definitions in a simple, readable syntax — then use Review & Export to inspect your schema, adjust field types, and copy FileMaker XML ready to paste into FileMaker Pro.

Getting started quickly:

  • Create a new snippet and choose FM Schema as the language.
  • Open Code Chat and describe your data model — e.g. "Design a schema for a bicycle shop managing inventory, sales, repairs, and customers." The AI generates the full FM Schema code for you.
  • Click Review & Export in the toolbar to see your tables and fields rendered as a structured list, adjust types and settings, and copy FileMaker XML.

In Review & Export, use Export as SQL to generate CREATE TABLE statements from your FM Schema. Choose a dialect — MySQL, PostgreSQL, or SQLite — and get a complete SQL script ready to use in another tool or the SQL Fiddle.

Tip: Ask something like: "Design a schema for a bicycle shop managing inventory, sales, repairs, and customers." The AI will generate FM Schema code with tables, fields, and relationships.

SQL Fiddle

The SQL Fiddle lets you run SQL queries entirely in-browser against a real SQLite database — perfect for prototyping and testing ExecuteSQL() logic before using it in FileMaker.

Getting started:

  • Open (or create) a SQL snippet, then click the flask icon (⚗) in the toolbar.
  • The editor splits into three panels: Schema Setup (top), Query (middle), and Results (bottom). Drag the dividers to resize them.
  • In Schema Setup, write your CREATE TABLE and INSERT INTO statements to build sample data.
  • In Query, write a SELECT statement.
  • Click Run — results appear in the bottom panel immediately.

Tips:

  • Use Code Chat → Schema to describe your tables in plain English and have the AI generate the CREATE TABLE statements for you. Or click Build Table and type something like "orders with line items, customers, and products."
  • If you use FM-style ExecuteSQL syntax — where function arguments are separated by semicolons instead of commas — FM Dojo automatically converts them when you click Run, so you can test real FM calculations without rewriting them.
  • Use → Schema and → Query insert buttons in Code Chat to push AI-generated SQL directly into the right panel.

JavaScript Fiddle

When the language is set to JavaScript, click the flask icon to open the JS Fiddle — a live preview environment for prototyping FileMaker Web Viewer content. Choose from five starter templates including a line chart, pie chart, calendar, Gantt chart, and progress bars. The preview updates as you type. Use Copy as FM Web Viewer to get a FileMaker-ready Set Web Viewer calculation.

Click Colors in the JS Fiddle toolbar to open a 100-swatch color palette. Click any swatch to insert its hex value directly into whichever editor panel (HTML, CSS, or JS) you were last typing in.

Split view & diff

Click the split view icon (two columns) in the toolbar to open two editors side by side. Load a different snippet in the right panel to compare them. Toggle Show diff highlighting to highlight lines that differ between the two — added lines appear in green, removed lines in red.

Validation

Click Validate to check your code for syntax errors. Available for SQL, JavaScript, JSON, YAML, and XML. The editor highlights the exact error line and shows a detailed message with line and column numbers. Valid code can also be auto-formatted.

For FileMaker languages, use Code Chat (see below) for AI-powered code review and validation.

Snippets

Creating a snippet:

  • If no snippet is open, the editor shows a grid of language cards. Click one (e.g. FM Calc, SQL, JavaScript).
  • Type a name for the snippet and press Enter or click Create.
  • Start typing — the snippet auto-saves every 3 seconds. A "Saved" timestamp appears in the toolbar.
  • To create another snippet when you already have one open, click the + New button at the top of the sidebar panel.

Managing snippets:

  • Hover a snippet in the sidebar to reveal Duplicate, Rename, and Delete buttons.
  • Click the pencil to rename inline — press Enter to confirm or Escape to cancel.
  • The language is locked after creation to keep your library organized.
  • Use the search box at the top of the sidebar to find snippets by name.
  • FM Calc and FM Script snippets support tags for categorization (set in the toolbar).

Folders:

  • Click the folder+ icon at the top of the sidebar to create a new folder.
  • Assign a snippet to a folder using the folder selector in the toolbar (the folder icon next to the snippet name).
  • Folders collapse and expand — click the folder name to toggle. Rename or delete folders with the icons that appear on hover.

Clip Manager

Organize snippets into folders and share them publicly — all from the Code Editor sidebar. Use the folder button to create folders, then assign any snippet to a folder using the folder selector on each snippet row. To share a snippet, click the share icon next to it: a public link is generated instantly and copied to your clipboard.

Each clip has a type that determines how it's shared and pasted into FileMaker. Available types:

  • Script step(s)
  • Custom function
  • Plain text
  • Layout object
  • Table(s)
  • Field(s)

Anyone with the link can view the code with full syntax highlighting and copy it. For FileMaker types, the shared page includes a Copy as FileMaker XML button — viewers can paste it directly into FileMaker Pro using the correct pasteboard format. Logged-in FM Dojo users can also click Save to my library to add a copy to their own snippets.

Editor themes

Choose from six themes: FM Dojo (light/dark auto), One Dark Pro, Dracula, GitHub Dark, Nord, and Solarized Dark.

Other features

  • Copy — one-click copy to clipboard
  • Download — save your code as a file
  • Send to Chat — send your current code to the main AI Chat with full context, so you can ask questions without copy-pasting
  • Line numbers, bracket matching, code folding, find & replace
  • Auto-save with last-saved timestamp

Code Chat

Code Chat is a companion AI panel built into the code editor — click Code Chat in the toolbar to open it alongside your code. Your current code is automatically included as context with every message. Use it to validate logic, ask "what does this do?", get suggestions, or — when the language is FM Schema — ask the AI to design a database from a plain-English description.

Tip: The info button next to the language selector shows all features available for the selected language — hover to see them.

4. XML Tools

FM Dojo includes two XML tools for working with FileMaker clipboard data.

XML Export
Generate FileMaker XML from the code editor and paste it directly into FileMaker Pro. Supported types: scripts, calculations, tables, fields, and table occurrences. Relationships cannot be pasted via clipboard yet — they must be created manually in FileMaker for now.
Get XML
Copy FileMaker XML from the clipboard (scripts, custom functions, schema) and paste it into the code editor. FM Dojo converts it to readable plain text.

FM Clipboard Helper

The FM Clipboard Helper is a FileMaker file with two scripts that let you move elements — scripts, fields, layout objects, and more — between FileMaker and FMDojo in both directions. It requires the BaseElements plugin to be installed and enabled in the file.

Copy from FileMaker → FMDojo
Use this to bring existing FileMaker content into FMDojo for editing or documentation.
  1. In FileMaker, select the objects you want to export (script steps, fields, layout objects, tables, custom functions, or value lists) and copy them with ⌘C (Mac) or Ctrl+C (Windows).
  2. Without clicking anywhere else, run the Copy from FM script in the helper file.
  3. The clipboard now contains plain XML. Switch to FMDojo and paste it into the code editor.
Paste to FileMaker ← FMDojo
Use this to bring FMDojo-generated XML back into FileMaker.
  1. In FMDojo, click Copy as FileMaker XML on the content you want to import.
  2. Switch to the helper file and run the Paste to FM script. It reads the XML, detects the correct FileMaker clipboard type automatically, and formats the clipboard so FileMaker can accept it.
  3. Switch to FileMaker (Script Workspace, field definitions, layout, etc.) and paste with ⌘V / Ctrl+V.
Tip: The helper detects the content type automatically — script steps, complete scripts, fields, tables, layout objects, custom functions, and value lists are all supported. You don't need to tell it what you're pasting.

macOS Sequoia and earlier

XML paste works natively — copy from FM Dojo and paste directly into FileMaker Pro's Script Workspace without any additional tools.

macOS Tahoe / FileMaker 21+

FileMaker 21 on macOS Tahoe no longer accepts plain-text XML paste. The clipboard must be formatted with the correct FileMaker pasteboard type before pasting. Two helpers are available from the info button in the editor toolbar:

  • FM Clipboard Helper.fmp12 — a FileMaker file with a one-click button. Copy from FMDojo, click the button, then paste. Requires the BaseElements plugin to be installed and enabled.
  • AppleScript helper — a standalone two-way macOS script. Works in both directions — FMDojo → FileMaker and FileMaker → FMDojo. No FileMaker file or plugins needed. One-time setup required (see below).

AppleScript helper — one-time setup

  1. Download FMDojoClipboard.applescript from the info button in the editor toolbar.
  2. Open it in Script Editor (search for Script Editor in Spotlight, or find it in Applications → Utilities).
  3. In Script Editor, go to File → Export, set File Format to Application, and save it somewhere easy to find (e.g. your Desktop or Applications folder).
  4. The first time you run it, macOS may show a security warning — click Open to allow it.

The script is fully two-way and auto-detects direction — no mode to choose. To paste into FileMaker: copy XML from FMDojo, then run the app. To copy from FileMaker: copy objects in FileMaker (Cmd+C), then run the app. A macOS notification confirms what was detected and which direction ran.

Windows users

Windows users should use the FM Clipboard Helper.fmp12 file (same as macOS Tahoe). It requires the BaseElements Plugin — download it using the BaseElements button in the editor toolbar, then open the helper file and follow the same workflow.

5. Diagram Tool

A visual relationship diagram builder for mapping out your FileMaker database structure.

Building diagrams

  • Add Table — create table occurrences with custom fields
  • Draw relationships — drag from one table to another to create connections
  • Edit relationships — define field mappings and operators (=, ≠, <, >, ≤, ≥)
  • Sticky notes — add annotations anywhere on the canvas
  • Color coding — assign colors to tables and notes for visual organization
  • Drag to reorder, resize, lock/unlock position

Diagram Chat

Click the Diagram Chat button to open an AI chat panel alongside your diagram. Describe what you want to build in plain English and the AI generates or refines a complete Anchor-Buoy relationship graph — table occurrences, fields, and relationships included. Continue the conversation to add tables, adjust relationships, or restructure your design.

Set a naming convention in the chat panel so the AI follows your client's conventions — for example, three-letter table prefixes like INV_, SAL_, REP_.

Tip: Try something like: "I have a bicycle shop. I need an app to manage inventory, sales, repairs, parts, and customers."

Export & save

  • Export to PDF — download your diagram as a PDF document
  • Save — diagrams are saved to your account and can be loaded later
  • Share — generate a public link to share your diagram (see Sharing below)

Layout Designer

A visual drag-and-configure tool for designing FileMaker layouts. Build layouts by placing objects, setting styles, and exporting FileMaker XML that you can paste directly into FileMaker Pro using the FM Clipboard Helper.

Object types

The toolbar gives you every layout object FileMaker supports:

  • Buttons — Button, Button Bar, Tab Control, Slide Control, Popover
  • Fields — Edit Box, Text Area, Checkbox Set, Radio Set, Drop Down, Pop Up, Container
  • Text & Layout — Text Label, Portal, Web Viewer
  • Shapes — Card, Rectangle, Rounded Rectangle, Oval, Line

Click an object type to add it to the canvas. Each object has its own property panel for fill, border, typography, radius, padding, and label.

Alignment & sizing

Select multiple objects to enable alignment tools — align left, center, right, top, middle, or bottom edges. Objects snap to each other while dragging. Use the property panel to set exact pixel dimensions and position.

Figma theme import

Paste the CSS variables from a Figma component export into the theme importer to automatically populate your color palette. This maps your design system's token values (fill colors, text colors, border colors) onto the Layout Designer's object styles — keeping your FileMaker layout consistent with your Figma designs.

Connect your Figma account from the Connections page to access your Figma files directly.

Generating XML for FileMaker

Click Copy XML to generate FileMaker layout XML and copy it to your clipboard. Then use the FM Clipboard Helper to paste the objects into FileMaker Pro. The XML respects the selected theme and object properties. You can also Save your layout to your account and load it again in a future session.

Tip: Start with a Figma import to automatically set your brand colors, then add and style your objects — the XML export will match your design system.

Snapshots

Snapshots let you import your FileMaker database structure from a “Save a Copy As XML” export file — no live server connection needed. Once imported, the Snapshot becomes the active schema for AI context in Chat and Code Editor, and can be loaded directly into the Diagram.

How to export from FileMaker

  • Open your database in FileMaker Pro.
  • Go to File › Save a Copy As XML…
  • Check “Include details for analysis tools” — this is required to include field and relationship data.
  • Save the .xml file and upload it on the Snapshots page.
Tip: The XML export captures tables, fields, table occurrences, relationships, layouts, scripts, and value lists — the full schema.

Large files

There is no file size limit on Snapshots uploads. Very large XML files (120 MB+) are split into 5.5 MB chunks automatically and reassembled on the server — you don't need to do anything special.

  • A progress bar shows how many parts have been sent and what percentage is complete.
  • Files over 35 MB show an advisory that server-side parsing may take up to a minute after all chunks are received.
  • If your XML is too large to export in one go, FileMaker lets you export the XML in sections — use Save a Copy As XML multiple times, then use the multi-file combine feature below.

Multi-file upload and combine

Drop multiple .xml files at once on the Snapshots upload zone. Each file uploads with its own progress bar. When all files finish:

  • Click Combine all into one snapshot to merge them into a single snapshot. Tables, table occurrences, relationships, layouts, scripts, and value lists are deduplicated by name across all files.
  • Click Keep as separate snapshots to save each file as its own independent snapshot entry.
Tip: The combined snapshot's filename shows the first file name plus a count of the others (e.g. KLS.fmp12 +2 more).

Push from FileMaker Server

Instead of exporting and uploading manually, you can push snapshots automatically from a running FileMaker Server. Click Push from FM Server on the Snapshots page to get a ready-to-paste FileMaker script and your personal API key.

  • Generate an API key from the dialog — it is automatically embedded in the script.
  • Copy the script (as plain text or directly as FM XML to paste into Script Workspace) and import it into your FileMaker database.
  • Run the script manually to push on demand, or schedule it in FMS Admin Console → Schedules → Script Schedule to push automatically on a set interval.
  • Each push creates a new version, auto-labeled with the filename and timestamp, and immediately sets it as the active schema.
  • If GitHub integration is connected, each push also commits the snapshot automatically.
Tip: Requires the BaseElements plugin installed on FileMaker Server (server-side, not just desktop). Keep your API key secret — anyone with it can push snapshots to your account.

Active schema

When a Snapshot is active, it feeds your real field names, layout names, and script names into the AI as context — in Chat, Code Chat, and Diagram Chat. The AI will use your actual table and field names instead of inventing generic ones. You can switch between a live database connection and a Snapshot at any time; activating one deactivates the other.

Loading into the Diagram

Each Snapshot can be loaded directly into the Diagram tool. In the Snapshot detail view (click View), the diagram data is pre-populated from the XML export — table occurrences, fields, and relationships are all included.

GitHub integration

Connect a GitHub account on the Connections page to automatically commit each Snapshot to your repo when it's uploaded. The commit stores one JSON file per table and one per script, so GitHub's native diff shows exactly what changed between versions.

  • Only files that actually changed are uploaded — unchanged files are skipped to keep diffs clean.
  • You can also push any version manually using the GitHub button on each version row, and customize the commit message before pushing.
  • If a version was imported before you connected GitHub, use the manual push button to commit it retroactively.
Tip: Set up GitHub integration on the Connections page — you'll need a Personal Access Token with repo scope.

Schema Analyzer

Click Analyze on any version row to open the Schema Analyzer — a live best-practice audit of your FileMaker schema. It scores your database against FileMaker-specific standards and flags issues with actionable details.

  • Health score — overall percentage of checks that pass, shown in the header.
  • Best Practices checklist — checks for primary keys (serial auto-enter), audit trail fields, anchor table occurrences (anchor-buoy pattern), orphaned TOs, cartesian joins, error capture coverage, empty scripts, oversized scripts (over 100 steps), and naming convention consistency. Click any failing check to expand it and see the full list of affected tables or scripts.
  • Naming Conventions table — shows the dominant casing style (PascalCase, camelCase, SCREAMING_SNAKE, etc.) for tables, fields, scripts, and TOs, flagging categories that are inconsistent.
  • Table Health Matrix — a row per base table showing primary key ✓/✗, audit field presence, anchor TO presence, field count, TO count, and layout count.
  • Script stats — step distribution histogram plus totals for loops, sub-script calls, and error capture coverage.
  • Share — click Share in the analyzer header to generate a public read-only link. Anyone with the link can view the full analysis — no login required.

Versioning

Each upload of the same database creates a new version. Give each version a name (like 1.0 or pre-migration) to identify it at a glance — this label replaces the auto-increment number as the primary identifier. Only one version per database can be active at a time.

  • Click any version name to rename it inline.
  • Click to set a version as the active AI schema context.
  • Click ↕ Diff to compare two consecutive versions — added and removed tables, fields, scripts, layouts, and relationships are shown. Modified scripts (same name, different steps) appear with a pencil icon — click them to open a step-by-step diff showing exactly which script steps were added, removed, or unchanged.
  • Click View to browse the full schema: tables & fields, TOs & relationships, layouts, scripts, and value lists.
Tip: The diff feature is in Beta — use in production at your own risk.

FM Servers & FMS Admin

FM Dojo connects to your live FileMaker Server in two complementary ways. FM Schema (via the Servers page) connects individual databases over the Data API so the AI knows your real table names, field names, layout names, and script names — this context flows into AI Chat, Code Chat, and Diagram Chat automatically. FMS Admin (via the FMS Admin page) gives you a centralized console to monitor and manage the server itself: connected clients, open files, schedules, configuration, and live events.

Both features share the same server record. You add a server once with your Admin Console credentials; schema sync and server management are then available from their respective pages.

Tip: FM Server connections are an alternative to Snapshots for teams that can expose their server over HTTPS. Snapshots work offline from an XML export; FM Servers connect directly to a running database.

Adding a server

Servers can be added from either the Servers page or the FMS Admin page in the top navigation. Both use the same form:

  • Server URL — the full HTTPS address of your FileMaker Server (e.g. https://yourserver.com).
  • Admin username & password — your FileMaker Server Admin Console credentials. Used to list databases and access the Admin API. Encrypted at rest (AES-256) and never sent to the browser after saving.
  • Label (optional) — a friendly name like "Acme Corp Production" to identify the server in your list.

Click Save. FM Dojo verifies the Admin API connection and stores the server.

PKI client-certificate authentication

If your FileMaker Server requires mutual TLS (client certificate authentication), expand Advanced: PKI Authentication when adding a server. Paste in your client certificate (PEM format) and private key. FM Dojo will present the certificate on every Admin API request to that server. This is required for servers configured to reject connections without a trusted client certificate.

Connecting databases for AI schema

On the Servers page, click any server to open its detail panel, then click Browse Databases. FM Dojo queries your server for all currently open databases and shows a checklist. Select the databases you want to connect, then enter Data API credentials:

  • Shared credentials — one FileMaker account (username + password) used for all selected databases.
  • Per-database credentials — a separate account for each database in the selection.

Click Connect. Each selected database is saved to your account and appears in the connected databases list below.

Tip: The Data API account needs at minimum read access to layouts and scripts. A dedicated read-only FileMaker account is recommended.

Syncing schema

After connecting a database, click Sync on its row. FM Dojo fetches layout names, script names, and field names (in Table::Field format) from the live database and caches them. The last-synced timestamp updates on the row.

Re-sync whenever your schema changes — after adding fields, layouts, or scripts in FileMaker. Schema is not updated automatically.

Setting an active database

Click the star icon on any database row to activate it. The active database becomes the schema source for the AI — field names appear in autocomplete in the Code Editor, and the AI uses your real schema as context in Chat and Code Editor.

  • Only one database can be active at a time. Activating a new one deactivates the previous one automatically.
  • Activating a live database also deactivates any active Snapshot, and vice versa.
  • Click the star again to deactivate — the AI will revert to general FileMaker knowledge without schema context.

Testing a connection

Click Test on any database row to verify the Data API connection is still working — useful after server restarts, credential changes, or network updates. FM Dojo reports whether the database is reachable and the credentials are valid.

FMS Admin: monitoring & managing your server

Open FMS Admin from the top navigation for a centralized console to monitor and manage all your connected servers. This feature is in Beta — use in production at your own risk.

Each server card shows version, uptime, open file count, and connected client count. Expand any server to access its management tabs:

  • Overview — server version, platform, uptime, WebDirect status, security settings, and general configuration (editable). Includes a live event feed.
  • Files — all open databases with status and session counts. Toggle databases open or closed.
  • Clients — all connected users with IP address, app type, version, and connection time. Send a message to any client or disconnect them with a configurable grace period and message.
  • Schedules — view, enable/disable, and run server-side schedules.
  • Logs — read FileMaker Server log files over SSH or WinRM. See Server Access below for setup instructions.

Live monitoring

When you open a server in FMS Admin, FM Dojo opens a real-time stream to the FMS Admin API. A pulsing Live indicator appears in the server header when the stream is active.

  • Client connections and disconnections appear instantly in the Live Events feed in the Overview tab — no manual refresh needed.
  • Database status changes (e.g. a file going from NORMAL to CLOSED) are also surfaced in the feed.
  • Events are color-coded: green for connections, red for disconnections, blue for database changes.
  • The Clients and Files tabs reflect live data automatically — the manual Load buttons are hidden when the stream is active.

Server alerts

The Alerts tab lets you configure automated monitoring checks that run every 15 minutes. When a threshold is breached or an issue is detected, FM Dojo sends a notification to your Discord or Slack webhook.

  • Disk usage alert — fires when any volume on the server exceeds your configured percentage threshold (e.g. 80%). Requires SSH or WinRM access.
  • Backup failure alert — fires when a FileMaker Server backup schedule's last result is not “OK”. Optionally filter by schedule name. Requires Admin API access.
  • Database status alert — fires when a database is in a non-healthy state (CLOSED, INCONSISTENT, ERROR). Requires Admin API access.

Configure notifications by entering a Discord webhook URL or Slack webhook URL and enabling the corresponding toggle. Use the Send test button to verify your webhook works. The cooldown setting prevents the same alert from firing again within the specified window (default: 60 minutes).

Tip: To get a Discord webhook URL: go to your Discord server settings → Integrations → Webhooks → New Webhook → Copy Webhook URL. For Slack: go to your Slack workspace apps, add Incoming Webhooks, and copy the URL.

Watchdog alerts

The Watchdogs section in the Alerts tab monitors low-level OS events that can silently kill FileMaker Server — out-of-memory kills, disk failures, and the FM Server process going down:

  • FM Server process not running — checks every 15 minutes whether the FM Server daemon is active. On Linux/macOS this uses SSH (pgrep); on Windows it checks the Windows service via WinRM.
  • OOM kills — scans the kernel journal (journalctl -k) for out-of-memory kill events in the last 20 minutes. Linux SSH only. Fires when the OS killed a process due to memory exhaustion — common on servers with FileMaker plus other services competing for RAM.
  • Disk I/O errors — scans the kernel journal for hardware and filesystem errors (I/O errors, EXT4/XFS errors, SCSI errors) in the last 20 minutes. Linux SSH only. Catches silent disk failures that don't necessarily crash FM Server immediately but indicate hardware problems.
Tip: All watchdog alerts share the same cooldown and notification settings as the other alerts on the same server. OOM and disk error watchdogs require an SSH connection to a Linux server — they do not work on Windows or when only WinRM is configured.

Connections

Connect FM Dojo to external services to unlock deeper integrations. Manage all connections from the Connections page.

GitHub

Link a GitHub account and repository to enable automatic snapshot pushes. When you push a FileMaker snapshot from the server, FM Dojo can commit the DDR XML to your GitHub repo — giving you version history for your FileMaker schema. You can connect multiple GitHub accounts, set a default repo and branch, and configure the destination path within the repo.

GitLab

Same as GitHub — connect a GitLab account and project to push snapshots to a GitLab repository. Multiple accounts supported with one set as the default.

Figma

Connect your Figma account using a personal access token. Once connected, you can link a default Figma file URL for use in the Layout Designer's theme importer — importing color tokens from your Figma components directly into the layout designer.

Cloud providers

Register cloud accounts for AWS EC2, Google Cloud, Linode, and Azure to use as targets in the Server Access tool. Once a cloud account is added, FM Dojo can discover running instances and establish SSH sessions through the cloud provider's access mechanisms (AWS SSM, GCP IAP, Linode SSH, etc.) without requiring a public IP or open SSH port.

Tip: Cloud provider connections are used only by Server Access — they are not required for FileMaker Server monitoring or AI chat.

6. Sharing

Share conversations, diagrams, and code snippets as live, read-only web pages — no login required for viewers.

Chat & diagrams

  • Click the Share button in the chat or diagram toolbar.
  • A unique URL is generated instantly.
  • Shared pages include full syntax highlighting and formatting.
  • Great for team reviews, client demos, and forum posts.

Shared chat pages include a call-to-action for viewers to try FM Dojo themselves.

Code snippets (Clip Manager)

  • Click the share icon on any snippet in the Code Editor sidebar.
  • A public link is generated — share it with anyone.
  • The shared clip page shows the code with full syntax highlighting, a copy button, and for FileMaker types, a "Copy as FileMaker XML" button.
  • Viewers can save a copy of the snippet to their own library if they're logged in.
  • Revoke sharing at any time from the snippet options.

Sharing a folder of clips

Share an entire folder of snippets with a single link — useful for distributing script libraries, starter templates, or client-specific code collections.

  • Hover any folder in the Clip Manager sidebar — a share icon appears alongside the rename and delete buttons.
  • Click it to generate a public link. The URL is copied to your clipboard automatically.
  • The shared folder page lists all clips in the folder with full syntax highlighting, copy buttons, and FileMaker XML export where applicable.
  • Viewers can click Save folder to my library to add a copy of the entire folder — with all its clips — to their own account in one click. If a folder with that name already exists in their library, it's saved with a short random suffix (e.g. Demo_A3F9B).
  • The share icon turns teal when a folder is shared. Click it again to copy the link without regenerating it.

8. Server Access

FMS Admin can connect to your FileMaker Server over three different protocols depending on your OS and hosting setup. All credentials are AES-256 encrypted at rest and never sent to the browser.

  • SSH — Linux and macOS servers. Uses a private key.
  • WinRM — Windows Server. Uses username and password over HTTPS. Built into Windows Server 2012 R2 and later.
  • AWS SSM — EC2 instances on AWS. Uses IAM credentials — no open ports or SSH key required.

SSH (Linux / macOS)

  • Open a server in FMS Admin and click the SSH Setup button.
  • Enter your SSH host (hostname or IP), port (default 22), and username.
  • Paste your private key in PEM format (RSA, ECDSA, or Ed25519). The key is encrypted before being stored.
  • Click Test Connection. FM Dojo connects, auto-detects the FileMaker log directory, and saves the configuration.
Tip: Use a dedicated SSH user. On Linux, add it to the fmsadmin group for log access: sudo usermod -aG fmsadmin fmdojo. On macOS, restrict access to /Library/FileMaker Server/Logs.

WinRM (Windows)

WinRM is built into Windows Server 2012 R2 and later — no extra software required. FM Dojo connects over HTTPS (port 5986) using a Windows account username and password.

  1. On the Windows Server, open an elevated PowerShell and run:
    Enable-PSRemoting -Force
    $cert = New-SelfSignedCertificate -DnsName $env:COMPUTERNAME -CertStoreLocation Cert:\LocalMachine\My
    New-Item -Path WSMan:\localhost\Listener -Transport HTTPS -Address * -CertificateThumbPrint $cert.Thumbprint -Force
    New-NetFirewallRule -Name 'WinRM-HTTPS' -DisplayName 'WinRM HTTPS' -Enabled True -Direction Inbound -Protocol TCP -LocalPort 5986
  2. Optionally create a dedicated account: net user fmdojo YourPassword /add then net localgroup administrators fmdojo /add
  3. In FMS Admin, open the server and click WinRM Access. Enter the host, port (5986), username, and password, then click Save & Test.
Tip: The full PowerShell setup commands are also shown inside the WinRM setup form in FMS Admin — you can copy them from there.

AWS SSM (cloud)

If your FileMaker Server runs on AWS EC2, FMS Admin connects via AWS Systems Manager — no open SSH port or key management required.

  1. In AWS IAM, create a user with the AmazonSSMFullAccess and AmazonEC2ReadOnlyAccess policies. Generate an Access Key ID and Secret Access Key for that user.
  2. Go to the Connections page, click Connect AWS / Google Cloud / Linode, and select AWS EC2.
  3. Enter a name, your Access Key ID, Secret Access Key, and the region your instance is in. Click Connect.
  4. Click Discover Instances to list running EC2 instances, then Add as FM Server next to yours.
Tip: The EC2 instance must have the SSM Agent running (pre-installed on Amazon Linux 2, Ubuntu 16.04+, Windows Server 2008+) and an IAM instance role with AmazonSSMManagedInstanceCore attached. System metrics (CPU, disk) require SSH in addition to SSM.

Google Cloud (GCP)

GCP uses a Service Account JSON to discover Compute Engine VMs. FM Dojo uses the JSON only to list instances and auto-fill the SSH host — you still need SSH configured for log access.

  1. Open the Google Cloud Console and navigate to IAM & Admin → Service Accounts.
  2. Click Create Service Account and give it a name (e.g. fmdojo). Grant the minimum roles your use case requires — Compute Viewer (roles/compute.viewer) is sufficient for instance discovery. Grant additional roles (e.g. Compute Instance Admin) only if needed. Follow the principle of least privilege.
  3. Open the new service account, go to the Keys tab, click Add Key → Create new key, select JSON, and download the file.
  4. Go to the Connections page, click Connect AWS / Google Cloud / Linode, select Google Cloud, and paste the entire contents of the downloaded JSON file.
  5. Click Connect, then Discover Instances. Click Add as FM Server — the SSH host is pre-filled from the instance's external IP.

Linode

Linode uses a Personal Access Token to list your instances. Like GCP, it auto-fills the SSH host — SSH credentials are still needed for log access.

  1. Log in to Linode Cloud Manager, click your profile icon, and go to API Tokens → Create Personal Access Token.
  2. Give it a label, set Linodes to Read Only, and save. Copy the token (it is only shown once).
  3. Go to the Connections page, click Connect AWS / Google Cloud / Linode, select Linode, and paste your token.
  4. Click Connect, then Discover Instances. Click Add as FM Server to add any instance.

Reading logs

Once SSH (or WinRM) is configured, the Logs tab shows a checklist of available log sources. FM Server log files:

  • Event.log — server events, database opens/closes, schedule runs
  • Access.log — client connection and authentication records
  • Stats.log — performance metrics (connections, calls per minute, elapsed times)
  • fmdapi.log — FileMaker Data API requests and errors
  • fmshelper.log — FileMaker helper process activity
  • fmodata.log — OData endpoint activity
  • TopCallStats.log — the most expensive script and database calls
  • wpe0.log / wpe_debug.log — Web Publishing Engine activity and debug output

Check one or more log files and click Load. Each file's last 500 lines are fetched in parallel and merged into a single time-ordered stream. Each line is prefixed with a color-coded tag — [EVENT], [ACCESS], [DAPI], etc. — so you can tell logs apart at a glance. Use the Lines selector to load more (up to 2 000 lines per file).

System log sources

In addition to FM Server log files, the Logs tab provides access to operating system logs (SSH required):

  • journalctl (Linux only) — the systemd journal, which aggregates all service logs. You can filter by any service unit name (e.g. fmserver, nginx, sshd). Useful for diagnosing startup failures and service crashes that don't appear in FM logs.
  • Kernel log (Linux, SSH) — kernel messages via journalctl -k. Shows OOM kills, disk I/O errors, hardware failures, and driver issues. This is the same source the Watchdog alerts scan.
  • Syslog (Linux/macOS, SSH) — the OS system log. On Linux, reads /var/log/syslog or /var/log/messages depending on the distribution; falls back to journalctl if the file isn't accessible. On macOS, reads /var/log/system.log.
  • Auth log (Linux, SSH) — SSH and PAM authentication records. Reads /var/log/auth.log (Debian/Ubuntu) or /var/log/secure (RHEL/Rocky/CentOS). Useful for spotting brute-force attempts or failed SSH logins.
  • Windows Application / System Event Log (Windows, WinRM) — the Windows Event Log for the Application and System channels. Shows Windows service errors, application crashes, and system events.
Tip: Kernel log and Syslog are only shown for SSH-connected Linux servers; Auth log is Linux-only. Windows Event Log sources are only shown when WinRM is configured. journalctl appears for Linux SSH servers with a detected FM log directory.

AI log analysis

Click Analyze with AI to send the current log view to the AI for analysis. You get a structured report covering:

  • Summary — what is happening overall on the server
  • Errors & Warnings — a list of every error or warning with plain-English explanations
  • Patterns — repeating issues, performance concerns, or unusual activity
  • Recommendations — actionable steps to address the problems found

To ask a specific question about the logs instead of a full analysis, type your question in the input box next to the Analyze button (or press Enter). For example: "Why are clients getting disconnected at 3 AM?" or "Are there any authentication failures?"

Tip: AI log analysis consumes tokens from your balance. Keep your log selection focused — loading only the relevant log files reduces token usage and gives the AI a tighter context to work with.

9. Tokens & Pricing

FM Dojo uses a token-based system. Every AI interaction (chat messages, AI Generate, Code Chat) consumes tokens from your balance.

How tokens work

  • Each subscription plan includes a monthly token allowance.
  • Unused tokens roll over — they accumulate month to month, so nothing is wasted.
  • Your token balance is shown in the header and updates in real time after each message.

Pricing

  • Monthly subscription plans at different tiers.
  • Multi-currency support — USD, EUR, GBP, AUD, CAD, JPY, NZD.
  • Upgrade, downgrade, or cancel anytime from your dashboard.
  • Payments are handled securely through Stripe.
Tip: Check the Pricing page for current plans and token allowances.

Rewards

Earn free tokens by spreading the word about FM Dojo. Visit the Rewards page to see available actions and submit your proof.

Earning tokens

Each reward action specifies the number of tokens you'll receive upon approval. Tokens are added to your balance once an admin reviews and approves your submission — typically within a few days. Current actions include:

  • Post on LinkedIn — share FM Dojo with your professional network
  • Post on X / Twitter — mention FM Dojo in a post
  • Post in a Facebook Group — share in a FileMaker or developer community group
  • Refer a friend who subscribes — your highest-value reward

Social sharing rewards

For social posts, submit the URL of your published post as proof. For referrals, enter the email address of the person who subscribed. Each action can only be submitted once. You can track the status of all your submissions — pending, approved, or rejected — on the Rewards page.

Tip: Referral rewards have the highest token value. If someone in your network is looking for a FileMaker AI assistant, a direct referral is the fastest way to earn a significant token boost.

Roadmap & Feature Requests

See what's coming, vote on what matters most, and submit your own ideas on the Roadmap page.

Submitting a feature request

Click Request a Feature and fill in a title, description, and category (Chat, Code Editor, Diagram, or New Feature). You can also indicate how important the feature is to your workflow — from "Nice to have" to "Critical." Submissions are reviewed by the team and approved requests move to the public roadmap.

Voting

Upvote any request on the roadmap to signal demand. The vote count is visible on each card and informs prioritization. You can filter by status (Planned, Approved, Launched) to see what's already in progress or completed.

Tip: If you have a critical workflow need, mark it as Critical when submitting — it stands out in the review queue.

10. Account & Security

  • Email + password or Google OAuth login
  • Two-factor authentication (2FA) — set up with any authenticator app (Google Authenticator, Authy, etc.)
  • Backup codes — generated during 2FA setup for account recovery
  • Session management — view all active sessions across devices and revoke any one
  • Password change — update your password from the Account page

All sessions are encrypted and expire automatically. Rate limiting is applied to all API routes.

AI Preferences

Customize how the AI responds from the Account page:

  • Response Style — a slider from Precise (lower temperature, more deterministic) to Creative (higher temperature, more varied). The default is 0.70.
  • Concise mode — when enabled, the AI gives shorter, more direct answers with less preamble and explanation.

Changes take effect on the next message you send.

11. Accessibility

FM Dojo includes several features designed to make the interface more comfortable and usable for a wide range of users and preferences.

Text size

Use the A− A A+ controls in the header to increase or decrease text size across the entire interface. Your preference is saved and restored automatically on your next visit. Three steps are available — default, large, and extra-large.

Dark mode

Click the sun/moon icon in the header to switch between light mode, dark mode, and system mode. System mode follows your operating system's appearance setting and switches automatically when your system preference changes.

Collapsible sidebar panels

The Chat and Code Editor both have sidebar panels that can be hidden to maximize the main content area. Use the panel toggle icon in the header to show or hide them. This is especially useful on smaller screens or when you want a focused, distraction-free workspace.

Keyboard navigation

The code editor (powered by CodeMirror) is fully keyboard-accessible. Standard keyboard shortcuts apply throughout — see the Code editor shortcuts table in the Tips & Shortcuts section. Tab navigation works across all interactive elements in the app.

Voice dictation

A microphone button in the bottom-right corner of every page lets you dictate into any text field, input, or editor. Click once to start recording, click again to stop — your speech is transcribed by OpenAI Whisper and inserted at the cursor. Your browser will ask for microphone permission the first time; click Allow. Works in all modern browsers on HTTPS.

Reduced motion

FM Dojo respects the prefers-reduced-motion media query. When reduced motion is enabled in your operating system accessibility settings, animated transitions are minimized across the interface.

Semantic structure

Page headings, landmark regions, and ARIA labels are used throughout the app to support screen readers and other assistive technologies. Code blocks in AI responses include descriptive labels and one-click copy buttons accessible via keyboard.

12. Tips & Shortcuts

Text size

Use the A− A A+ controls in the header to adjust text size across all pages. The setting is remembered between sessions.

Dark mode

Toggle between light, dark, and system theme using the sun/moon icon in the header.

Sidebar panels

The Chat and Code Editor both have collapsible sidebar panels. Use the panel toggle icon in the header to show or hide them.

Code editor shortcuts

ShortcutAction
TabAccept autocomplete suggestion
Cmd/Ctrl + FFind & replace
Cmd/Ctrl + ZUndo
Cmd/Ctrl + Shift + ZRedo

General tips

  • The AI is most helpful when you give it context — paste your code, describe what you're trying to do, and mention the FileMaker version if relevant.
  • Upload your snapshots or script PDFs directly into the chat for analysis.
  • Use Diagram Chat to quickly scaffold a relationship graph from a plain-English description, then refine it manually.
  • Share chat links with colleagues instead of copying and pasting long conversations.