A comment containing 4.5 could satisfy the mechanics check and claim that walk speed uses it, while an equivalent calculation without that literal could fail. The numeric-text match is gone: a readable mechanics sheet passes its readability check with a saved unknown for the unmeasured behavior and makes no claim about what the build uses. A check result another builder turn can't resolve no longer sends the builder to retry it; the builder states it as unverified instead, and the summary counts the comparisons that remain unverified.
POSIX makes everything after = in a ps -o argument the header, so FreeBSD's ps read pid=,ppid= as a single pid column headed ",ppid=". The process tree then had no parents, a runner's child window was never found there, and snapshot_finds_an_owned_child_on_this_host failed on every FreeBSD run since it was added.
Docs only. The roadmap line for live-checking core_text_read in an agent chat is ticked with what live Codex and Claude Code chats showed, STATUS says what was run, and a new line records the gap they found: a text file's kind is still unknown, so the target list and triage call it a file we don't recognise yet.
A PyInstaller PYZ archive could only be read through the program around it, so a PYZ-00.pyz on its own showed nothing. It's now read on its own: each module by its dotted name, namespace packages kept as a fact, the Python version its magic names, encrypted (--key) modules listed but not readable, and a module read back as a .pyc with its header. A .pyz that's a Python zip application is still read as a ZIP.
A text file outside a build (a script, Markdown, settings, a log) could only be searched byte by byte: the native tools refused it and build_file_read works only in a build. The new core_text_read (Deep mode) reads one as text, a page of lines at a time: UTF-8, or UTF-16 with a byte-order mark, invalid bytes shown as U+FFFD and counted, very long lines cut and named, and a file with zero bytes near its start refused as binary. Nothing is run.
Fixes#539
native_publisher_show reported a signed program as changed after signing when its sections had a gap between them, because the file was hashed as one run of bytes up to the certificate table. The Authenticode hash now follows the PE/COFF specification: the headers (less the checksum and the security directory entry), then each section in the order its data sits in the file, then the data after them less the certificate table, so a gap between sections isn't hashed.
When a coding agent's saved program had gone (an update moved it), another program ran in its place with nothing in Settings saying so. Settings → AI now says under the agent's program that it isn't there any more and which program runs in its place, read on the worker that loads the AI list, and offers "Use it" to save that program when it's a path of its own.
Refs #721
A service that limits requests a second or a minute could only be answered after the fact, by waiting and retrying once it had said it was rate limited. An API backend can now be given requests_per_minute in config.toml, and its requests start at least that far apart, across every conversation on that backend in the app (a crew's workers, a build and a chat). A stop ends the wait; unset or zero sends requests as they come, as before.
Refs #668
Unity Editors were looked for only in Unity Hub's default folders and its install-location setting, so an editor added to the Hub with Locate, which can be anywhere, wasn't found and Make kept saying Unity isn't installed. Unity Hub's own list of editors (editors-v2.json, then editors.json) is now read too, in either of its layouts, and every editor on it whose program is still there is offered; the list is read up to 1 MiB, and one that can't be read finds nothing.
Refs #1077
The test that a launched program's log is cut while it writes assumed the cut would come within the few seconds its stand-in spent printing, so on a loaded machine the file could end over its bound with nothing wrong. The stand-in now watches its own log and keeps printing until it has seen a cut and filled the file again, and the test checks it saw a cut before checking the size. No change outside the test.
A program started from Play or a pin wrote last-run.log or play.log for as long as it printed, with no limit. The program still writes straight to its file, now opened for appending, and while Craft Anything runs the file is cut back to empty once it passes 1 MiB (looked at every 2 seconds), so the program's writes never fail or block and the log's last lines are still there to read. A program that outlives the app is left as it was.
Adding a server by its address can wait up to a minute for one that was reached but is still starting or loading a model, and that wait could only run out. The form now has a way to stop it: the request runs on a helper thread and the wait checks for a stop every 100 ms, so it ends at once, nothing is added, and the app says it stopped adding the server instead of giving address advice.
A Swift subscript accessor was printed with its type first and the accessor last (Swift.Array.subscript(Swift.Int) -> A.getter), so the accessor read as if it belonged to the result type. It now reads as swift-demangle prints it, the accessor right after subscript and the type after a colon (Swift.Array.subscript.getter : (Swift.Int) -> A), in every symbol that names one; a subscript without an accessor still prints its type straight after.
A Swift symbol ending w and two letters is a value witness, one of the functions the runtime calls to copy, move or destroy a value of a type, or to read and set an enum value's case. These now decode as swift-demangle prints them, for example "destroy value witness for" and the type; an unknown kind, or one whose operand isn't a type, isn't decoded.
A private or fileprivate Swift declaration's symbol carries the name, then an identifier for the file that declares it, then LL, as two declarations in different files may share a name. Such symbols weren't decoded; the name now reads (name in _HASH), as swift-demangle prints it, wherever it appears: a type, a protocol, a function, a variable, a nested type or a generic argument.
When a run's time limit or a cancel fired, the program was stopped through a call that then waited for it with no limit (and on Windows for a job message the system doesn't promise to send), so a program that outlived its stop held the run past every deadline, Pause included. The program and whatever it started are still stopped, but the run now waits at most 5 seconds for them to be gone, then logs a warning and carries on.
Refs #1438
When some arguments of a Swift function, initialiser or subscript have labels, the others now read _: as swift-demangle prints them, so append(_:length:) reads append(_: Swift.UnsafeRawPointer, length: Swift.Int) instead of leaving the first argument bare. A single argument not wrapped in a tuple prints bare, as there. About 21,000 symbols from system binaries now match.
A Swift symbol ending Ml is the cache the runtime fills the first time it lays out a type's metadata whose layout is only known at run time, and one ending ML is the type's lazy metadata cache variable. Both were named "lazy cache variable for type metadata for"; Ml symbols now read "type metadata singleton initialization cache for".
A job of unknown length drew its progress bar with egui's animated ProgressBar, which asks for a frame every frame, so the window redrew at the display's rate for as long as the job ran, even in the background (as the spinner did before #579). The jobs list now uses our own progress bar: filled to a known fraction with no frames asked for, or sweeping at the animation's pace (once a second in the background) when the fraction isn't known.
Look for AI suggested the first chat model a local server listed. LM Studio lists every model downloaded and FastFlowLM every model it can download, and asking for another one loads or downloads it. A local server's suggestion is now a chat model it says is loaded, from Ollama's /api/ps or LM Studio's /api/v0/models (embedding models left out), and the first chat model listed only when nothing says what's loaded. Adding LM Studio by address gets the same.
Refs #1434
Adding a server by its address with no model named saved the first chat model its /models listed. On a server whose list is a download catalogue (FastFlowLM), that started a 5.5 GB download and unloaded the model in use. The server is now asked which models are loaded (/api/ps, which Ollama and FastFlowLM answer) and a chat model from there is used; otherwise the first chat model in /models, as before. A model the person names always wins.
Refs #1434
Adding a model server by its address showed nothing while it connected and gave up after 10 seconds, then said to check the address even when the server had been reached. The form now shows "Connecting to <name>…" with a spinner and the seconds waited, and Add can't be pressed again meanwhile. The server has a minute to list its models once reached, and one that was reached but didn't answer in time is told it may still be starting or loading a model, to wait and add it again.
Fixes#1429
A coding agent's turn ended only when its process exited, so when Claude Code printed its final result and then kept running (a shutdown hook, logging), a finished build stayed on "Building" or "Pausing" for as long as the idle limit allowed, hours for a builder turn. The turn now ends a short grace (5 s) after the stream's own result, without being reported as stopped or failed; a deadline hit before any result still stops the turn as before.
Each request starts a new run, and a run after the first skips the study, so its session had nothing open and the builder's first native tool calls said "Nothing is open yet". In Deep mode, a run that skips the study now opens the program the study looked at (found the same way, so a game given as a folder gets its executable), so the builder's tools start with it. Clean room, a builder over SSH and a program that's gone open nothing.
Fixes#1421
The run removed its mark on a builder's check right after answering, so an answer that landed as rebuild_check's wait ended made a taken check read as "No build is running". The mark now stays until rebuild_check has read it. A check interrupted by stopping the build now answers that the build was stopped, so a builder still waiting isn't told the check is still going.
A coding agent's turn killed mid-turn leaves a record of its session, which was removed only at the next agent turn or on uninstall; meanwhile the agent's own background service could carry on a session nobody was watching. The desktop app now sweeps those records when it starts, on a background thread, with the same rules as any sweep: a record a running turn holds is left alone, and a delete that fails is kept for the next sweep.
Started from the Dock, the app has a short PATH, so a Codex installed inside the ChatGPT or Codex app wasn't found. It's now looked for in those apps' known bundle locations (never the app's own executable), after an explicit program and PATH. Testing a local coding agent in Settings → AI (or `ai test`) now also asks its adapter whether it's signed in, without sending a prompt, and Codex only gives sign-in advice for real authentication failures.
A coding agent's saved session counted as the project's history whatever mode it ran in, so after switching between Clean room and Deep a run could skip its study and build from the other mode's capture. A saved session or transcript now counts only in its own mode (one saved before the mode was kept counts as Deep); one from the other mode makes the run study again and replace the capture before the builder is briefed, including an API follow-up whose transcript was rejected for its mode.
rebuild_check said "no build is running" when the run had taken the check and one of its steps hadn't finished, and the builder gave up after its default 20 minutes, below the run's own 30-minute limit on a check. The run now marks a check request it takes, the tool says "still going" apart from "no run took it", and its default wait (35 minutes) outlasts the run's limit, so the run reports a stuck check itself.
In Deep mode, a builder that hadn't decompiled anything was reminded to, but whether it had was kept only for one run, and each request from the person starts a new run. So a builder that had read the original's functions earlier was told "You haven't decompiled anything yet" after every request. It's now kept in the project's craft.json, so a decompile in any run counts.
A question answered from a fork of the builder's Claude Code session reported the whole session's running total, so its cost was hidden. It's now what the total added since the builder's last turn, read before the question starts, and unknown when there's no kept total, never the session's total. The question's cost is added to the project's usage, and a build turn and a question saving their costs at the same time no longer overwrite each other.
A GNU long-name or long-link record whose text was complete but whose 512-byte padding was cut off, or whose padded size overflowed, stopped the listing without saying why, so the engine installer could still write the files listed before it and report success. Both cases now count as a cut-short GNU record, and the installer refuses the archive before writing anything.
An ASAR manifest whose nodes aren't objects, are both a folder and a link, have a link that isn't text, have no size, a non-boolean `unpacked` flag, or a packed file with no offset is now reported as damaged instead of being listed with made-up values.
When a tar listing stopped at a GNU long name or link it refused (too long, or cut short), the engine installer still wrote the files listed before it and reported success, which could replace a working engine with part of one. The listing now says why it stopped, and the installer refuses such an archive before writing anything, with a plain-English error. An archive missing only its end marker still installs.
ZIP entries compressed with LZMA (method 14) were listed and not read. They're now extracted with the same output limit, size and CRC checks as other methods, whether the stream gives its size or ends with a marker; the dictionary is held to the output limit, and properties of another size are reported as unsupported.
A GNU sparse member stores only some extents of its file, and was extracted as if those were the whole file. It's now listed as another kind of member with a warning, under the name GNU.sparse.name gives when there is one.
A versioned ELF import names its library while its relocation slot doesn't, so since slots were matched by name and library, such imports lost their slot address. An import now takes a slot of its own library first, then a slot with no library only when the name belongs to one library and has one address.
A standalone LZMA stream's declared size is now checked against the output limit before decoding, and its dictionary is held to the limit, so a damaged stream can't grow a large window before failing.
ZIP entries compressed with bzip2 (method 12) or XZ (method 95) were reported and not read. They're now extracted with the same output limit, size and CRC checks as deflated entries.
A gzip member in a packed bundle was inflated without its trailer being checked, and only its first gzip member was read. Every member is now read, within the size limit, and each trailer's checksum and length must match.
A gzip header with the optional header checksum (FHCRC) is now checked against it. The extra-flags and operating-system bytes, which are only informational, no longer make a valid header be refused, while reserved flags still do.
A member whose stored bytes reach past the start of the archive's table, into the table, cookie or a signature after it, could be read as that member. Such members are now unreadable, with a note counting them, and a PYZ there supplies no nested members.
A method list whose record size was smaller than a method record, or whose last record was only partly in the file, was still read, so methods came from whatever bytes followed. A list now needs records of at least 24 bytes (12 for relative ones), each wholly in the file, and longer extended records still read.
A Godot pack embedded in an executable ends before its trailer, and a member's data could run into the trailer. The file table and members are now read only before it, and a member that would reach past it isn't readable.
A `long` or `double` constant takes two constant-pool slots, and one in the last slot was read past the pool's declared count. Such a constant is now refused as a damaged class, with no overflow at the largest pool size.
Cooked Unreal textures in half- and full-precision float formats (R16F, G16R16F, FloatRGBA, R32_FLOAT, G32R32F, A32B32G32R32F and the filtered half aliases) were reported as unsupported. They're now decoded with the shared float reader: colour becomes 8-bit sRGB, alpha stays linear, and values outside the range are clipped.
The metadata reader took a header offset past the end of a short input and read past the declared metadata into object bytes. The offset and size are now checked against the object data, the declared file length and the bytes supplied, and only that range is parsed.
Each repeated name or producers section got its own allowance, so together they could keep more than the item limit, and the cutoffs left metadata out without saying so. The function-name and producer limits now apply to the whole module, names already kept can still be updated at the limit, and the report says when anything was left out.
A resource chunk could fit in the file while reaching past the size its table or package declares, so string pools, library records and short headers could read unrelated bytes. Each chunk is now read only within its parent, package and known child headers must be complete, package string pools stay inside the package, and only complete library records are kept.