Densar 4.0.0

Densar BK 4.0.0, Windows, one file.

SHA-256 of densar.exe: 3663ef0be7d599d845e216c9fba9fba9f2c3881c991f86edb0378c84cda7408f

What is new since 3.0.5: Densar now works on whole disks.

• Clone disk (with the licence). Clone system copies only what Windows needs to start and fits a larger disk (C: grows to fill it) or a smaller one, as long as the data fits; the boot setup is rebuilt on the new disk, so it starts on its own once fitted in place of the old one. Clone disk copies every partition; Clone partition copies just one. Only the used blocks are copied (byte for byte as an option), the source is read from a snapshot so Windows can stay on, the disk Windows runs from is never a target, and the file system of the copy is checked at the end.
• Partition manager (with the licence). Create, resize, format and delete partitions, change letter and name. The Windows partitions are protected.
• Disk health (free). Status, life left, temperature, power-on hours and data written, for NVMe, SATA and many USB enclosures.
• A new home screen, with Full, Differential and Incremental grouped under BK Classic, and a rounded icon.

Classic backups, restoring and disk health stay free. BK Smart AI, disk cloning and the partition manager are 59 euro, once.

Densar 3.0.5

Densar BK 3.0.5, Windows, one file.

SHA-256 of densar.exe: 34039920e75d16a9e5d7cf988da9afc73151fb18727fcd5f9e2e269841dd7591

What changed since 3.0.4: the resumed upload no longer has a fixed number of attempts.

• After a resumed upload reports "done", Densar waits for the size on the server to settle and, if bytes are still missing, resumes from there for as long as the size keeps growing. It gives up only when the size stops growing three times in a row. A file that is still arriving is never abandoned halfway; a transfer that is truly stuck does not loop forever. The re-read hash of the remote copy remains the judge.

Nothing else changed.

Densar 3.0.4

Densar BK 3.0.4, Windows, one file.

SHA-256 of densar.exe: 4f30aa1f19a467a6f512493c36a0b216c4a80cb4aa8e05d90799bfe882c62394

What changed since 3.0.3: the resumed upload, done properly.

• After a resumed upload reports "done", Densar now waits for the size on the server to settle before deciding. If bytes are still missing, it resumes from there, up to three times; if it is all there, it moves on. The re-read hash of the remote copy remains the judge.
• The final size check also reads the settled size, not a single read taken on the fly.

Why: 3.0.3 trusted one size read taken right after the resume. Some servers report the size late for a few seconds, so a copy that had arrived whole was being marked incomplete and discarded. 3.0.2 had the opposite flaw and appended the same chunk twice. 3.0.4 sits in between, which is where the correct behaviour is.

Densar 3.0.3

Densar BK 3.0.3, Windows, one file.

SHA-256 of densar.exe: 4c12cd83902b5418dfb9544290ab6fd27890c79a0060830da31e3e05b7e57976

What changed since 3.0.2: two fixes to the remote upload, from a night when a backup went silent.

• After a resumed upload completes, Densar no longer re-reads the file size from the server before deciding what is left. Some servers report the size late after a resume, and that made Densar append the same chunk twice. The re-read hash of the remote copy remains the judge of the copy.
• A watchdog on the upload: if no byte moves for twenty minutes, Densar writes the result file with the error and exits, instead of staying silent until something kills it. The morning after, the outcome is always there, and the local copy stays.

Nothing else changed.

Densar 3.0.2

Densar BK 3.0.2, Windows, one file.

SHA-256 of densar.exe: 4cf01a54d753f71bf9a18567a071c40d6e8655d6d829af62611b381087d727a7

What changed since 3.0.1: one rule for the Sam department (the backup of a personal assistant), written into the program.

• The profile of a Sam takes everything that lives in her folder: models, voice, vectors, memory, media, secrets, keys. It never leaves out a piece of hers. Only build caches stay out (node_modules, target, __pycache__, .vite, dist and the other build outputs), and the engine skips those by itself, not the profile.
• When the Sam department creates or rewrites a profile, the exclusion list is emptied, whatever the form sends.
• If a Sam profile still lists an exclusion that is not a build cache, Densar says so at the start of the backup (a line in the log), in the result file (esclusioni_sospette) and in the Sam department window. The backup runs anyway: a night with one piece missing is better than no night, but it must not go by in silence.
• Densar keeps no list of required pieces: it copies the Sam folder as it is. If an update removes a piece, Densar does not look for it.

Why: a Sam profile had been excluding its models and its speech model for days, and two nightly archives went out without a single model file. Nobody noticed, because nothing said it.

Densar BK 3.0.1

Densar BK 3.0.1, Windows, one file.

SHA-256 of densar.exe: 20520a89074049399cd1336e55bd6cb8ebaa8186060bc9e4888d3ea36e31cc05

What changed since 3.0.0: the memory of the other AI assistants was tested live, one by one, with the real programs installed (Gemini CLI, GitHub Copilot CLI, Cursor, Copilot in VS Code), and the restore now does what each of them needs to find its chats again on the new PC.

• Gemini CLI: its ownership markers (.project_root in tmp and history) are rewritten with the new path. Before, Gemini discarded the registry entry and created a new project id, leaving the restored chats orphaned.
• Cursor: the chat you see in the app does not live in the transcript but in Cursor's indexes. The backup now carries the rows of that project (and only that project) and the restore puts them back under the workspace hash of the new path, creating the workspace folder. The .cursor\projects folder is renamed with the slug of the new path. Cursor must be closed, and it must have been opened at least once on the new PC: if not, the result says so and you restore the memory a second time.
• Copilot in VS Code: the workspaceStorage folder is renamed with the hash of the new path and its workspace.json points to the new folder. If VS Code already opened that folder, the chats are merged into its workspace.
• Copilot CLI: no change needed. Its index rebuilds itself at the first resume, so the note that said otherwise is gone.

Not saved, because they do not live on disk per project: Cursor's cloud Memories and Copilot Chat's global memory notes.

The program is a bit larger (about 17 MB): it now carries its own SQLite to read and write those indexes.

Densar BK 3.0.0

Densar BK 3.0.0

Restore straight from your own server, guided. In the SAM area the gesture is now three sections: Bring her back from the server (Densar reads the server and lists the copies with their date, the most recent in full pink and the others fading to grey; pick one and it is downloaded with a progress bar inside the program, then a window asks for the keys, each field saying what it opens: the key from the paper sheet opens the copy downloaded from the server, the archive password opens the archive and comes already filled in from the profile), from a local copy (same gesture, no download) and Open an archive and pull files out. The result says where the copy came from and its date. If you type the archive password where the paper-sheet key goes, the error tells you which of the two secrets is wrong, before downloading anything.

Three real defects fixed in the server restore (found on the first live test): the key was not checked before downloading; a failed attempt left the downloaded file on disk; a sealed copy already on disk was handed to the import as a plain archive and failed with "wrong password" on a good copy. Now a sealed copy is always opened with the key, wherever it comes from, downloads go to a temporary name and are cleaned up on failure, and the key is validated first.

Any archive opens like a zip. Folders and files as they are in the copy, enter a folder with a click, tick files or whole folders, search by name, then Export to the Desktop or Export to a folder. Everything is pulled out in a single pass; nothing on the PC is ever overwritten (a name that exists gets a suffix). Available in the SAM area (from the server or local) and in the Open screen for any backup.

The memory of other AI assistants. Besides Claude Code, BK Smart AI now saves and puts back the local memory of Cursor, Gemini CLI, Codex CLI, GitHub Copilot CLI and Copilot in VS Code. Only the sessions of the project being backed up are taken (Codex and Copilot CLI keep sessions of every project in one folder). After a restore, the project paths inside the files (Codex, Copilot CLI) and in the registry (Gemini) are rewritten from the old location to the new one. Copilot in VS Code comes back under the same key, but VS Code ties it to the folder's creation date: the result says so. Windsurf is not saved: its history has no documented link to the project. An assistant that is not installed is simply skipped.

Also: the manual re-upload now applies the usual remote rotation (it converges to N copies and can never remove one too many); the in-app update bar is silver, like the rest of Densar.

Formats (.age, sealed remote copies), existing profiles and the 2.2.0 command line (--elenca, --estrai) are unchanged. Restoring, extracting and opening are free, as always.

Windows, one file. SHA256 below, in the README.

Densar BK 2.2.0

What changed

Pull out one file, without restoring anything. Nine times out of ten, the person with a backup does not have a dead disk: they deleted a file. Until now Densar could only do the full restore, which takes the whole machine back to last night. Now, in the Open screen, under the archive contents, there is a "Pull out a file" section: search by name (a piece of it is enough, and * and ? wildcards work), tick what you want and pull it out into a separate folder. The archive is only read; nothing is ever written over the original, or over a file that already exists (if a name is taken, the copy goes next to it and the program says so); if nothing matches, you are shown the closest paths. It works from the command line too, from a profile (--elenca, --estrai) or straight from an .age archive. It is free, like restoring: no licence gate.

A trap found while testing, and it affected restoring as well. On a slow PC, or with the encryption tuned high, the encryption library refused to even try the password because it estimated it would take too long, and Densar showed that as "wrong password or corrupted archive": a good archive with the right password came back as wrong. Fixed: the limit is raised, and when the error is real it now carries the actual reason.

The guide next to the archive (the GUIDE file Densar writes beside every backup, in three languages) now also explains how to pull out a single file.

Classic backups stay free, and restoring stays free: with or without a licence, on any machine, offline.

Download: densar.exe below (~15 MB, one file: it asks whether to stay portable or install; no admin rights needed). If you are on 2.1.0 or 2.1.1, the strip at the top of the program updates you in place.

SHA256
7d666105c75a8cf05c6c3d72b1676a15874bc4949fb251c422ab8de1690532ce

Verify what you downloaded. In PowerShell, in the folder where you saved it:
Get-FileHash densar.exe

"Windows says it's suspicious": Densar is not code-signed yet, so the first run may show a warning (it can be red): it is not a virus, nothing was found in the file, it is just a new program with no download history. Click the link under the message ("More info") and then "Run anyway".

More: https://www.chrononyte.com/projects/densar/

Densar BK 2.1.1

What changed

A remote copy now has to prove itself before it gets the real name. The upload lands under a provisional name, is read back from the server, and only a byte-for-byte matching fingerprint promotes it to a real copy. Before, the promotion happened first and the check second: a corrupted upload could sit on the server dressed as a good copy, counted by rotation. The fingerprint check itself already refused to delete anything old, and that is how this was caught, on the first real run of the manual re-upload.

The resume logic learned about lazy storage. After a dropped connection, the server's reported file size can keep growing for a few seconds while its storage catches up. Densar now waits until two consecutive readings agree before resuming an upload, instead of appending against a file that is still moving. And a provisional file left over from a previous run is discarded rather than resumed: every run seals the archive afresh, so no two runs share a single byte.

A failed verification cleans up after itself. The mismatched file is removed from the server on the spot; a good retry then simply replaces whatever the earlier attempt left behind.

Classic backups stay free, and restoring stays free: with or without a licence, on any machine, offline.

Download: densar.exe below (~15 MB, one file: it asks whether to stay portable or install; no admin rights needed). If you are on 2.1.0, the strip at the top of the program updates you in place.

SHA256
b7b36750f99d12995ebec7f5493de6db71020e14f4eadb0bfd371384306bb88e

Verify what you downloaded. In PowerShell, in the folder where you saved it:
Get-FileHash densar.exe

"Windows says it's suspicious": Densar is not code-signed yet, so the first run may show a warning (it can be red): it is not a virus, nothing was found in the file, it is just a new program with no download history. Click the link under the message ("More info") and then "Run anyway".

More: https://www.chrononyte.com/projects/densar/

Densar BK 2.1.0

What changed

Updating no longer means a trip to the website. When a new version is out, a strip appears at the top of the program, whatever screen you are on, not just in Settings. One button downloads the new version with a progress bar, checks its SHA-256 fingerprint against the published one (if they do not match, nothing gets installed), swaps the program in place and restarts it. Densar is not code-signed yet, so Windows may still show its warning screen the first time the new version starts; nothing else changes.

The remote upload of a profile can be relaunched on its own. When the nightly backup makes its local archive but the connection eats the remote copy, densar --profilo <name> --solo-remoto re-uploads the latest local copy and verifies it byte for byte against the local fingerprint. It deliberately does not re-run rotation: if the previous night had already rotated, doing it again would delete one remote copy too many. Better one extra copy on the server until the next good night than one missing.

Classic backups stay free, and restoring stays free: with or without a licence, on any machine, offline.

Download: densar.exe below (~15 MB, one file: it asks whether to stay portable or install; no admin rights needed).

SHA256
7747b5933542e4a1f90447284b8a3139d0751dd3fb6d1a4d121761e0cb97f317

Verify what you downloaded. In PowerShell, in the folder where you saved it:
Get-FileHash densar.exe

"Windows says it's suspicious": Densar is not code-signed yet, so the first run may show a warning (it can be red): it is not a virus, nothing was found in the file, it is just a new program with no download history. Click the link under the message ("More info") and then "Run anyway".

More: https://www.chrononyte.com/projects/densar/