> Warden / blog
• workspace, control, usability

When Something Breaks, Nothing You Keep Disappears

A damaged file, a copied home folder, or a changed machine should cost you a notice, not your sessions or your sign-ins. Warden now moves what it cannot read aside, says so, and keeps going.

A coding client keeps more than conversations. Session records, checkpoints, cost history, and the sign-ins it uses to reach your model providers all build up on your machine, and all of it can meet a bad day. A disk fills mid-write. A home folder gets copied to a new laptop. A file is damaged. The worst response to any of these is the quiet one, where something that cannot be read is replaced with something empty and you find out weeks later that your history is gone.

Moved aside, never deleted

Warden’s stores, session records, checkpoints, and cost files now carry a version, and a file Warden cannot read is moved aside with a notice instead of crashing the session or vanishing. Store failures that used to pass silently now raise one notice per store, so a problem is reported once, plainly, rather than swallowed.

Sign-ins that survive a move

Warden seals your sign-ins with a key this machine holds. If it finds a key the machine cannot open, because the home folder was copied, the machine or the user changed, or the file is damaged, it moves that key and the sign-ins it sealed into a dated folder and starts a fresh one. Nothing is deleted. Signing out no longer fails on a sign-in Warden cannot read; it removes it.

The keys that open Warden’s own databases are handled the other way round: a missing one is refused loudly, never quietly swapped for a new one. Warden’s home folder is also kept readable by you alone, and Warden sets that again every time it opens.

An answer you read once

Sometimes a model’s answer fails partway through and has to be requested again. Warden used to retry quietly while the failed attempt’s first lines were already showing, so a reply could repeat its opening after each retry. Now the partial text is withdrawn before each retry and you are told it is retrying, so you read the answer once.

Built for the bad day

None of this is something you notice on a good day. It decides whether a bad day costs you a notice or your history. It sits beside a long session that survives a hard stop: the session rides out a killed process, and what it keeps rides out a damaged file.

Warden is a working proprietary development build. Supported platforms and data handling will be stated with its public release.

Was this useful?