Your editor never breaks

The thinking line and the chat banner modify two files inside Claude Code, and modifying another program's files is exactly as dangerous as it sounds. So the patch engine is built like deployment infrastructure: byte-exact backups, hash verification before and after, atomic writes, and a fail-safe that prefers earning less over breaking anything.

Before anything is touched

The engine trusts nothing but hashes. A file is only patched if its content hash matches a known-good original for that exact Claude Code build - a file modified by anything else is left alone. Before writing, the original bytes are backed up into Awaitful's own private storage, never as stray files next to Claude Code, and a Claude Code update naturally invalidates old backups because the build changes.

The write itself

Writes are atomic: the patched content goes to a uniquely named temporary file which is then renamed into place, an operation the filesystem performs completely or not at all. A crash mid-write, or two editor windows patching simultaneously, cannot publish half a file.

Verified after, or rolled back entirely

After applying, every patched file is read back, the patch is stripped out, and the result is re-hashed - it must reproduce the original exactly. If any file fails that check, all of them are rolled back together; the patch applies both-or-neither. Any error at any point triggers the same restore.

The fail-safe

Every failure path - unknown build, unfamiliar bytes, a conflicting extension, a failed verification - ends the same way: your editor left untouched or restored, and Awaitful quietly earning from the status bar instead. A failed patch never takes the product down with it; the fallback is itself a working surface. What that looks like in practice is described in Thinking line fell back to the status bar.

Updates, and other extensions

When Claude Code updates, Awaitful re-applies automatically once a verified recipe for the new build exists. If another extension overwrites the same files, Awaitful reclaims them a bounded number of times and then yields - it earns from the status bar and tells you about the conflict rather than fighting a write war inside your editor. It never touches another extension's files.

All of this is public code, not a description you have to trust - start at Verify it yourself. And consent is per surface: nothing here happens unless you turned a patch surface on in Choose where the line appears.