Docs only. A live chat --deep run with Claude Code on a 581 KB comparison of two builds showed it asking for a summary, then paging the result with core_evidence_browse and quoting the rows, with no result over the 80 KB budget, and a page just under the budget reaching it whole. The roadmap line is ticked with what the run showed, and two new lines record the gaps it found: name the lists core_evidence_browse can page, and compare Rust names without their crate hash.
A text file (notes, source code, settings) was a target of unknown kind, so the target list and triage called it a file we don't recognise yet. Text now has its own target kind, found by the same check the text reader uses (a byte-order mark, or valid UTF-8 with no zero bytes and few control characters near the start) after every other format, so lists and triage call it a text file and point to core_text_read. A binary file stays unknown.
A key save still in flight could write the key back after the backend's removal had deleted its key and configuration, leaving an orphan key that a backend re-added under the same name would silently use. Saving or forgetting a key and removing a backend now take turns, so a save that comes after a remove fails, and Settings keeps a backend's remove button disabled while its key is being saved or forgotten.
A GGUF model's quantized tensors (Q4, Q5, Q8, K and IQ types) had no byte length in the model-header report, so a complete tensor table could describe a truncated payload without that tensor being counted as past the end of the file. Their storage length is now calculated from each type's block layout, scale bytes included; a row width that isn't a whole number of blocks is reported, an unsupported type keeps an unknown length, and the end-of-file checks can't overflow.
The key row #1486 added for every API backend pushed the add-by-address form's Add button below the AI settings page's visible area, so the test's click could land outside it and the test failed now and then. It now scrolls the page first, as a person would.
A key saved in the app silently wins over the one in the environment, so a rotated key stayed hidden behind the old one unless the backend was removed or the keychain edited by hand. Settings → AI now shows for every API backend whether a key is saved; a saved one can be forgotten, so the environment's is used again, and a new one saved in its place, without removing the backend. The CLI does the same with ai key <name> (--key-env, --key-stdin or --forget), and never prints the key. A new key is read back after saving, and a forget that a locked or failing keychain can't confirm says so instead of reporting success.
Refs #1358
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.
CheckStop::limited is only used by Unix tests, so on Windows it was dead code and clippy --all-targets -D warnings failed on main there. It's now built only for those tests.
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.
After stopping a program, the wait for it to be gone stopped silently when checking its exit failed. It now logs a warning with the error; a program that ended, one still running, and one past the 5-second grace behave as before.
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.
On Unix a folder's name may hold a backslash, and turning it into / named another package (cmd/foo\bar became ./cmd/foo/bar); Go reads a backslash as a separator, so keeping it wouldn't help either. The package is now written from the path's folders joined with /, the same on every system, and a command folder whose name holds a backslash gets no inferred launch.
A Go project's command package was written with the system's separator, so on Windows the launch test expected ./cmd\viewer while the launch gave ./cmd/viewer (right for go run only by accident, from a mixed path). {package} now always writes the folder with /, as Go names packages, and the test expects ./cmd/viewer.
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 build on an SSH host started Craft Anything's tool server by the bare name craft-anything-cli. The pre-build check found it, but Claude Code starts the tool server with its own PATH, so the server failed and the build stopped with "Craft Anything's tools did not start in Claude Code". The check now prints where the helper is, and the tool server is started by that absolute path; when the host gives no absolute path, the bare name stays.
Since a turn now ends shortly after its stream's result line, that line alone decides whether a lingering process counts as a finished turn. Gemini CLI's result event wasn't checked for a failure; one whose status isn't "success" now fails the turn with its error, as Claude Code's already does.
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.
Two edits to the README's AI paragraph had landed on top of each other, so it broke off mid-sentence, repeated the Copilot and ACP text, and said both that only Maki and that Maki and Devin had been run live. It now has one version with both updates: Devin among the ACP agents and xAI among the providers.
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.
Whether a build turn gets the Deep-mode decompile reminder is now one function the run calls, with a test that reopens the project from disk as a later request's run does: reminded in Deep mode on a program with nothing decompiled yet, and not in Clean room, after an earlier run's decompile, or without a program target. Behaviour is unchanged.
The English README explains how to check that a Mac download is signed and notarized; the Japanese, Korean and Chinese READMEs stopped before that section. Each now has it, translated, with the same commands.
The Traditional Chinese README's Craft App Suite table had no MaterialCraft row. It now lists it after TextureCraft, as the English README does, with the same links and its description in that language.
The Portuguese README's Craft App Suite table had no MaterialCraft row. It now lists it after TextureCraft, as the English README does, with the same links and its description in that language.
The French README's Craft App Suite table had no MaterialCraft row. It now lists it after TextureCraft, as the English README does, with the same links and its description in that language.
The Spanish README's Craft App Suite table had no MaterialCraft row. It now lists it after TextureCraft, as the English README does, with the same links and its description in that language.