Airbuild 1.4: two projects at once, and models that pace themselves

Version 1.3 was about work that does not stop when something runs out. Version 1.4 is about work that does not stop because something else is already running — and about the model doing the work being the right size for the step in front of it.

You can build in two projects at once

A running turn used to block every other project in your account. A message in a second chat came back with “Another AI turn is already running for your account” until the first one had finished — half an hour, on a long turn.

The lock belongs to the project, not to you. Two projects, two turns, at the same time.

Three models move up

Claude Opus 5.5 takes the place of Opus 5, and GPT-6 Sol and GPT-6 Luna take the place of the 5.6 pair. Sol costs less and answers faster than the model it replaces, and its rating in the picker says so.

GPT-5.6 was also running with its reasoning switched off. Turns ended in the middle of the work — a short wrap-up with steps of the plan still open and no error card to explain it. On the interface the model was called through it cannot use tools and reason at the same time; it now runs on one where it can.

The Claude 5 models decide for themselves how long to think

Fable 5, Opus 5 and Sonnet 5 can vary their own thinking from step to step. Their effort control now offers Adaptive and starts there, so a simple step stays cheap and a hard one gets the room it needs — instead of everything running at one setting you picked once and forgot.

Attachments reach the model you picked

Three ways an attachment could be lost on the way. Images were dropped entirely on Gemini — the model was handed the words “[Image attached]” in place of the picture and answered about things it had never seen.

A screen recording could be uploaded, stored and shipped in your app, but not watched: reading it fell through to the text reader, which answered “cannot read file” and spent a whole iteration saying nothing. The assistant watches it now. And a video is recognised as a video even when the browser reports nothing about the file, so it takes the right size limit and shows a thumbnail instead of a broken-media icon.

Design Mode takes attachments too — the paperclip, drag and drop, paste from the clipboard, with a pasted screenshot named by its timestamp.

The workspace speaks your language everywhere

Whole areas were hardcoded English, and in a few places hardcoded German, so one panel could mix both whatever your setting said. The chat and every tool card, the publish and deployment flow, the log viewer: all of it follows the language you chose.

Organisations, tidied up

Opening an organisation now requires a Suite Builder plan of your own — which means your own seat is already paid for, so only the members you add are charged.

A budget could be created and deleted and nothing in between, so correcting a limit meant deleting it and losing the usage counted against it. Name, monthly limit, alert threshold and whether it blocks or only warns can all be changed now. And the trash icon in the members table does what it says, instead of being offered even for the sole owner, who cannot be removed at all.

The name has reached the addresses

The website and the workspace answer on airbuild.ai, and the previous addresses redirect there. A session you had open kept working across the change. The company behind Airbuild is registered as Airbuild FlexCo — the imprint, the terms, the data processing agreement and the privacy page carry the new name; the address and everything else about the entity are unchanged.

Everything else

The full release notes live on the Version 1.4 page.

• A new start page, built around business software a team runs on rather than a prototype to throw away.
• A prompt typed on the website before signing up now opens the build, instead of landing you in front of an empty composer.
• A shared link shows the wordmark on a light grey ground — not the homepage hero.
• The contact and sign-up pages arrive complete instead of as an empty document that needs JavaScript.
• A frontend-only publish no longer waits on an endpoint check that has nothing to look at.
• The publish bar keeps moving: progress is reported from the new build path instead of sitting at 10 %.
• One question at a time before a publish, so two dialogs cannot stand on screen at once.
• Links to a published site keep everything after the question mark when they are sent to the canonical address.
• Published apps can run their migrations again — the statement that creates their schema no longer reads as an injection risk.