FabricLoom starts when a cartridge is installed from more than one registry. It used to stop at launch.
The startup window is drawn while the engine starts. It used to stay blank on macOS 27.
A view that cannot be shown is reported in its place, with what failed and a way to reload it, and the rest of the app keeps running. The app used to quit.
The engine starts without waiting on the network. The app checks for updates itself, so the Enable version checking setting is gone.
If the engine stops, the app starts it again, on Linux and Windows as on macOS. Only several crashes in quick succession ask you to Retry or Quit, and an engine started again comes back ready as it does at launch.
On macOS the status bar shows the engine as ready when it is. It used to show it as down whatever its state.
When the engine cannot start, for example because its data cannot be read, the app asks what to do in the same way on every platform, and clears the data only if you choose to.
A setting with an empty value, such as a text option that defaults to nothing, is shown on the settings page. It used to close the window.
Runs
A run no longer waits for ever when its cartridge stops answering. The cartridge is stopped and the run fails, saying why.
A run’s progress is its share of the whole run, and never goes backwards.
On Linux and Windows a finished run appears in the list at once. It could be missing for several seconds.
On macOS the lists, and the progress of a running machine, stay current while another app is in front.
On Linux and Windows, when something asked of a machine or a run cannot be done, the app says so. The message used to be drawn where it could not be seen.
A machine’s inputs and outputs have names. Running a machine on macOS asks for each input’s files separately, and files are bound to inputs by name, or to the input they fit best; a file that fits two inputs equally well is refused, naming both.
A run is shown as the plan it ran, on macOS as on Linux and Windows: each input’s sources and each output’s files, the steps that were skipped, retried, or failed without stopping the run, and the outputs it did not produce. A run that completed despite such failures says so.
A run starts with the plan it showed you. Running a run again, with or without changed arguments, binds its files to the same inputs and delivers its outputs beside the files it was made from.
A run’s outputs are listed in the order of the items that produced them, not the order in which they finished.
Each item a run processed separately, such as each page of a document, shows its own preview. On macOS, a preview that cannot be fetched says so.
An output a failed or stopped run never delivered reads as nothing produced, not as nothing yet.
Each profile keeps its own runs, beside the database that records them. Clearing a database the app cannot read clears its runs too, so outputs of other runs are no longer reported as missing.
On Linux and Windows, every run a machine makes exports its outputs. On every platform, exported outputs land in a folder named after the output.
The machine editor
A blank machine opens in the editor and is built there step by step: steps are added, connected, connected differently, and undone.
On Linux and Windows the editor fills its window. It used to open two pixels wide.
Opening a different machine shows that machine.
A new machine stays open once machines have been run.
On macOS a machine document opens from its file whether it is complete, half-written or empty.
A machine written with every step and value named has each of its steps typed from its capabilities, and a step that runs once per item is marked as such.
On macOS, a machine opened while another is being edited gets an editor of its own.
Adding a model, choosing a path
Closing Add Model, or the wizard that chooses a path, while it is still searching no longer breaks the next search.
On Linux and Windows the wizard offers every path there is. Opened while the app was busy it could offer one, three or a handful of them and call the list complete.
Capabilities and cartridges
The capability pages name every argument and list every output, the main one first, on every platform. A capability that takes no input is shown as taking nothing.
Capabilities show the dimensions each was built from, with their documentation. The fabric browser lays definitions out along axes, colour, shape, size and a grid, and each filter can show, hide or grey out a definition.
The app follows fabric manifest 12. Text written to be read is plain text, and the capabilities that read text as language (summarizing, classifying, embedding, prompting a model) take it. A yes-or-no value is its own type, and model information, embeddings and transcripts are JSON records.
Cartridges made for an earlier release must be updated: one built for the previous protocol is refused when it starts.
New: market and economic data. Quotes and live quote streams; economic and market series from named sources; SEC filings and company facts; identifier and LEI lookup; and analyses over series, from resampling and rolling statistics to returns, benchmarks and scored forecasts. The SEC asks every client to name a contact: filings and company facts take it as a setting, and ask nothing of EDGAR until it is set.
Offline
The network setting reaches every cartridge. Offline refuses each request a cartridge would make (model downloads, registry lookups, market and economic data), and the refusal names the setting. A change takes effect at once, and a download in progress stops.
With telemetry off, only analytics and crash reports are refused.
While offline, the app does not check cartridge registries. It marks each one offline and checks again as soon as the setting changes.
Registries and models
The registry manager on Linux and Windows lists its registries at once, each pending until its own check is back. Adding or removing one updates the list in place. It used to wait for every check and blank the list after each change.
An address that answers with something other than a registry is reported as unreadable.
On macOS, the cartridges page checks every registry it lists.
A Hugging Face model that cannot be seen without a token is reported as missing or private. It used to be reported as needing authentication.