Skip to main content

Release notes

This page records what changes for people who build, publish, and operate agents. Internal changes that do not alter what you see or do are not listed here.

September 2026​

Imaginne operates the product by conversation. Describing what you want became a first-class path: it creates the agent, adds steps, points at connections, tests, publishes and turns on the trigger. The /agent terminal and the editor dock are the same conversation — switching screens does not restart the subject. See Building by conversation.

Investigating an API without using your flow as scratch paper. Discovering the shape of a response no longer requires building, running and undoing steps in the agent you were working on.

The same call, delivered again, does not run again. A repeated delivery no longer becomes a second execution.

The conversation runs the agent that is live. Asking it to execute now triggers the environment's active version, not the draft open on screen.

"Before X, do Y" became a single gesture. Inserting a step between two that are already wired rewires the edges and preserves the branch labels, without unplugging and replugging by hand.

A dropped turn comes back on its own. When the model's transport dies in the middle of a long inference, the turn is resumed automatically, up to twice, without redoing what was already applied.

August 2026​

Connections. Server and credential are now registered once, under a name of their own, in the types http, postgres, smtp, ssh and s3. Steps point at the connection by name, the secret stays in the vault and does not show up again — not in the edit screen, not in the published definition. The Test button opens the real connection. See Connections.

System components. Send email (SMTP), Query a database, Write to a database, Run over SSH, SFTP, S3-compatible storage and CSV. Files travel between steps in a single shape, so they chain without glue. See System components.

Reading and writing a database are separate components. The query starts in a read-only transaction; the write is its own component. Whoever reads the flow sees where it alters data, and the space can enable one without enabling the other.

Import cURL and OpenAPI. Paste a curl, or point at an OpenAPI 3.x document, and the HTTP step is born configured. A credential present in the command becomes a secret or is left out — never text in the flow.

Command palette, Explore and favourites. Cmd/Ctrl + K jumps to any agent, space or action; the example gallery really creates one with a click; and a starred agent stays within reach.

Save as template. A finished agent becomes a template — yours or the organization's — with the variable parts marked to become setup questions.

Re-editable schedules. Changing the cadence no longer requires recreating the trigger, and the screen shows the upcoming runs.

The step test pins the data by itself. A successful test now feeds the data picker with the real fields of that response, including nested ones. Renaming a step does not break references.

Insert in the middle, from the canvas. A "+" button on the connections adds a step between two, rewiring and preserving the exit label.

The organization's skills available in AI tasks. A skill published by the organization is now present in the environment where the task runs. Previously, the AI was instructed to use a skill that did not exist where it was running, and the failure arrived as though the tool did not exist.

The "Run an automation" step. It runs a published automation — a program with declared inputs and outputs, deterministic and without AI. It is the right path when the task has to be identical every time.

Tool recovery no longer fails the step. A tool that fails and is run again successfully no longer makes the whole step fail.

Triggers follow the active version. A schedule runs correctly again when the environment's active version changes.

July 2026​

Five control steps, with durable waiting. Wait, Choose a path, Handle error, Combine results, and For each item. All durable: a run that waits releases resources and comes back on its own.

Simple mode as the default. Linear flows are built as a numbered list, with automatic connections and the Result step created alongside. When the flow gains parallel branches, the list refuses to show it and takes you to the visual editor, changing nothing.

Per-step testing. A step can be tested on its own, with pinned data in place of what would come from earlier steps — including in an incomplete draft. It is a real run, with its own rate limit.

The "Generate with a model" step. It sends text to a model and receives the answer, with no tools. It does not retry on its own: an ambiguous answer may already have been billed.

A configuration contract for actions. Publishing an HTTP call with no address, with an invented method, or with a value that looks like a credential is now refused at publishing time — previously that became an immutable version and only failed on its first run.

Schedules with checked input data. The data is validated at creation, against the version it points to. A data failure no longer disables the schedule on its own: it stays visible and waits to be corrected.

A stable step panel. Adding a field no longer sends the panel back to the top, and focus, values, and open sections are preserved.

Resources chosen by name. Tools and skills are now selected from a list, with each one's real state — available, not allowed, unavailable, or not confirmed.

Next steps​