v1.6.0

Released 2026-10-19.

This is a minor release. Your profiles, saved queries, settings and stored data carry over unchanged, and no command or setting was removed. Nothing needs to be done for a normal install. Read UPGRADE.md ("Upgrading from 1.5.0 to 1.6.0") for the few behavior changes you may notice.

In short:

• New: Layout Mode has standard field sizes and spacing, arranging and standardizing a layout (each undone in one step), and starter templates. The find form, Record Editor, Record Viewer and generated web layout views now show fields the same way.

• Fixed: a certificate you trusted could still fail with a misleading "not trusted" error under VS Code's default network setting; the message now says why and names the setting to change. Script runs return only the script's answer, copy-as-code is more exact, and profile changes made in another VS Code window show up within two seconds.

• [FEATURE] Layout Mode adds standard field sizes and spacing, arranging the selection into a standard form and standardizing it (each with one Undo step), and blank, form, two-column and first-portal starter templates (offered for a new, empty web layout). Synced field types and FileMaker field order guide placement; names and behavior bindings stay intact.

• [FEATURE] Find forms, Record Editor, Record Viewer and generated web layout views share Layout Mode field sizes, top labels and responsive spacing. The next time you generate or preview an FM Web app, its managed runtime files are refreshed to template version 3; a managed file you edited is left alone and named in a warning.

• [FIX] A certificate you trusted (pinned) could still fail with a misleading "not trusted" error when VS Code's http.proxySupport setting is override (its default): VS Code then replaces the extension's own connection, so the extension cannot check the certificate you trusted and VS Code's normal check applies instead. A server whose certificate VS Code trusts anyway (for example from Let's Encrypt) keeps working. Under override the trust is not enforced: a different certificate that VS Code trusts would be accepted too. The message now says why, for every kind of request and for proxy connections, and names the fix: set http.proxySupport to fallback, or install a public certificate on the server and choose Forget trusted certificate. The trust dialog, the wizard and the message after trusting say the same. The on value was not tested.

• [FIX] Script runs return only the script's answer, including the plain GET form. Layouts, scripts and container fields named . or .. are refused before a request is sent, also in proxy mode.

• [FIX] Copied TypeScript keeps a field named __proto__. Copied proxy requests keep a trailing slash. Copied API base paths stay as configured (including percent escapes), and curl switches off bracket and brace expansion when needed.

• [FIX] New files written by Write AI Context and new FM Web runtime files are readable by you only; a file that is replaced keeps its permissions (without setuid, setgid or sticky bits).

• [FIX] Folder names keep visible emoji presentation selectors while refusing hidden standalone selectors. The Output panel and Show Effective Settings now warn when ai.hiddenFields is a string instead of a list; hiding is unchanged: the whole string still counts as one field name, even with commas.

• [FIX] Profile changes made in another VS Code window refresh the connection status, explorer and AI tools within two seconds; configuration and secret changes also refresh them.

• [FIX] Layout Mode lists fields in FileMaker's field order, not alphabetically. The Record Viewer also asks the server for the layout's field details at the same time as the record when schema metadata is on (it is not added to the request history, and a failure is ignored).

• [INTERNAL] The test mock of FileMaker Server's default certificate now matches a real server exactly, with an end-to-end test of the trust flow. Connection-limit tests no longer depend on timing.

v1.1.0 — UX, a11y, security, reliability

Major usability, accessibility, security, and reliability release.

Onboarding

• Added a first-run Getting Started walkthrough (Add Profile → Test Connection → Query Builder) with screenshots and clear action verbs.
• Added a dedicated activity-bar container with a FileMaker icon.
• Added a Welcome view that surfaces Add Connection Profile / Open Walkthrough when no profiles exist (previously the empty state was buried behind always-present Environment Sets / Jobs roots).
• Connection wizard restored: fixed a crash on load caused by a missing <form id="wizardForm"> wrapper. Save and Test Connection buttons are now reliably bound.
• Connection wizard collapses advanced server fields (API Base Path, API Version) under a <details> disclosure so first-time users see only what they need.
• Connection wizard shows live progress during Test Connection with phase-by-phase status.
• Walkthrough id computed from context.extension.id at runtime so a publisher rename can't silently break the walkthrough; the first-run flag is now only set after the walkthrough opens successfully.

Connection / Status

• Added a persistent $(plug) FileMaker: <profile> status-bar item so you always know whether you're connected and to which profile. Click to open the Explorer.
• Proactive session-token refresh in fmClient keeps long-running sessions alive without manual reconnect.
• Exponential-backoff retry on transient login errors during Connect.
• Inline Test Connection result + save guard: badge shows untested / passed / failed / stale; configurable policy (off / warn / block) controls whether saving without a recent test is allowed.

Errors & Recovery

• Error toasts now offer Retry / Edit Profile / Open Settings actions inline. Retry re-invokes the original command; Edit Profile reopens the wizard for the failing profile; Open Settings jumps to the relevant setting key.
• Structured error reports with the full request chain, redacted headers, and a one-click Copy as Bug Report action that produces a markdown report safe to paste into an issue.
• Graceful fallback in secretStore when VS Code SecretStorage is unavailable (AES-256-GCM PBKDF2 envelope).
• Offline-mode status-bar indicator with stale-cache awareness.
• Circuit-breaker registry plus Show Circuit Breaker Status command for diagnosing repeated failures.

Accessibility

• Connection wizard required fields now mark aria-required, render a visible *, and link hints via aria-describedby so screen-reader users get full context.
• Authentication mode toggle exposes proper aria-pressed state.
• Password / username inputs include autocomplete hints.
• Focus management: focus lands on the first input on open; Query Builder focuses the profile select after init.

Discoverability

• Command palette flood: ~33 commands gated behind context keys (filemaker.hasProfiles, filemaker.hasSchemaSnapshots, filemaker.enterpriseMode, filemaker.advanced.powerUserMode). New users see only what's relevant; advanced/diagnostic commands stay hidden until needed.
• Power-user mode setting unlocks plugin / circuit-breaker / diagnostics commands.

Settings

• Deduplicated filemakerDataApiTools.* settings under the canonical filemaker.* namespace. Legacy keys now carry markdownDeprecationMessage; explicit values continue to be honored with a one-time deprecation toast pointing at the new key.
• Validation: filemaker.schema.hashAlgorithm is checked against crypto.getHashes() at activation; an unsupported value surfaces a toast instead of a silent fallback.
• Declared capabilities.untrustedWorkspaces so VS Code's built-in trust banner fires up front (instead of bespoke command-level toasts).

Documentation

• Rewrote USER_GUIDE.md connection sections to match the actual webview UI (the previous copy described a quick-pick flow that no longer existed).
• Walkthrough markdown gained screenshots reused from the marketplace assets.
• Corrected an incorrect tip claiming profiles were workspace-scoped; profiles are global, only saved queries are workspace-scoped.

Security & Reliability

• Token-bucket rate limit plus per-session request budget on the FM bridge server.
• Profile cache keys versioned (v2::) and include the normalized serverUrl to prevent cross-profile cache poisoning.
• Documented proxy threat model; minimized outbound profile payload.
• Structural validator for inbound webview messages.

Performance

• Replaced 59 per-command activationEvents with onStartupFinished and lazy command registration.
• batchExportFind now streams CSV rows instead of buffering the entire result set.
• Refactored fmClient to extract SessionTokenTracker for clearer proactive-refresh state.

Tests

• New unit-test coverage for schemaService, batchService, error-action selection, deprecated-setting tracking, command-resolution helpers, connection status bar, and webview structural assertions (catches the kind of HTML/JS mismatch that hid the wizard form bug).

v1.0.0 - Production Release

FileMaker Data API Tools for VS Code - v1.0.0

Free, open-source VS Code extension for the FileMaker Data API.

Install

1. Download filemaker-data-api-tools-1.0.0.vsix below.
2. In VS Code, open Command Palette and run Extensions: Install from VSIX...
3. Select the downloaded file and reload.

Highlights

• Full CRUD: find, get, create, edit, delete records
• Query Builder, Record Viewer/Editor, Script Runner, Schema Diff webviews
• Value lists, container fields, portal support, global fields
• Compound find queries with omit support
• Batch export/update with concurrency control
• Enterprise role guards and workspace trust
• 253 tests across 58 test files
• No telemetry