A new `cargo xtask status` check, also run by `cargo xtask ci`, fails when a table in docs/STATUS.md lists the same area twice, as union merges of the docs have done before.
A library name, soname or run path whose offset or terminator lay past the dynamic string table's declared size (`DT_STRSZ`) could take bytes from whatever followed the table. Those names are now read only within the declared size, keeping the existing length cap for long names.
The header line of a device's `ps` output is now cut at the same length limit as its rows, on a character boundary, so a very long header can't stretch the columns read for every process.
The check after every build starts the program with `--screenshot`, and its window came up in front of what the person was doing, with focus. The contract every app and game brief carries now asks for that run's window to open without taking focus and to keep drawing while unfocused, and on Windows also behind other windows. On macOS and X11 a covered window is reported occluded and stops painting, so it isn't lowered there. Started without the option, the program opens as usual, so Play still brings it to the front.
A default such as `DEFAULT -'1e3'` is read as SQLite reads it: the quoted text becomes an integer when it's written as one and a real otherwise, is negated, and then takes the column's affinity, so it's '-1000.0' in a TEXT column and -1000 in an INTEGER one. Quoted text with a digit separator, or that isn't a number, stays unsupported.
Claude Code reports the whole session's running cost on every turn, and a build resumes the same session each turn, so adding each turn's figure made a long build's estimate grow far past what it cost. The last total of each session is now kept in the config folder, and a resumed turn counts only what it added; a new session's first turn counts its total, and a resumed or forked session with nothing kept counts nothing rather than an inflated figure.
Refs #1187
Swift symbols refer back to earlier parts by position, and the demangler must number them the way the compiler does. An `Sg` optional and the `Qz`/`Qy` associated types now take a substitution slot and extensions no longer do, so a later back-reference names the right type instead of its neighbour, as in symbols from macOS system binaries.
An added column's default is now filled when it's a bare word (`DEFAULT abc`) or a double-quoted word, which SQLite keeps as text at the top level, and when a number has digit separators (`1_000`), read with the column's affinity. A bare `x` is no longer taken for the start of a blob, and words or quoted names inside parentheses, which SQLite refuses as not constant, stay unsupported.
Asset catalogs key symbol images by glyph weight (attribute 26) and glyph size (27), which were listed by number only. They now read `glyph-weight` and `glyph-size` in the key format and each rendition's key.
A TOML config saved with Windows line endings, such as Codex's, keeps them when setup adds or removes our entry, as the JSONC and YAML configs already do. A file that mixes line endings, or whose values the change would alter, is written as before.
`mcp_servers: null` or `~`, with or without a comment, is now an empty table like `{}`, so our entry goes into it and the comment is kept. A flow table with members, or a value that carries on onto the next line, is still left to the person.
The binary view had its own platform table, which stopped before DriverKit (10) and the visionOS simulator (12), so a DriverKit extension read "unknown" while the dependency view said "driverkit". It now uses the dependency view's table, so both name every platform alike, and an unlisted number reads `platform-N` in both.
Python 3.5 is the one line that changed its magic number in a bugfix release: 3.5.0 to 3.5.2 wrote 3350 and 3.5.3 moved to 3351. Only the latest number counted as a release, so a `.pyc` from 3.5.0, 3.5.1 or 3.5.2 was reported as coming from a pre-release. Each line now records the lowest number a final release wrote, and both 3350 and 3351 read as releases.
Removing our entry when it was the last member of a plain-JSON config, such as Claude Desktop's, left a trailing comma that strict JSON readers refuse. The comma before it now goes too. A file whose members already end in commas keeps that style, both when an entry is added and when it is removed.
On Windows the coding apps keep their settings under the user profile and ignore HOME, which a shell such as MSYS2 or Cygwin points elsewhere. Setup now takes USERPROFILE first there and HOME first elsewhere, and an empty value counts as not set.
A registration may name the CLI by its bare name (`craft-anything-cli mcp`), as `claude mcp add` writes it. The app starts such a name from PATH, and doctor now looks for it there and in the usual install folders too, instead of calling it missing.
A byte-order mark that some Windows editors put at the start of a YAML config was read as part of its first key, so setup added a second table of the same name that hid the first. The mark is now set aside while the file is read and edited and put back as it was, so our entry goes into the existing table and removing it gives the file back byte for byte.
A check round in which every check worked is kept, and the next check reuses its results while nothing it looked at has changed: the app's files, the reference and capture files, the kind, stack and mode, the plugin checks and the project's folder. So a prompt that changes nothing in app/ no longer builds and starts the app again, and the check after the builder's turn doesn't repeat its own check. The feed says when results stand. A round with any failure is never kept, so Try again always looks again; the kept round is saved in the build progress.
A round of the builder's own checks now has a 30-minute limit, Pause is looked at before each check and stops a running build step, and every check is said as its own step ("Checking its work (2 of 4): …"), so a check that stalls names itself instead of holding the build for hours. The limit reaches the checks' own program runs, a step is refused before it starts once the round is past its limit or paused, a check that can't run is reported as not run with its reason, and a caught bug leaves the project at "Needs you" instead of "Checking". Real check rounds keep no limit. Addresses the stalls reported in #981 and #1198; a live Windows run is still to do.
OpenCode Go backends that weren't added through Settings (from an older version, or found from an environment key) had no saved session id, so each run sent a new one. The app and the CLI now save one at startup for any OpenCode Go backend that has none, before any session lock is taken, and keep it across restarts. An OpenCode error that comes without a message now shows its name, HTTP status and the start of the response body instead of "no error details".
Refs #1225
Devin can be added as a coding agent. Builds talk to `devin acp`, which takes our tool server and sends its permission requests to the approval policy; since Devin doesn't use its own CLI sign-in over ACP, the session authenticates with the key stored for that backend, sent only to the local process and only when Devin offers that method. The key is looked up only for agents that authenticate this way, so other agents never touch the keychain. One-off questions use `devin -p`, and `craft-anything-cli ai add --acp` sets an agent to ACP.
The Send button takes its icon and hover colours from the theme instead of fixed white and black, a sidebar status pill and a palette tag use the theme's small corner radius, code in the chat and evidence uses the app's code size, an evidence summary uses the small and body sizes, and a Just ask question uses the semibold body size of the other card titles.
SQLite keeps a comment after a CREATE TABLE's column list in the stored statement, and the end of the list was taken from the last `)` in the text, so a parenthesis in that comment hid `WITHOUT ROWID` and `STRICT`: such a table read no rows, and its ANY columns lost their STRICT handling. The list's closing parenthesis is now found by tokens, outside comments, strings and quoted names.
A catalog compiled for a system older than one of its key attributes (display gamut before macOS 10.12) keeps a placeholder in KEYFORMAT and the real attribute in KEYFORMATWORKAROUND. That block is now applied as the system applies it, so the key format and each rendition's key name the real attribute, such as `display-gamut` for a Display P3 variant, instead of `placeholder`.
A code signature's flag names used the wrong bits for hard, kill, expires, restrict, enforcement and library-validation, and named two of them as other flags, so a library-validation signature showed no flag names and a hardened one read "allowed-entitlements". The names now follow the bits and words `codesign -d` shows.
With no `max_tokens`, OpenRouter holds a model's whole output limit against the key's credit, so a key that still had money was refused with 402 "can only afford N" before the model ran. On that refusal the request is now sent once more with the answer capped at what the key can afford, and the cap is kept for the conversation. A cap under 4,096 tokens, a repeat refusal and other providers stay a billing error as before.
Fixes#1213
A pin's menu says "Open folder", as the project page does, for the same action. A game's chosen folder is shown like every other chosen folder: shortened, cut to fit its row and whole on hover, so a long path no longer widens the page.
A server that took the request but didn't start answering in time now says so instead of "Couldn't reach". When the AI runs on this computer (localhost, 127.x or ::1), the advice says a large model may still be loading or reading a long prompt, and a server that can't be reached is told to check it's running here, with nothing about the internet connection. Remote servers keep their advice.
`LC_MAIN` gives a Mach-O executable's entry point as a file offset. It was mapped through the last segment starting at or below that offset, so a `__DATA` holding only zero-fill sections, which has no file bytes but records file offset 0 like `__TEXT`, took the entry point and placed it outside the code. The offset now maps through the segment whose file bytes contain it, and an offset no segment holds gives no entry point.
A SquashFS metadata table cut inside a block's header or payload now says so with a warning and marks the recovery incomplete, instead of stopping silently. Only blocks that were read are mapped, so the blocks before the cut stay readable and nothing points into the missing one.
A default filled into an older row is now read the way SQLite reads it into that column: a TEXT column reads a number as text, NUMERIC and INTEGER columns read text that is a number as that number, a REAL column then makes it a REAL, and BLOB, untyped and STRICT ANY columns keep the literal as written. Numbers too large for a REAL stay unsupported instead of showing as infinity.
Ollama fits a prompt that is too long for its context by dropping the oldest messages; once the person's request is among them, a Qwen 3.8 model refuses what's left with 500 "no user query found in messages". That refusal is now reported as a context overflow, saying how to give the model a larger context or send less, and it is no longer retried, since the same request would be refused again. Other server errors are still retried.
Fixes#1245
Source map lookups find the section and the segments at a generated position by binary search over the sorted lists instead of scanning them all, keeping every mapping that shares the matched column.
Source map VLQ fields now decode the whole signed 32-bit range, including the reserved encoding of the minimum, reject values beyond it, and accept redundant zero groups without overflowing a shift.
Some linkers write a version string with wType 0 (binary), and the PE reader dropped it, such as a DLL's FileDescription. A binary leaf at the string depth is now decoded as UTF-16LE text, while a binary node that holds a child node is still walked as a container.
Rows stored before ALTER TABLE ADD COLUMN now get the added column's default when it is a hex integer (`DEFAULT 0x10`, kept as SQLite's 64-bit two's-complement value) or a single literal in parentheses (`DEFAULT (5)`, `DEFAULT ('hi')`), instead of NULL with an "unsupported DEFAULT" note. Expressions and nested parentheses still show the note.
A column's declared type keeps the comma inside its parentheses, so `DECIMAL(10, 2)` is listed as written instead of `DECIMAL(10 2)`, in the parsed columns and the schema overview; only the comma that separates columns is dropped.
Schema rows were decoded with the 4 KiB cap used for every text value, so a CREATE TABLE longer than that lost the columns after the cut, its rowid alias and its WITHOUT ROWID marker. The schema is now read whole for parsing (up to 1 MiB per statement and 32 MiB per walk, after which text is cut as before), while the statement shown is still cut at 4 KiB on a character boundary.
A build carrying on without a new request deleted the API builder's kept conversation before starting, so it could never resume and always studied again. The conversation is now kept whenever the run is continuing, and only a genuinely fresh build (no continuation and no finished study) starts a new one; a conversation from the other mode is still refused when it loads.
SQLite stores a REAL with no fractional part as an integer and turns it back into a REAL when it reads a column with REAL affinity. Rows now read the same way, including WITHOUT ROWID keys and filled-in defaults of added columns, so `1.0` no longer shows as `1`. Affinity follows SQLite's order, so a `FLOATING POINT` column, which contains INT, stays an integer column.
Solana program relocations are read at the table's declared entry size, which must be at least the record's own size, and each record must be complete; a short entry size or a truncated table is reported instead of fields being read from the next record.
Before a certificate's fields are used to verify a signature, the algorithm OID must be the first element of its sequence and valid, the key and signature bit strings must be non-empty with no unused bits, and the issuer and subject must be sequences. A certificate that fails these checks is not taken apart for verification instead of yielding an empty algorithm or misread bytes.
Adds tar tests for PAX records with a signed length, an empty key or an equals sign inside a path value: malformed framing stops the listing, and `path=a=b` names the member `a=b`.
A cpio member's name must end in a NUL (extra NUL padding is still allowed), and an archive counts as complete only when its trailer is empty and fully present. An unterminated or invalid name, or a trailer with data or cut short, stops the listing with a warning instead of the archive being reported complete.
The XML plist reader now takes exactly one value, inside a closed `<plist>` when there is one, with only whitespace, comments and declarations around it: unclosed roots, extra values, stray text, non-empty `<true>`/`<false>` and a `<key>` outside a dictionary are errors instead of being read past. A DOCTYPE's internal subset is skipped as one declaration, without fetching or expanding entities. Invalid UTF-8 and a half UTF-16 code unit are reported instead of being replaced.
An index source map's sections now need a valid offset and either an inline map or a `url`, in ascending order; malformed section tables are an error instead of defaulting to offset 0. A section that points to an external map, which is never fetched, keeps its start, so lookups past it no longer borrow mappings from the inline section before it.
The check that a module has one code body per declared function now counts every declaration in the function section, not only the ones the inventory kept, so a module with more functions than the listing limit no longer gets a false "function declarations but bodies" warning.
A packed bundle member whose stored or unpacked size differs from the size its manifest records is now an error instead of being returned as if it were complete.
Source map and external debug URLs in WebAssembly custom sections are read as WebAssembly names: invalid UTF-8 is rejected instead of being replaced, and long inline source map URLs are kept whole.
A function's local count now includes every local declaration group, not just the first 10,000; the inventory limit still applies to the number of functions listed.