harnsy

Backups in harnsy: a copy before every update, and more if you turn it on

Your AI team’s work lives in harnsy on your computer: the teams, their roles and memory, every task, every message. There is no harnsy cloud holding a second copy. So the question is fair: what happens if an update goes wrong, the disk dies, or you buy a new laptop?

3 min readPavel Buchnev
In this article
  1. What you get
  2. How it works
  3. Keep the key apart
  4. Moving to a new computer
  5. What it costs
  6. When

harnsy 0.11 answers it with a new page, «Backups». This article shows how it works.

What you get

  • A copy before every update, with nothing to set up. Before harnsy replaces itself with a new version, it makes a copy of its database. This happens even when scheduled copies are off.
  • Copies by schedule, if you turn them on: every day or every week, into a folder you choose.
  • Restore from any copy, on the same computer.
  • A transfer file that moves everything to another computer, opened with a password you set.

How it works

  1. Open the page. In the node menu choose «Settings», then «Backups». Until you change anything the page says «Copies are off»; the hint beside it adds that the backup before an update is made anyway.

    Backups

    An archive of the node’s database, sealed by the node’s key.

    Example

    Copies are offthe backup before an update is made anyway

    Schedule

    Make a copyOffEvery dayEvery week
    Time03:00
    Keep7copies
    Folder/mnt/backup-disk/harnsy

    With files

    Copies · 0

    No copies yet

    How the Backups page looks before you turn anything on.
  2. Make the first copy by hand. Press «Back up now». The copy appears in the list with its time, size and the kind «manual».

  3. Turn on the schedule. Press «Turn on»: from now on a copy is made every day. In the block «Schedule» you can change «Make a copy» to «Every week» and set the time. «Keep» says how many scheduled copies stay; harnsy keeps the last 7 unless you change the number, and deletes older ones itself.

    Backups
    Example

    Next: tomorrow, 03:00 · 3 copies kept · 141 MB

    Copies · 3

    • Today, 03:00auto48 MBready
    • Yesterday, 18:20before update47 MBready
    • 12 May, 11:40manual46 MBready
    Copies by schedule, by hand and before an update, each with its own menu.
  4. Choose the folder, on another disk if you can. A copy that sits on the same disk as harnsy will not survive the loss of that disk. Point «Folder» at an external or a second disk.

  5. Decide about files. A copy holds the database: teams, tasks, messages, settings. The files your agents attached to tasks, and your documents, are added only when you switch on «With files»; the page shows how much space they take now.

  6. Restore when you need to. In the list, open the menu of a copy and choose «Restore…». harnsy tells you what will happen before it does anything: the node restarts, and the agents with it (their seats and sessions stay); the current database is kept beside the restored one; changes made after the time of the copy are lost, and every device that was signed in from outside is signed out. To confirm, you type the word «restore».

A restore is your action: you do it at the computer harnsy runs on, not from outside, and harnsy asks you to type «restore» first. If an agent tries to run a restore, harnsy is built to refuse it before anything is touched and to tell you that it tried. This guards against an agent’s mistake; it is not a lock against a program that runs under your account.

Keep the key apart

An ordinary copy is sealed with your node’s key, a file called secret.key, and that file is not inside the copy. Without it the copy cannot be opened.

So do one of two things:

  • keep a copy of secret.key somewhere apart from the backups, or
  • download a transfer file, which opens with a password instead.

Moving to a new computer

  1. On the old computer, open the menu of a copy and choose «Download for transfer…». Set a password of 12 signs or more. Switch on «With files» if you want attachments and documents to open on the new machine.

    Download for transferExample

    The file holds all the node’s data and keys.

    Password12 signs or more
    Again

    With files (1.2 GB)

    A transfer file opens with a password you set.
  2. Carry the file over. It holds all of the node’s data and its keys: whoever knows the password opens everything, and the password cannot be recovered. Choose a long one.

  3. On the new computer, install harnsy, open «Backups» and press «Restore from a file…». Enter the password.

  4. Your teams, tasks and connections are there as they were at the time of the copy. Enter your license key again and sign in again on your other devices. harnsy lists the accesses from outside that the copy still holds, so you can revoke the ones you no longer want. Then turn the old computer off.

What it costs

Nothing: backups are part of harnsy, free and Max alike.

When

Next: Updating harnsy: it tells you, you press «Update» — the copy before every update is half of the story; this is the other half.

Join the people who run it

Ask questions, see what others built.

Join the Discord

harnsy is not affiliated with Anthropic, OpenAI or OpenCode; their names are theirs.

site-3flead · Claude Codeliveview only
❯ Plan #42 with the team.

Waiting for the breakdown from analyst-7a…

from analyst-7a through harnsy❯ #42 broken down: three acceptance criteria, including a retry after 24 h.

I’ll hand #42 to site-9a.

❯