Claude Code v2.1.272

The routine that renders a bridge connection's QR code as text (using a UTF-8, low-error-correction QR encoder) was splitting the wrong variable into lines: it used the value captured before an asynchronous operation completed, instead of that operation's actual resolved result. This is now fixed.

Scripts running inside the new AppifactRepl tool (see related entries) can call claude.see({text, images}) to attach images and text notes to the tool's result. Up to 4 images are allowed per result, and only PNG or JPEG images are accepted; anything larger or in another format is refused, with messages such as "at most 4 images per result" and "not a PNG or JPEG".

The tool-name resolver now imports isPewterOwlTool from the same dynamically-loaded chunk that already supplies the Brief tool's name, the send-user-file tool's name, and the Brief tool's own enabled check (isBriefEnabled). This suggests a second tool, alongside Brief, that is controlled by its own feature flag.

The process that starts an AppifactRepl session refuses to run on Windows. It also has no way to run inside a sandbox (an isolated execution environment) yet: it only runs commands unsandboxed, and if unsandboxed commands are disallowed for the session, it refuses to start at all.

A new internal protocol lets scripts running inside AppifactRepl (see the related entries on this tool) issue Artifact tool actions directly: reading or querying data (get/list/query), writing it (set/update/delete/batch), working with files (read_file/read_files/list_files), handling assets (upload_asset/read_asset), and publishing or opening the artifact. Messages are exchanged as one JSON object per line.

Each action is checked against the session's permissions individually, and can be refused, for example, if the Artifact tool's database actions or asset actions are turned off for that session.

When the Artifact tool renders the result of a read, it appends extra text explaining how to proceed. This routing text is now produced by a new function, fxn(), which first checks whether the Artifact REPL tool is present and returns nothing if it isn't, instead of always producing the text as before.

A second new helper, hur(), looks up a per-Artifact-type "two steps" routing note keyed by the file's frontmatter name, and reports whether the referenced files were kept as files. This feeds into flags used elsewhere to track how a read was handled.

The background runner's failure-reporting path, covering runner:session and runner:stuck logging, gained new timing constants (500ms, 1000ms, 2000ms, and 3000ms) and an abort helper. These are used when retrying a failed attempt to post a failure result, and to detect when another runner has already taken over a session, logged as a "stale epoch" rejection.

When creating a typed Artifact after a quickstart call, Claude Code shows a reminder that quickstart already listed the available design systems in the conversation. The function that builds that reminder now first checks an internal helper, afterQuickstartSavedLine, for a saved or customized version of the line, and only falls back to the generic wording if none is found.

In the code that checks for and reports Claude Code updates, several messages, including the current version line, "Update available" notices, and "Claude Code is up to date" messages, now go through an internal output helper called lr instead of the previously used ar. The messages themselves are unchanged.

The embedded VERSION, BUILD_TIME, and GIT_SHA constants were updated from 2.1.271 to 2.1.272 in many places throughout the bundled code, where the same metadata block is duplicated across chunks.

A warning message shown when a background process is using a stale binary now has both of its code paths call the same internal helper function, Ou(), where one of them previously called a different helper, xu().