What's new

What changes in Kedalia, the most recent first.

On this page

2026-10-17

  • “Publish” no longer takes you away from the conversation. The window stays open on “Publishing…”, then the test version's conversation stays on screen, read-only, and follows the live app's update.
  • A published test version reopens: “Reopen the conversation” in its conversation, “Reopen” on its row in “Applications” or on its Kanban card. It is recreated from the live app, and the conversation carries on with the assistant where it had stopped.
  • “Publish” is also on a test version's row, in “Applications”. Once published, its “AI assistant” button opens its conversation again, read-only.

2026-10-15

  • Kanban: “Ask for a change” leaves the cards. Drag the card into “Queued”, or write the change in its conversation, then “Apply as a correction”.
  • Kanban: a card dragged from “To approve” into “In discussion” opens its conversation, to talk it over with the assistant. A new plan brings it back there.
  • The preview opens already signed in, with its administrator test account, and a test version lets you in with “Sign in with Kedalia”: each member of the organisation gets an administrator account in their own name there. The sign-in details fold under a “Sign-in details” button. For applications created from today.
  • Board cards no longer show their test version's sign-in details: they are at the top of its conversation. A “Kanban” button, at the top of the page beside the application's name, replaces the “Back to the board” link.
  • On the Applications page, a test version shows its title once, then its address before “Up”.
  • After you send a message, a long conversation goes down to “The assistant is working…”: you had to scroll to see it.
  • In a test version, the username and password sit beside its address, at the top of the conversation. In the preview, they move to the left of the buttons; “Reload” and “Open in a tab” become icons there, named when you hover them.
  • A greyed-out “Publish” tells why when you hover it, instead of a line under the buttons. A card with no description no longer shows “Add a description”: the pencil beside “Description” adds one.
  • “Try a change” is now “Create a test version”. In the live app's conversation, the button now sits at the top, beside its name and “Preview”.

2026-10-14

  • Kanban: the “To clarify” column is now called “In discussion”: that is where you clarify the request with the assistant, then approve its plan.

2026-10-13

  • The terms of sale and the data processing agreement are online, each on its own page, with a table of contents. The sign-up page recalls them under its button.
  • The legal information reads like the help: a table of contents, airier sections, and tables that scroll on a phone.
  • After 10 wrong passwords in 15 minutes on an address, password sign-in on that address waits 15 minutes, and the message says so. An address receives no more than 3 “forgot password” links an hour.

2026-10-12

  • An application's address, next to its name, is now in colour, followed by an arrow: a click opens it in a new tab.
  • The “Assistant usage” gauge now sits under the conversation's message box, where a message spends it.
  • “Point” puts a label into your message, where the cursor was: write what should change right after it, and point at several elements in one message. The label cannot be edited, its cross removes it, and the conversation shows it as is.
  • Publishing a card the live app has moved past: Kedalia first adds the live app's changes to the card, and renumbers the card's database changes above its own. When both changed the same files, the assistant combines the two versions instead of an error message: check the result in the “Preview”, then publish again.
  • Kanban: “Undo start”: a card in “In discussion” started by mistake becomes a ticket again, at the top of “Backlog”. Its test version and its conversation are deleted; “Discuss with the assistant” opens a new one.
  • “Point” on an image calls it “Image”, with its description or its file name, even when a layer covers it or when it is a background: no more nameless “Element”.
  • A card kept in one of your team's columns takes a place among its tickets: drag it above or below one of them to prioritise it. A new card arrives at the top of "In discussion".
  • In a ticket's window, the “Start” button is now called “Discuss with the assistant”: it turns the ticket into a card, and the assistant reads it as soon as its test version is ready.
  • While the assistant works, the waiting line says what it is doing when nothing else moves on screen: "The assistant is reading the application's code…", or, during the plan, "The assistant is preparing the technical part of the plan…".
  • The address of an application that does not exist, or no longer does, opens a page that says so instead of a technical error: a deleted or renamed application, or a typo.
  • Two database changes at the same time: when a card delivers first, Kedalia renumbers the other conversation's change itself and delivers it; that conversation's preview starts over with fresh test data.
  • Checks that could not run because of an incident on our servers are run again once by themselves, and no longer offer to fix an application that has nothing wrong.

2026-10-11

  • A card and the app's conversation at the same time: when both change the database, the one that delivers second no longer loses its work: Kedalia renumbers its change and delivers it. Each also checks the app in its own browser, without disturbing the other.
  • A card's conversation on a laptop always keeps room for several messages: the page scrolls when the description and the credentials take up the screen's height.
  • What Kedalia refuses stays typed: the name of a new app, a colleague's invitation and the display name are no longer wiped after a refusal; just correct them.

2026-10-08

  • The help assistant follows you everywhere: the round button at the bottom right of every page opens and closes it; the conversation stays when you change pages. It leaves the bottom of the help pages.
  • Kanban: the card keeps its description: once a ticket is started, its description stays at the top of the card's conversation, apart from the exchanges with the assistant. The pencil keeps it up to date, and the assistant reads the new version with your next message or your next plan request.

2026-10-07

  • A question? Ask the assistant: at the bottom of every help page, the assistant answers from these pages. The "fast" intelligence level also moves to a newer model, more capable for the same use.
  • Display name: the pencil on an application's card, in “Applications”, sets the name its emails (welcome, forgotten password…) go out under.
  • “Request the plan” takes your last detail along: what is written in the message box goes with the request, no need to send it first.
  • “Point”: the line added to your message names the page in plain words, for example “home page”.
  • The assistant's progress lines are written in your language and in your words, throughout the build.
  • Signing up with Google: the account takes the language of the page you sign up from.
  • Help is here: these pages explain Kedalia in the words on your screen, and are kept up to date with every change you will notice.