What changed, week by week.

One console, four tools: send work from Chat to Dev, App Generator or Automation

Chat, Dev, App Generator and Automation now hand work to each other. A new Send to another tool chip beside the composer opens a transfer dialog: you choose the destination, describe the request, and can attach selected messages or documents as supporting material. The receiving tool gets a linked conversation with the brief and acceptance criteria, and the result travels back to the conversation that asked. An analysis in Chat can become an app request, the app can ask Dev for a Priority change, and the verified result returns through both conversations. Opening the dialog never starts a model run; nothing moves until you send it.

Sources: priority-dev#329, priority-dev#335, priority-dev#341

Fast and Deep answers in Chat

Simple data questions — a count, a total, a top list — now run in a Fast mode that goes straight from your Priority map to a checked query, with less deliberation, and shows only the finished answer instead of its working notes. Deep, selectable in the composer, spends more reasoning and a larger query budget on questions that need it. Follow-ups about the same records reuse what was just learned instead of rediscovering it, and highest/lowest questions return the document's business identifiers together with the amount.

Sources: priority-dev#325, priority-dev#330, priority-dev#331, priority-dev#332, priority-dev#333, priority-dev#334, priority-dev#337, priority-dev#339, priority-dev#340

One shared Priority sign-in across Chat, BI Generator and the licensing portal

Connecting a product to Priority is now the same short step everywhere. Pick your tenant, and the connection is named for you and pre-set to that tenant's company, with an optional company picker and the advanced settings folded away. Chat and BI Generator open the shared sign-in popup directly instead of asking for a name first, and the licensing portal's connector dialog uses the same defaults without ever exposing the customer key to the browser.

Sources: WebSDKGateway#159, licensing#31, priority-dev#326, BI_Generator#86

Automation now reaches n8n on your own network

Automation no longer needs a publicly reachable n8n. A new Local / private network connection in Settings → Integrations pairs with the small daemon you already run for App Generator, so n8n on your PC or a LAN server works without opening a port. Self-signed certificates can be allowed per connection (off by default), and the Automation composer gained /plan and /checkpoint chips with an n8n-specific planning prompt.

Sources: priority-dev#310, priority-dev#313, priority-dev#317, priority-dev#321

Select and delete several conversations at once

The conversation list now has a clear Select button. Tick the chats you want, or Select all within the current mode and search, and delete them with one confirmation that states the count. Projects and files are kept, and switching chats while a deletion is running can no longer interfere with it.

Sources: priority-dev#336, priority-dev#338

Discovery says when it is incomplete, and never confirms an entity it could not check

Entity search now reports how many matches it found, whether the list was cut, and which entity types it could not search, instead of returning a silent 30. Asking about a procedure or form that does not exist answers "not found" rather than "0 fields". Form dumps carry field, subform and trigger counts, and the assistant is told to read a procedure's body before explaining it. The MCP server instructions were refreshed so connector clients such as Claude and ChatGPT know all of this.

Sources: WebSDKGateway#144, WebSDKGateway#145, WebSDKGateway#146, WebSDKGateway#157, priority-dev#309

Large results: the real total, paging on a time budget, and dashboards that refuse a partial chart

When Priority's output cap cuts a result, BI Generator now states the real row count instead of asking you to run a count yourself, and a "top N" query is paged correctly inside its own window. The gateway pages on a time budget (20 seconds by default) and says when it stopped, so a wide Hebrew report no longer runs for a quarter of a minute. Dashboards page their rows to completion, refuse to chart more rows than the limit you set, and long-running queries get the timeout headroom they need.

Sources: BI_Generator#74, BI_Generator#75, BI_Generator#76, BI_Generator#77, BI_Generator#79, BI_Generator#82, BI_Generator#84, BI_Generator#85, WebSDKGateway#142, WebSDKGateway#143

Fixed questions like "how many active customers" pulling in unrelated tables

A word such as "active" matched column names across dozens of tables and made them all query subjects. Exact table matches now scope the columns they own, and status catalogs exposed through a main form are recognized again. On the demo graph the same question went from 86 candidate tables to 34, with one subject.

Sources: BI_Generator#87, WebSDKGateway#160

Dev investigations no longer stall on missing tools or phantom permission denials

Specialist Dev agents could resolve zero tools and then receive a denial nobody issued. Their tool lists were corrected, subagents now finish in the foreground under the same approval broker, and when two agents ask for approval at once both cards stay actionable, in order. A new Dev chat also keeps its first turn on reload, and a deployment restart records what happened instead of leaving a message with no outcome.

Sources: priority-dev#306, priority-dev#307, priority-dev#308

Generated apps are checked in a real browser, at desktop and phone width

An app could compile and still crash before it drew anything. The generator now opens the app in an isolated browser at both widths, feeds any startup failure or missing mobile layout back into the build, and carries the screenshots into the handover. Login bootstrap, parent/child record updates and internal IIS publishing recipes were corrected as well, and the "Connect this computer" command now names a corporate-TLS failure and refuses to run in a system folder.

Sources: priority-dev#312, priority-dev#319, priority-dev#301, priority-dev#302, priority-dev#303, priority-dev#314

A portal-minted connector token needs no gateway key

The node's credential help said a gateway key was required in both authentication modes. It is not: a connector token minted in the licensing portal authenticates on its own. The credential description, the README and the LLM authoring guide now say when the key is actually needed.

Sources: n8n-node#6

Teach BI Generator a business filter directly in chat

A new Teach mode lets you define a business term, such as "active customers", in the SQL Builder chat. BI Generator checks the definition against your data before saving it, and you can undo it later.

Sources: BI_Generator#71, BI_Generator#72, BI_Generator#73

/publish-ready checks an app before you publish it

/publish-ready reports exactly what an older app needs before it can publish, applies straightforward fixes automatically, and can retrofit the rest — instead of hitting one publish failure at a time.

What to do: Run /publish-ready before publishing an older app.

Sources: priority-dev#268

Fixed cases where BI Generator gave wrong answers until manually refreshed

Some questions returned incorrect SQL because a knowledge update hadn't been fully applied yet. BI Generator now applies and orders knowledge updates correctly so this no longer happens on its own.

Sources: BI_Generator#67

SQL Builder asks before replacing your chart; bulk-delete chats added

A new question no longer silently replaces your current chart — the SQL Builder asks first. You can now delete several chats at once, and the default AI model moved to Gemini 3.8 Flash.

Sources: BI_Generator#65

SQL Builder keeps a version history of every query

Every query in a session — from chat, manual runs, applied criteria, templates or a Priority import — is now saved as a restorable version. A new History menu lets you go back to any earlier query.

Sources: BI_Generator#64

Choose and change your generated app's look

The new-app wizard now offers real look choices, including your saved brand, instead of one fixed default. Once an app exists, /restyle can re-theme it from a chosen look, your brand, a website URL, or a reference image, with one-step undo.

What to do: Run /restyle to re-theme an existing app.

Sources: priority-dev#261, priority-dev#263, priority-dev#264

Fewer interruptions while building an app

A preview session used to disconnect after 30 minutes with no explanation; it can now run up to 8 hours, and a disconnect tells you why. Reading Priority data while building no longer raises a separate approval card for every read.

Sources: priority-dev#257, priority-dev#259

Fixed contact sign-in failures on published portals

A published contact portal could reject a valid sign-in when the same email address is shared by more than one contact record, and could sign a contact in without properly scoping their data to their own company. Both are fixed.

Sources: priority-dev#254, priority-dev#255

Denied dashboard viewers can now be added with one click

Someone denied access to a shared dashboard link now sees their own email, so they can send it to you. The Share dialog lists recently-denied people, and you can grant access with one click.

Sources: BI_Generator#63

Publish contact, employee or no-login apps to Vercel

Apps built with a customer/supplier contact login, an employee login, or no sign-in at all can now be published to Vercel behind a secure server-side proxy, so the Priority connection key and token never reach the browser.

Sources: priority-dev#245

Fixed WINDBI-style data dumps on older Priority 23 servers

Data dumps used by Priority Console — Dev returned "entity not found" on Priority 23 servers even though the same entity worked in Priority's own dump tool. The gateway now sends the request in the shape Priority 23 expects, so dumps work there too.

Sources: WebSDKGateway#130

Priority Dev no longer misreports writes and rebuilds that actually succeeded

On slower servers, a long write could time out on the client while it actually finished on the server, and Priority Dev reported it as failed. Rebuilding a procedure (rebuild only applies to forms) is now refused with a clear message instead of silently doing nothing, and activation commands with unrecognized options are now refused instead of ignored.

Sources: WebSDKGateway#129, WebSDKGateway#135

Import a Priority report or procedure as your SQL Builder query

A new menu option seeds the SQL Builder with the logic of an existing Priority report or procedure, instead of asking the AI to rebuild it from scratch. Column headers and aliases from the import now come through correctly.

Sources: BI_Generator#61, BI_Generator#62

Chat composer supports multi-line messages; tab counts and paging fixed

The chat input in the SQL Builder and Home now grows for multi-line messages (Shift+Enter for a new line). The "planned N tabs" count now matches what you see, and results cut by Priority's output cap can be paged further.

Sources: BI_Generator#60

"Auto-approve this chat" — a one-conversation escape hatch

A new switch stops the assistant from asking for approval on almost every action for the rest of one conversation. Deletes, deployment writes and other destructive actions always still ask, even with the switch on.

What to do: Turn on "Auto-approve this chat" from the approval card menu when you want fewer prompts.

Sources: priority-dev#222, priority-dev#223

Truncation banner now explains Priority's output cap

When Priority silently limits how much data it returns, the SQL Builder's "results cut short" banner now says why, instead of leaving the reason unexplained.

Sources: BI_Generator#59

Settings page and company selection for generated apps

Generated apps can now include their own settings page, and a user can pick which Priority company to work with at login.

Sources: priority-dev#180

Fixed publish bugs: stale keys, wrong login mode, leaked secrets

Publishing an app could ship with an outdated connection key after you rotated it, could fail for apps built with "Priority user" sign-in, and could — in one case — ship the real connection key and token inside the public app bundle. All three are fixed.

Sources: priority-dev#177, priority-dev#241, priority-dev#244, priority-dev#249

Fixed connections that failed activation even though they worked

A slow or timed-out check on one channel could fail an entire Priority connection setup, even when the connection actually worked through the other channels the assistant uses. The activation check no longer fails the whole connection over that one channel.

Sources: WebSDKGateway#126

Fixed connections wrongly shown as failed

A slow or restricted check on one channel (OData) could mark a fully working Priority connection as failed, blocking activation even though the gateway answered every query. Connection status now reflects whether Priority is actually reachable.

Sources: priority-dev#172, priority-dev#174

Fewer, clearer approval prompts on the Dev route

Read-only verification queries were sometimes misclassified as writes and raised a card that could expire unanswered — genuine reads no longer card. The "approve all for this build" and "always approve" buttons on a card were also faint, hard-to-see text stuck in English; they now render as real, localized buttons.

Sources: priority-dev#169, priority-dev#221, priority-dev#198, priority-dev#214

Fixed Hebrew analytics questions that failed to find the right topic

Hebrew-phrased questions that used to come back as "ambiguous" and never reach the right business area (sales, purchasing, etc.) are now routed correctly.

Sources: BI_Generator#54

Test your Priority connection before submitting registration

The registration form now has a Test Connection button that checks your Priority server address and credentials before anything is saved, so you catch a mistake before onboarding starts. It also tells a wrong server address apart from a wrong password.

What to do: Use the Test Connection button on the registration form before submitting.

Sources: licensing#28, licensing#29

Fixed connection errors when reconnecting BI Generator to Priority

Reconnecting could fail with an authorization error and leave the connection stuck. Reconnect now refreshes an outdated key automatically, so the repair path always works.

Sources: BI_Generator#52, BI_Generator#53

Fixed a bug that could block Chat connections for every customer

A server-side origin check rejected the connection request Priority Console — Chat sends to link your Priority account, which then showed a licensing error to every customer regardless of their actual entitlement. The check is fixed, so connecting works as expected.

Sources: WebSDKGateway#125

Automation route: correct welcome screen and fewer approval prompts

A new Automation chat used to greet you with Chat's data-question examples instead of describing n8n workflow building, and routine n8n reads — listing credentials, checking a workflow reference — raised an approval card on every call. Both are fixed.

Sources: priority-dev#166, priority-dev#170

Fixed login failures for Priority Connect customers

New customers hosted on Priority Connect could not log in at all — the gateway was dialing an on-premise-shaped address that Priority Connect rejects. Logins now use the correct address, so onboarding on Priority Connect works.

Sources: WebSDKGateway#121

SQL Builder is now one screen, with saved queries always visible

The SQL Builder no longer opens on a separate landing page. Saved queries, the chat and results all live in one workspace, and a single actions menu replaces the previous button row.

Sources: BI_Generator#48, BI_Generator#49

Connection errors now explain the real reason, not a generic licensing message

A revoked or unregistered key used to show the same generic "not licensed" error as an actual licensing problem, sending troubleshooting in the wrong direction. The connect flow now names the real cause, so you know whether to reconnect, re-register, or contact support about licensing.

Sources: WebSDKGateway#119, WebSDKGateway#122

Redesigned pages and dark mode across BI Generator

Every screen in BI Generator now uses a consistent design, including the sign-in and error pages. A new dark mode toggle is available alongside the existing light theme.

Sources: BI_Generator#41, BI_Generator#45

Warning when removing an app that is still granted via a profile

Turning off a user's direct access to an app no longer looks like access was removed when a profile still grants it. The confirmation now names the profile and offers to remove that too.

Sources: licensing#24

Deep analysis mode: verified answers in the SQL Builder

A new Deep analysis option in the SQL Builder checks the generated SQL against your live Priority data before answering, shows a live progress trace of what it checked, and asks a clarifying question when your request is ambiguous. Direct mode still works the same as before.

What to do: Turn on Deep analysis in the SQL Builder's mode selector when you need a verified answer.

Sources: BI_Generator#43, BI_Generator#44, BI_Generator#46, BI_Generator#50

Fixed incorrect large numbers in sum and total calculations

Sums and totals over certain quantity and balance columns (like stock balances) could display a value 1000x too large because of how Priority truncates long column headers. Totals are now computed from the right column type, showing the correct figure.

Sources: WebSDKGateway#117

Simpler user management menu in the customer portal

Actions for each user on the Users tab — Welcome, Resend invite, Make/Remove admin, Remove — are now grouped under one menu instead of four separate buttons on every row.

Sources: licensing#14

Onboarding now grants your contact person access automatically

Approving a registration no longer requires choosing an application first; it is created automatically on the first grant. The email address used to register is automatically added as a user, so that person has access without an extra step.

Sources: licensing#15

Fixed crash when selecting certain AI models in BI Generator

Picking opus-5 or gpt-5.6 in the model selector used to fail every query. BI Generator now retries automatically so these models work.

Sources: BI_Generator#38

Long build turns no longer lose your work or your reply

A turn that hit a provider slowdown, a stall, a page reload or a reconnect could die silently, leaving a blank reply or forcing you to type "continue". Turns now keep running through a reload, retry transient provider errors automatically, show a friendly message during provider slowdowns, and never disappear without a visible result.

Sources: priority-dev#138, priority-dev#139, priority-dev#143, priority-dev#144, priority-dev#233, priority-dev#262, priority-dev#288, priority-dev#295

Large query results no longer get silently cut off

Priority's own SQL service caps how much text it returns per call and used to cut results mid-line with no warning, so a query could quietly return fewer rows than actually match. The gateway now detects the cut and automatically continues past it, and any still-capped result is reported as truncated instead of hidden.

Sources: WebSDKGateway#113, WebSDKGateway#127

Priority Dev now rejects source lines Priority would silently truncate

The underlying writer previously let long lines of generated code save, and Priority cut them at 68 characters without any error, causing bugs that surfaced much later. Long lines are now rejected up front, with a clear error at write time.

Sources: WebSDKGateway#112

"Auto-approve safe build steps" now covers more of a build

The persistent auto-approve switch for build steps on the Dev route is easier to find, and now also covers database structure changes, form/menu rebuilds and warning confirmations that used to raise a card every time regardless of the switch. The same kind of switch is now available for App Generator's toolchain calls too.

What to do: Find the auto-approve switch in Settings or on a build-safe approval card.

Sources: priority-dev#130

More consistent and accurate answers in the SQL Builder

The same question now returns the same correct SQL every time, and follow-ups like "add a column" find the actual column you asked for instead of a similar-looking one. Several join and matching bugs behind wrong or inconsistent results in the SQL Builder chat are fixed.

Sources: BI_Generator#26, BI_Generator#27, BI_Generator#28, BI_Generator#29, BI_Generator#30, BI_Generator#31, BI_Generator#32, BI_Generator#34, BI_Generator#35, BI_Generator#36, BI_Generator#37, BI_Generator#40

More accurate field and table lookups when discovering your Priority data

Field discovery now uses Priority's own dictionary instead of guessing from table presence, so the source table and column reported for a field is always correct. A new lookup can resolve a single field's real source directly.

Sources: WebSDKGateway#109

Fixed repeated connection drops caused by a memory leak

A network connection leak could crash the gateway and cause repeated disconnects during heavy use. It's fixed, so sessions stay stable.

Sources: WebSDKGateway#110

Chat and BI answers over your Priority data are more accurate and faster

Several bugs that produced slow, incomplete or wrong answers are fixed: over-sized results that got cut before reaching the assistant, tables picked for the wrong reason, Hebrew column names not matching, and quantities shown 1000x too large. Answers to questions about your Priority data are now more reliable.

Sources: WebSDKGateway#107, WebSDKGateway#108, WebSDKGateway#111, WebSDKGateway#114, WebSDKGateway#128

Smoother streamed replies in Chat

Answers now stream into the chat window smoothly instead of visibly pasting in bursts, and the view reliably stays scrolled to the newest text while an answer is still arriving.

Sources: priority-dev#122, priority-dev#123

SQL query errors caught before they reach Priority, with clearer messages

Common SQL syntax mistakes (wrong join style, TOP/LIMIT, missing table alias, and more) are now flagged immediately with a clear explanation, instead of being sent to Priority and returning a cryptic error. Unresolved column names now come back with suggested matches.

Sources: WebSDKGateway#104

SQL Builder now accepts AS column aliases and COUNT(DISTINCT)

Queries using AS to name a result column, or COUNT(DISTINCT column), now run correctly instead of failing to parse.

Sources: BI_Generator#24

Fixed chat turns stuck on "Working…" forever

Some turns on the Chat route could show "Working…" with the token counter stuck at zero and never produce an answer. This hang is fixed.

Sources: priority-dev#120

Start a Chat conversation without picking a project

"New chat" on the Chat route now opens right away — you no longer need to choose a project first. You can still file the chat under a project later. Dev and App Generator still require a project up front.

Sources: priority-dev#119

Project plan documents shared across every chat in a project

A project can now hold named documents — a spec, an app description — that the assistant reads and updates on both the Dev and App Generator routes, so decisions survive across chats.

What to do: Open the paperclip icon on a project row to view or create a document.

Sources: priority-dev#110, priority-dev#111, priority-dev#113

Connection setup is more reliable in longer sessions and shared logins

The Add-connection dialog could lose its list of Priority servers after about an hour, and two people sharing one Priority login could keep disconnecting each other's connections on reconnect. Both are fixed.

Sources: priority-dev#105, priority-dev#106

BI Generator understands credit/debit invoices and production reporting

Questions about sales, purchasing and production reporting now correctly account for invoice credit/debit rows, who logged production work, and status flags, instead of misreading them.

Sources: BI_Generator#22

Data actions now run and are checked under your own Priority identity

Some connector logins used the tenant's shared master identity for OData, which could return wrong data or fail to log in. Queries and actions from Chat, generated apps and connected tools now run and are checked against the actual signed-in Priority user's own permissions.

Sources: WebSDKGateway#96, WebSDKGateway#97, WebSDKGateway#98, WebSDKGateway#99

Fixed silent write failures in procedure and trigger text

Writes containing quoted text with apostrophes could fail to save without any error being shown. The tool now escapes text correctly and verifies every write by reading it back, so a reported success is always a real one.

Sources: WebSDKGateway#93

Attach CSV files in Chat

You can now attach .csv files to a message in the Chat route, joining the markdown, text, JSON and PDF files already supported.

Sources: priority-dev#93

App Generator's preview connection no longer gets stuck

The local preview panel could sit on a stale "connecting" screen even after your executor was ready. This is fixed — the panel now correctly shows a connected executor.

Sources: priority-dev#88