FutrixData v1.0.27

FutrixData v1.0.27

Highlights

• Codex users can now install the FutrixData plugin, authorize it from the desktop app, and use the bundled sidecar and skill assets without hand-wiring MCP configuration.
• Datasource credentials can now reference existing HashiCorp Vault KV v2 secrets. FutrixData stores only the Vault location metadata, resolves the secret at runtime for the owning datasource, and strips stale inline plaintext when a real reference is present.
• New local users now receive a 30-day trial, including logged-out use, with the same effective entitlement applied across datasource limits, risk rules, sensitivity rules, and daemon access.
• The SQL console now catches common syntax mistakes before execution, offers quick fixes for issues like unclosed quotes, and renders friendlier syntax-error panels with jump-to-position and Ask AI actions.

Fixes

• Third-party agents can no longer drive approval-gated operations with untrusted approval context; agent-side gates now reject those paths instead of treating them as locally trusted UI actions.
• Datasource timing diagnostics were added for connection, schema, query, explain, and write-preview paths, and diagnostic snapshots are preserved in the Wails runtime so local support and debugging flows can inspect real timing data.
• Secret reference handling now rejects agent, MCP, CLI, and HTTP payloads that try to carry real secret refs directly, reducing the chance that externally-owned credentials can be redirected or exposed.
• SQL syntax errors from MySQL and PostgreSQL now preserve the failing SQL snapshot and map the reported location back into the editor more reliably, including substatement execution cases.

Upgrade notes

• No manual data migration is required.
• Existing datasource credentials continue to work unchanged unless you choose to move them to Vault-backed references.
• Vault-backed credentials require an existing HashiCorp Vault KV v2 secret and provider configuration; FutrixData does not create, rotate, or delete externally-owned secrets.
• Codex plugin users should install or update the plugin and authorize it from the FutrixData desktop app before using Codex-side tools.

FutrixData v1.0.26

FutrixData v1.0.26

Highlights

• FutrixData can now open and run in a guest state while still applying Free-plan limits for local datasources and devices, so first-time users can start local setup without being forced through sign-in first.
• Signed-in Free users can manage their own custom risk rules and sensitivity rules, while built-in rule overrides remain reserved for Pro.

Fixes

• Policy-changing operations now consistently require an active signed-in desktop user, including custom risk-rule deletion, sensitivity configuration changes, and agent-side policy mutations. Agent access keys alone no longer bypass the desktop session requirement.
• Guest users now see localized sign-in guidance and disabled controls for risk and sensitivity edits instead of reaching backend errors.
• Plan-gated risk and sensitivity screens received small accessibility and layout fixes, including import/export labels, wider touch targets, and safer AI sidebar and toolbar spacing.

Upgrade notes

• No manual data migration is required.
• No datasource configuration changes are required.
• If an agent tool needs to change risk rules or sensitivity policy, sign in to the FutrixData desktop app first. Read-only workflows and normal Free-limited local usage remain available without migration.

FutrixData v1.0.25

FutrixData v1.0.25

Highlights

• Redis protobuf schema uploads now keep their local store during app startup and runtime recovery, so saving a schema no longer fails with "store unavailable" after the app has been reloaded or restored.
• Redis and MongoDB risk rules are easier to cover correctly: the command selector now has an explicit "all commands" wildcard, and Redis rules can browse and search the full Redis command catalog before applying coverage.
• Redis bitmap and binary string values now open in a binary-safe inspector view with a Binary badge, hex dump, and Auto/Text/Hex display controls.

Fixes

• Switching a datasource trust level to Danger now uses an in-app confirmation dialog, avoiding the WebKit confirmation issue that could prevent the change from being applied.
• Redis and MongoDB wildcard command rules now match parsed commands and subcommands more reliably, including rules that intentionally cover every command.
• Redis full-value preview now preserves complete backend binary payloads instead of falling back to truncated text or empty structured output.
• Redis command, readback, TTL, cleanup, and risk-gate behavior now has a dedicated FutrixData Redis skill regression harness.

Upgrade notes

• No manual data migration is required.
• No datasource configuration changes are required.
• Existing Redis protobuf schema data remains compatible.

FutrixData v1.0.24

FutrixData v1.0.24

Highlights

• Redis protobuf schemas now persist locally instead of living only in the current session. You can manage saved schemas, search schema/message type pickers, and let FutrixData auto-detect the best message type when opening a Redis key.
• The Redis console now behaves more like a dedicated key-value inspector: first-open keys show typed badges, TTL and size metadata are fetched in batches, full values render as structured tables where appropriate, and JSON strings can switch between raw and pretty views.
• The Direction A console design now extends across the shared SQL, MongoDB, Elasticsearch, DynamoDB, D1, and related console surfaces with cleaner tabs, flatter toolbars, consistent pane headers, and aligned result styling.
• Expired Pro licenses now display and gate consistently as Free. The account page shows the expired state directly, and datasource/risk-rule creation uses the same effective entitlement as the backend.

Fixes

• Redis "View full" no longer collapses hashes, lists, sets, sorted sets, streams, or empty values into {}.
• Redis protobuf Wails bindings now expose timestamps in a frontend-compatible format, so saved schema metadata can be listed reliably.
• Console toolbar controls no longer overlap between roughly 900px and 1200px. Long datasource subtitles are truncated with a tooltip, and the dense console action row stacks without leaking compact button styles into unrelated forms.
• Shared console visual inconsistencies were cleaned up across statement tabs, result headers, Elasticsearch titles, DynamoDB limit controls, fonts, and toolbar buttons.

Upgrade notes

• No manual data migration is required. Existing Redis protobuf schema text from a session is saved into the new local schema store on first load.
• Expired Pro accounts will now be shown and limited as Free after the update. Active Pro accounts are unchanged.
• No datasource configuration changes are required.

FutrixData v1.0.23

FutrixData v1.0.23

Highlights

• Added typed Redis agent tools so AI agents can call Redis with structured arguments instead of a single fragile command string. Values that contain spaces, quotes, or JSON bodies are preserved more reliably through Skill, MCP, and CLI execution.
• Added a Redis batch execution primitive for pipeline-style multi-command work. Related Redis operations can now be reviewed and approved together, with item-level success or error details in the result.
• Clarified the agent access-key model with datasource scope, optional expiry, revocation behavior, and explicit write-approval boundaries. Existing keys remain compatible while new integrations can be constrained more precisely.
• Updated managed Skill documentation and CLI ergonomics with agent-key environment variables, DynamoDB bounded-pagination examples, server-side cap tables, approval-layer guidance, and a reusable pagination loop.

Fixes

• Redis risk analysis now handles Lua write intent, flush/write command classification, quoted keys, empty quoted arguments, and overlapping single-quote escapes more consistently across direct statements and argv-based calls.
• Redis console protobuf decoding now accepts unpadded base64 payloads, so valid protobuf values are less likely to be rejected because of encoding padding differences.
• DynamoDB bounded execution now applies explicit caps for page size, returned rows, page count, and evaluated items, with localized cap labels and clearer source metadata in console flows.
• Console layout regressions around paging source labels, entity tabs, sidebar docking, SQL editor parity, and quick-prompt controls received focused coverage and fixes.

Upgrade notes

• No data migration is required. Existing agent access keys continue to inherit the local user's datasource visibility unless a narrower scope or expiry is configured.
• Refresh or reinstall managed FutrixData skills if you want the new v1.2.3 agent-key, approval-layer, Redis, and DynamoDB examples in your local agent documentation.

FutrixData v1.0.22

FutrixData v1.0.22

Highlights

• DynamoDB console pagination is now user-controlled instead of silently clamping high page counts. Teams that need strict limits can enforce them with FutrixData risk rules instead of being blocked by a fixed UI/backend cap.
• DynamoDB table selection now generates sample PartiQL using the table's real partition key, and includes the sort key when one exists, so first-run table queries need less manual editing.

Fixes

• Redesigned DynamoDB repair and index-suggestion banners so the primary action applies the suggested statement and runs it in one click, keeping the editor text and executed query aligned.
• Prevented stale DynamoDB describe responses from overwriting the active entity after users switch tables quickly.
• Improved the entity field and index panel layout so long table, field, and index names wrap cleanly without detached PK/SK rows or horizontal overflow.

Upgrade notes

• None. This release does not require data migration or configuration changes. Existing DynamoDB risk rules remain the right place to enforce organization-specific query budgets.

FutrixData v1.0.21

FutrixData v1.0.21

Built from the latest main release pipeline on 2026-05-09.

Release artifacts

• FutrixData-v1.0.21-macos-arm64.dmg
• FutrixData-v1.0.21-macos-amd64.dmg
• FutrixData-v1.0.21-windows-amd64-installer.exe
• FutrixData-v1.0.21-linux-amd64.tar.gz
• SHA256SUMS.txt

Verification

• Packaging CLI tests passed.
• MCP and updater backend tests passed.
• Updater frontend store tests passed.
• macOS DMGs were signed, notarized, stapled, and validated.
• Linux archive layout was inspected.

FutrixData v1.0.20

FutrixData v1.0.20

Built from the latest main release pipeline on 2026-05-09.

Release artifacts

• FutrixData-v1.0.20-macos-arm64.dmg
• FutrixData-v1.0.20-macos-amd64.dmg
• FutrixData-v1.0.20-windows-amd64-installer.exe
• FutrixData-v1.0.20-linux-amd64.tar.gz
• SHA256SUMS.txt

Verification

• Packaging CLI tests passed.
• MCP and updater backend tests passed.
• Updater frontend store tests passed.
• macOS DMGs were signed, notarized, stapled, and validated.
• Linux archive layout was inspected.

FutrixData v1.0.19

FutrixData v1.0.19

Built from the latest main branch on 2026-05-04.

This release includes the latest FutrixData desktop changes from main and refreshes the public macOS, Windows, and Linux downloads.

Verification

• macOS arm64 and amd64 DMGs were signed, notarized, stapled, and checked with Gatekeeper.
• Windows amd64 installer was built successfully.
• Linux amd64 archive was built and its root folder was checked.
• SHA-256 checksums are attached in SHA256SUMS.txt.

FutrixData v1.0.18

FutrixData v1.0.18

Built from the latest main branch on 2026-05-04.

This release includes the latest FutrixData desktop changes from main and refreshes the public macOS, Windows, and Linux downloads.

Verification

• macOS arm64 and amd64 DMGs were signed, notarized, stapled, and checked with Gatekeeper.
• Windows amd64 installer was built successfully.
• Linux amd64 archive was built and its root folder was checked.
• SHA-256 checksums are attached in SHA256SUMS.txt.