Skip to contentChangelog
Run notifications from plugins

- Plugins can report job runs. With such a plugin installed, the job editor gets a Notifications section: turn the plugin on for the job and choose when it writes, which runs it reports and what it attaches. Manual, scheduled and agent runs all count
- Plugin settings appear where they apply: in the plugin settings, in each plugin step, or in the job's notifications
- Some plugin settings get a search button that offers values, such as a chat. One result fills the field, several open a list, and the chosen value keeps its name
- A plugin can come in any one language. Its page and the marketplace show its languages, and a plugin without a translation for the interface language is marked No translation
- The marketplace tells when a plugin needs a newer QueryLane and does not offer to install it
- Exported jobs include their notifications and the plugins they need, without secret values
- The code editor highlights Markdown
- Fixed plugin settings that sometimes did not show when more than one plugin was installed, and the extra space on the right of plugin settings
Plugins and assistant tools

- New Settings → Plugins with a marketplace of official plugins. Before installing you see what a plugin can access; installed plugins can be updated, turned off or removed, and installing and removing show their progress step by step
- The first plugin, Browser, runs Chromium without a window: a job step opens web pages, clicks through them and collects data. Each plugin has its own settings and named presets, and a step can override them
- Screenshots and files that steps save stay with the run in the history, where you can preview and open them. A run keeps up to 100 MB of such files
- The AI assistant can now work with your jobs: read them, change steps, test them and use plugin tools such as the browser. Before it changes data or runs anything it asks you: Allow once, Allow in this chat or Deny. Stop also cancels the runs it started. Turn this off with Settings → AI → Tools in chat
- An open job editor picks up the assistant's changes. If you have unsaved edits, choose Keep my edits or Load the assistant's version
- Exported jobs carry the plugins they need and their presets, without secret values. Importing such a job offers to install, turn on or set up the plugins
- JavaScript steps get the Execution timeout field for scripts that need more than the default 30 seconds
- The code editor highlights Python and shows the step code at once instead of an empty field while it loads
- The job page shows the title and actions in one row, then the description and the schedule and other details
- Click the version in Settings → About to read the notes of the installed release
- Run history keeps the 50 latest runs of each job and removes older ones with their result files
- Fixed a full-window error «The quota has been exceeded» when the app's local storage filled up
SQLite databases

- New SQLite connection: open a database file or create a new one, optionally Read only. Tables, views, indexes and triggers appear in the explorer
- Browse and edit SQLite data, run queries and scripts with EXPLAIN QUERY PLAN, import files into tables and export results. Integers beyond 2^53 keep every digit
- A long SQLite query stops at once when you cancel it or when the query timeout is reached, and the rest of the app stays responsive
- The schema editor creates and changes SQLite tables: rename tables and columns, change types, defaults, NOT NULL and the primary key. Changes SQLite cannot make in place rebuild the table with its data, indexes and triggers, and the DDL preview shows the exact script
- SQLite connections work in job SQL steps and through the QueryLane MCP server, and the Navicat import brings them over
- Renaming a column in the schema editor now works on PostgreSQL, CockroachDB, YugabyteDB, MySQL, MariaDB and Percona Server; the new name used to be dropped. Renaming a primary key column keeps the key
- The DDL preview uses the new names after a table or a column is renamed
- New switch Settings → General → Open at login, off by default
- Object details show keys and constraints the same way for every database. MySQL and MariaDB users without access to the constraint list now see primary, unique and foreign keys
Job schedules

- New Schedule button on a job: run it every few minutes or hours, daily on chosen weekdays, monthly, or by a cron expression. The dialog shows the next runs and rejects an expression macOS cannot run
- A scheduled job runs while the Mac is on, also when QueryLane is closed. A run missed while the Mac slept starts on wake, and a run is skipped while the previous one is still going
- All schedules share one QueryLane item in Login Items & Extensions of macOS, whatever their number. QueryLane shows when that item is turned off there and opens the settings
- A failed run, a run stopped by a result check and check warnings arrive as a notification; clicking it opens the job
- New Settings → Schedules: every scheduled job with its next and last run and a switch, plus the state of background runs and of failure notifications
- The job header and the job list show the schedule and the next run, and execution history marks the runs the schedule started
- AI agents set a schedule through the job fields and read its state through the QueryLane MCP server
- In the release notes window only the notes scroll, while the title and the artwork stay in place
Result checks for job steps

- New Result checks in job steps: rules the step result must meet, such as a minimum or maximum number of rows, fields that must be present, fields that must not be empty, unique values, allowed values and a regular expression. A failed check either stops the job before the next steps run or only adds a warning
- Rows from points the checks at an array inside the result, for example
items of an API response
- Fields and allowed values are suggested from the step's last run, and a field that is not in it is highlighted
- Execution history shows warnings on the run and, for each step, which checks failed with sample rows. A run stopped by a check names the check that failed
- AI agents can add checks through the QueryLane MCP server, and the AI assistant sees them
- Job import asks which local database to use for each database the imported steps select and marks databases the chosen connection does not have
- The row editor, the row viewer, the value editor and the large code editor share one dialog: the title and table in the header with copy, format and expand, hints and actions at the bottom. The row editor can open full screen
- Multi-line text in result cells stays on one line and shows line breaks as ↵
- Connection and job actions sit next to the name, and long job names are cut to one line
- Chips in filters and the import wizard stand out from the field in the dark theme
- A table tab left open loads its rows when you open Connections instead of staying empty until you refresh it
Collapsible job cards and fixes

- The steps and execution history cards of a job collapse with a chevron at the right of their header. QueryLane remembers what you collapsed for each job, also after a restart
- Both cards now share one header: the title and counters on the left, the controls on the right. The steps card switches between List and Graph from its header, and the duplicate header inside the step list is gone
- Result table column widths are kept after you resize them
- Format code in the SQL editor writes keywords in upper case
- Excel import reads the worksheet you picked instead of always the first one
- Importing dates with a time zone no longer fails on every row
- Streamed AI assistant answers keep updating instead of stopping after the first part
- The query tab you had open is active again after a restart
- A collapsed section in a run's details opens on the first click
- Deleting a connection names it as a source or a target correctly
- Notifications show their description, not only the title
- The QueryLane MCP server reports the app's version to AI clients
Charts in jobs and job files

- New Chart step: JavaScript that returns ECharts charts, one or several per step, with templates for a line, bars, a pie, a key number and several charts
- Runs with charts get a Report tab next to the results; it opens first when the job ends with a chart step. Charts open in full screen and save as PNG or SVG
- The AI assistant writes chart steps, and AI agents can render a run's charts to PNG or SVG
- SQL and MongoDB steps can use another database of the same connection, and PostgreSQL steps a chosen schema. The explorer opens objects from other databases in their own tabs, and agents get the same options
- Jobs can be exported to a
.querylane.json file: one job, a folder or a selection. Import them with the button or by dropping the file onto the job list; QueryLane matches connections, asks for secret values, offers missing packages and lets you replace a job or add a copy
- Secret variable values stay out of exported files, and export warns about credentials written directly into steps. Imported steps run code on your computer, so import files only from people you trust
- A MongoDB replica set that advertises addresses your computer cannot reach now shows a clear error with an Enable direct connection button
- New Appearance section in Settings: theme, language, hover hints and the default result view. Hover hints can be turned off
- Variables with a secret word in an upper-case name, such as
SMTP_PASSWORD or API_TOKEN, are now always treated as secrets and are no longer pushed to git in plain text
- If you share jobs through git with someone on QueryLane 1.0.87, their version drops the step database and schema when it saves those jobs
Connect AI agents without manual setup

- Claude Desktop, Cursor, and VS Code can now be connected to QueryLane in Settings → CLI and MCP
- Connections now go through the
querylane command instead of paths inside the app, so moving or updating QueryLane no longer breaks them
- Existing connections are marked Update required; Update all connections moves them to the new format without touching other client settings
- Other MCP client shows ready-to-copy settings for any client that runs local stdio servers
- Clients found on this computer are listed first; the rest are collapsed into a separate group
- If another program already uses the
querylane path, QueryLane warns you and leaves the file untouched
Softer shapes

- The interface is rounder and more consistent: cards, dialogs, menus, buttons, chips, and editor suggestions share one set of corner radii
- Connection cards no longer show a table count; an open connection is marked by the green frame around its icon
- Pipeline steps reference each other only through stable
${step_id} references; numbered references such as $1 and $2 are no longer supported, so replace them in existing jobs
- Steps created through MCP or the CLI must use IDs that start with
step_
Stable connections

- Pipeline steps can now use stable
${step_id} references, so links keep working when steps are reordered or new steps are inserted
- The code editor suggests variables and step results, highlights invalid references, and opens a referenced step with Cmd+click
- Dependencies referenced in code are detected automatically and shown in job details and the dependency graph
- AI assistants connected through MCP now receive a complete pipeline authoring guide before creating or editing jobs
- Selected database rows are clearer in the dark theme, without the persistent underline on edited cells
- Existing pipelines that use
$1, $2, and other numbered references remain compatible
Clear structure

- The connection editor is now more compact: core fields, SSL/TLS and SSH settings are arranged in a clearer structure
- Objects and arrays in database results keep their actual type after deferred loading and display consistently
- Import and export icons now follow the direction data moves relative to QueryLane: down for import and up for export
Everything in place

- Release banners now load in advance, so What's new opens with its illustration already prepared
- On a slow connection, the button briefly shows progress before opening the notes
- If the banner cannot load in time, the notes open without it and stay in place
A quieter workspace

- Checking for updates no longer shows a toast when you're up to date; the result stays in update settings
- The circular update button above Settings is now slightly smaller
Coming together

- Upcoming release notes will follow your interface language: English or Russian
- The What's new window now supports a full-width illustrated banner for future updates
- Icon buttons now share softer, more consistent corners across the workspace
- The macOS installer has a refreshed appearance