Changelog

Loomi

• Loomi can speak in a cloud voice on your own OpenAI or ElevenLabs key, priced where you turn it on. The local voice stays default and free.
• She starts talking at the end of her first sentence, while the rest of the answer is still arriving.
• Plain field commands like "clear the field" or "focus Cole" are acted on straight away, with no model in the loop.

Fields

• Every field says what is happening on it: somebody needs you, somebody finished, somebody is working. You see it without switching.

Looms

• A loom whose turn was cut short is told what it left half-finished, so its next turn picks up instead of starting blind.

Agents

• Resuming a Codex loom puts back the model, the effort setting and the permissions it was running on.

Usage

• The Claude bars read the limit each turn reports back, so they move while you work instead of waiting on a shared account endpoint.
• The usage page keeps plans and keys apart, names who bills each one, and totals what your keys have spent.

Looms

• A turn that dies of a server error or a dropped connection waits and tries again for up to fifteen minutes, instead of settling as failed.
• Resuming a claude loom no longer settles the work you just handed it as finished a moment after it starts.
• Closing a loom somebody was waiting on tells the waiter it is gone, rather than leaving them waiting for a result that never comes.

Loomi

• Volume and speed are remembered for each voice, not shared across all of them.

Usage

• A refused usage reading keeps its age on screen, "as of 91m ago", instead of drawing a stale bar as if it were current.
• A long company or product name in the usage ledger is no longer cut off inside a narrow column.

Providers

• The design consent toggle works after a design sign-in; it was sending the wrong credential and being refused every time.

Needs

• Your agents hit doors you have the keys to. Now they say so in one place, instead of stopping to ask in a chat you are not reading.
• The pane is *What we need from you*. Paste a key into the row, press *Do it* to send a browser loom after it, or *Done* when it is yours.
• A key you hand over goes to the vault and to the project that asked. It never reaches a transcript, a loom or a log.
• A need outlives whoever filed it. It moves to whoever is on the work now, and they are told what it is.
• A key you sealed into a project can be taken back out.

Looms

• Ask an agent for a file and it hands you one: a local text file lands on the field, to read, copy, reload or open in Explorer.
• What you copy from it never goes back to the agent. That is how you pass on a key it must not hold.

Providers

• Every agent CLI now says which build you are running, beside its name.
• When a newer one is published the row offers Update, and a corner notice tells you when you are not in Settings.
• Update runs the vendor's own command in a Terminal loom you can watch. It clears itself when it finishes cleanly, and stays put if it fails.

Looms

• A browser loom keeps its page when you move to another field. The agent carries on, and coming back picks up the live page, not a reload.
• A signed-in session and anything typed into it survive the trip.

Loomi

• Loomi leaves far less dead air between phrases. The wait before she starts is a third of what it was, and total silence is down by a third.

Design

• The design pair drives Claude Design itself, reading the repo you attached and typing into the same chat you can type into.
• Starting one no longer waits on a consent step, so the pair is always there to summon.

Agents

• Model menus name the model instead of printing its id, and the one you chose wears the plate rather than a word.

Needs

• An agent could be handed an out of date key with no way to withdraw it, which made Claude Code fail every turn with "Invalid API key".

Looms

• A browser page froze in place mid window while a field slid past it, instead of travelling with the field.
• Screenshotting a browser loom that was not on screen timed out and was refused.
• Showing a page again could land on the wrong loom when two of them were on the same address.
• A question a loom asked you could be deleted before you saw it, if a report on a different job arrived first.

Providers

• Every provider read "no key set" when the vault would not open. It now says what is wrong, and offers a reset only where one helps.
• A model released since you last opened a picker could stay invisible until you opened the menu twice.

Agents

• One internal error could refuse every new agent, break Resume and hide the halted banner until you restarted the app.

Usage

• Usage readings asked for numbers often enough to trip the provider's own rate limit, which left rows blank.
• They are read less often now, a provider asking to be left alone is obeyed, and the last good reading stays up instead of the row emptying.
• Spend on Sonnet 5 was costed at the older family price, so it read higher than it was.

Agents

• Ask for an agent without naming a provider and it goes to one with usage left. A spent provider is passed over, and the loom's note says so.
• Asking for a provider by name while its window is spent is refused in a sentence that names the provider and says another can take the work.

Agents

• Running out of usage on one provider refused every new agent on every provider, restart or not, until that window reset.
• A spend limit you typed into Settings was read as the provider's own wall, so reaching it could refuse agents twice and blame the provider.

Looms

• A browser loom showing a file on your machine reloads when that file changes.
• A report an agent keeps rewriting stays current in front of you, with nothing to press.

Loomi

• She reads the sign-in step aloud while you set her up, so every page of onboarding is spoken rather than only most of them.

Looms

• Drag a loom by its plate, not only its header. The padding, the gaps and the whole side margin are fair game now.
• A browser loom's band is two rows: the window above, the page below. The controls are the same ones, in clearer company.
• Branches are a plain line again by default: a woven wire animates on every relationship whether or not anything is crossing it.
• Woven is now something you switch on rather than something you are handed.
• Appearance carries the Branch wires setting, and it holds whichever you pick.

Fields

• A row in What they made can be forgotten. It drops the pointer and never touches the document.

Looms

• Zooming a browser loom well out could flash a huge copy of the page across the loom before it settled.
• An agent working on a field you were not looking at could file its document, its saved row and its recruits against the wrong field.

Looms

• Drop a folder, or a .zip, onto the field and it stays there as a loom of its own.
• A folder loom hands itself to an agent, joins the wants list, copies its path, or opens in Explorer.
• Closing a folder loom takes the loom off the field and leaves the folder alone.

Fields

• A new pane, What they made, holds the reports, pages and figures your agents produced.
• Open any of them again long after the loom that made it has gone.

Looms

• Branches between looms are woven fibre now, and a message crossing one shows as light travelling through the strands.
• Appearance carries a Branch wires setting if you would rather have the plain line.
• Handing something over takes folders as well as images, so a folder and a screenshot go the same way.
• Resize handles come up when you hover a loom, not only when you have selected it.

Fields

• ⌘K opens and closes the panes, the same rows View ▾ carries.

Documents

• Circle a region that is not text, a diagram or an image, and note it the way you note a line.
• A report wears the scene you are in, and changes with it while you are reading.

Scenes

• Three more scenes: Abyss Coast, Lavender Dusk and Vermilion Coast, made in Wispfield's own image maker.
• The tray runs the light scenes first, then the dark ones.

Agents

• Choosing which model draws your images has moved to Agents. The list still fills in when your key cannot reach the provider to ask.

Looms

• A report on a narrow loom ran off its right edge, taking the comments gutter and your notes with it. It fits the loom now.
• A report's scrollbar never painted, so nothing showed how far down the page you were.
• A page in front of Loomi covered the box you were typing into, swallowing the words and the clicks.
• Zooming a browser loom could flash the previous page at the wrong size for a few frames.
• A pane or a menu sliding open showed the field through the space it had just left.
• The grab handle for resizing sat slightly off the corner of a loom rather than on it.

Agents

• An instruction turned away because a loom's queue was full reported that loom as failed, naming an agent that never saw it.

Fields

• A scheduled run closed Wispfield when it finished, which could shut the window from under you if you had started working in it.

Settings

• A dropdown near the bottom of a settings panel was cut off instead of opening upward.

Fields

• A loom you send to a field you are not looking at starts work there straight away, and is already underway when you switch over to it.

Documents

• Mark up a document a loom shows you. Highlight a line, circle a region, or note the whole thing, and say what the build should do.
• Your notes stay with the document and travel into the brief, so whoever builds from it reads them.

Images

• Choose which model draws your images. Every option carries its own rate, so what you are picking and what it costs sit in the same place.

Looms

• A browser loom's page keeps pace with its loom as you drag the field, and zooming in magnifies the page crisply rather than reflowing it.
• A browser loom carries a loading bar, so you can see how far a page has got.
• A loom in front of a page covers it along its own rounded corners, and the toolbar's menus and the panes stay above it.

Agents

• Model pickers read as names, so you choose Opus 5 rather than the version string a command line wants.

Wants

• A document waiting on your verdict stays on its loom's bar and off the wants list, so the list holds only what you have decided.

Fields

• The field could freeze if the window changed focus while a key was held down, leaving Wispfield unresponsive with agents still running.

Fields

• A loom working in one field can hand work to another. It arrives as a parcel, and nobody picks it up until you approve it.

Looms

• A native window that one of your looms opens can join the field as a loom of its own, carrying that window's facts and a photograph of it.

Reports

• Send a report when something goes wrong, from About, from the command bar, or from a loom that faulted.
• Your home folder, your workspace paths and the front of your keys never leave as themselves.

Fields

• Panes snap as you drag them, so two of them side by side line up without fiddling.

Looms

• A browser loom wears the name of the page it is showing, so you can ask Loomi to close it by name.

Loomi

• What she said is still there when you come back. Close Wispfield and reopen it, and the Said pane still answers "where was I".

Scenes

• Dialogs and panels take their color from the scene you are in, rather than the one fixed green they wore in every scene.

Settings

• About can show you the license key on this machine. It stays masked until you press Show.

Looms

• With a browser loom open, a field screenshot and Reveal could not find the main window.

License

• When a trial ran out, keyboard shortcuts still worked behind the lock screen, so the field could still be driven from it.

Settings

• The settings window closes on the first Esc. It used to take a second press once the control you

Panes

• Esc puts away a pane only when that pane is the last thing you clicked, so closing a window with
• Panes stay on the side until you remove one. A pane that raised itself while you were away is no

Security

• Saved API keys are wiped from memory the moment Wispfield is finished with them, so a crash dump

Welcome

• The last step of first run says what the folder is for: a new or existing project folder, not a

License

• Wispfield runs on a license key, and one key covers three machines. Release one you no longer
• A new machine starts with a seven day trial. Every feature is on, and it asks for no card and no
• A quiet mark in the corner counts the trial down while it runs, and turns urgent for the last two
• Keys are short enough to read down the phone, like WF-7K4QP-2WJXR-9BTNQ. A mistyped one is
• When the trial ends, Wispfield asks for a key and shows you the folder each of your fields is
• If your license cannot be re-checked because you are offline, everything keeps working and

Updates

• This is the last build you install by hand. Wispfield looks for a newer one when it opens and
• Press once to put it away, twice to install. It downloads, checks the release really came from
• You decide when. Nothing installs on its own, and if looms are mid-task it says how many and asks
• Settings, About carries the same offer, alongside the version you are on and when it last looked.

Jobs

• *What runs itself* is a new pane. Hand a loom a prompt and a cadence, and it does that work
• A daily job runs even when Wispfield is closed: Windows opens it, the work happens, and it puts
• The pane tells you which of the two a job is, so you are never promised more than is true.
• Every run is kept, with what it did and how long it took, and a job that fails says why rather
• Your agents can book work in too, and see what is already on the schedule.

Fields

• A fresh field opens with Loomi teaching it, one quest at a time and out loud. There is no panel
• It is the shape of every job here: bring an agent in, ask about the weather, turn its loom over
• Every quest finishes when the work actually happens, never because you pressed something that

Loomi

• She greets you as the field appears. Her first line could take twenty seconds on a cold machine,

Fields

• The top left corner names the field you are on, and stays there. Nothing else on screen told you
• An idle field costs about a third less CPU, so a Wispfield left open is quieter on the fan and

Panes

• A pane stays where you put it. Dragging one used to push its neighbor and move the edge at half
• Two panes aimed at the same place no longer stack into unreadable glass.

Wants

• The list belongs to the field you have open, because a want is about a project rather than about

Looms

• The opening screen no longer covers a browser loom that was already on the field.
• A burn survives a relaunch instead of starting over.

Cast

• Your looms have always had faces. Now they have a cast, and it is yours to run: bring someone new
• Whole crews arrive as packs you can swap between, and each pack tells you how many looms are
• Put the cast in the order you want, by dragging a portrait or with Ctrl+←/→. That order is the
• The crew that ships with Wispfield can be duplicated, so you can start from it rather than from

Scenes

• A scene is where the work happens: the photograph behind your field and every color on top of
• Name it, keep it, throw it out. The scenes that came with Wispfield stay where they are.
• Make a scene and an agent gets straight to work on its colors, then tells you whether it improved

Images

• There is a loom that draws. Tell it what you want and it makes the image.
• It is how the two above get made: a sheet of new faces for the cast, or a single image to become
• Ask for six faces and six come back on one sheet, named, so you can keep who you like and pass on
• Drawing costs real money, so the loom says which model it is about to use, and you can stop a run
• If the model turns a request down, it says so and hands your words back, so you can change them

Wants

• A Wants pane holds the list of what you want built, with a burn-down beside it.
• Press a picker for a priority and a category, or keep typing p0 if that is quicker.

Agents

• When someone writes up a chart, a diagram or a stat block, their page draws it properly instead of
• Bar, line and pie charts, mermaid diagrams, hand-drawn SVG, stat tiles and callouts all arrive as

Usage

• A pace mark says where a quota should be for this point in its window. 29% used with four days

Providers

• Codex and Kimi report alongside Claude and Antigravity, so there are four kinds of worker you can
• Each one brings its own model and effort setting, and a row tells you what it inherited.
• Codex's meter reads your subscription quota out of its own session, with no key and no network
• Loomi can think on Codex as well as on Claude. You pick who answers.

Fields

• Fields list in a stable order, and Ctrl+Shift+←/→ walks them.

Looms

• Every loom header carries copy, expand and rename-in-place.
• A finished turn quotes the verdict its own stream gave, instead of a state word you have to

Agents

• A loom that hands work out names who owns each step, and says so the moment it sends it.
• A loom sent off to do one job writes a plan for it now, the way a loom you talk to already did.

Usage

• Refresh reads Codex and Antigravity live, so the numbers are current rather than last seen.

Providers

• Signing in to a provider happens on its own sheet, instead of a button tucked inside a row.
• The sign-in offer follows the account rather than the binary, so it stops offering what you have

Settings

• The Settings window moves and can leave the edge, and its rows use the width they were given.
• The window rim can be told to hold still.

Fields

• A loom lands on the field it belongs to, even while you are looking at a different one.
• Stepping past the last field keeps the direction you pressed.
• A confirmation that read as a button doing nothing now says what it did.

Looms

• Every × closes on one click.
• Closing a loom twice is still one closure, and an already-exited process is stopped cleanly.
• Clicking back into a loom's message bar returns the caret where you left it, and attaching a file
• A loom that was working the whole time is no longer reported as failed.
• A loom that was never asked to run no longer reads as one that finished.
• A loom's plan keeps forty steps, so the end of a long one is no longer cut off.
• A resumed session is checked against the transcript on disk, not against the process that started.
• A restored loom's model is re-checked before it reaches the command line.

Agents

• Agents no longer flash black console windows when they start, or when the app checks your machine.
• A question you have not answered survives switching fields, and reaches the fleet board.
• The answer to a handed-off job arrives even if the loom that asked has already finished its turn.

Loomi

• You can interrupt her. An agent never can, and nothing is left queued up behind it.
• Her caption no longer outruns her, and it stops when the sound does.
• An unusable recording is refused instead of being encoded as silence.
• She names a saved batch of files by kind and count, never by reading you filenames.

Scenes

• Controls that went invisible against a dark scene now hold their contrast at both ends.

Usage

• Antigravity's usage token is renewed by the CLI instead of being read stale.
• A figure of 1.8 hours stopped printing as 1h.

Providers

• Antigravity looms no longer die seconds in from a malformed model name.
• Signing in to an agent CLI no longer exits halfway, and an install is not called finished until