harnsy

harnsy MaxSince 0.9.0

Take your whole team setup with you.

Available since harnsy 0.9.0.

Export your company to a file, and import it on another machine or for another person. The file carries the company with its projects and teams: roles (the company’s role templates and each project’s own changes to them), documents and goals. It carries no secrets, no agent sessions and no tasks.

This machine

Acme

~/work/acme

billing · website

Press Export: the organization becomes one .zip file.

In the file

  • projects and teams
  • roles: the company’s templates and each project’s changes
  • documents and goals
  • a manifest of what is inside
  • folders as labels, not paths

Not in the file

  • secrets: keys, tokens, invites
  • agent sessions
  • tasks and their history
Exporting a company: what goes into the zip file and what stays out. Sample data.

One zip file for the whole company.

Press Export on a company (the dashboard calls it an organization) and harnsy writes one zip file, with a manifest that lists what is inside: the projects and teams, their roles (the company’s templates and each project’s own changes), documents and goals.

Folders become labels.

The file does not carry the folder paths of your machine. Each project folder and the root folder become a label, so the file means the same thing on any machine.

What stays out.

The file holds no secrets, no agent sessions, and no tasks or their history. You can send it to another person without handing over keys or your work.

Another machine

Import organization

Archive (.zip)acme-organization.zip

A file from Export, on this machine or another. It becomes a new organization; nothing existing changes.

In the file: projects 2, roles 9, teams 2, goals 3, documents 7.

Folders on this machine

Give each project a folder that exists.

2 folders of the machine the file came from, outside the organization

Prompts and documents mention these folders of the machine the file was exported from. None of the organization’s folders covers them. They are imported as they are; this machine may not have them.

  • /home/pavel/notes3 mentions
  • /opt/shared/brand1 mention

The import changes

  • team website → website-2
Importing: the preview, a folder for each label, then everything applied at once. Sample data.

A preview first, then one go.

Import shows a preview of the file. You map each label to a folder on this machine and settle any name that already exists. Then everything is applied in one transaction: all together, or not at all.

Only you can do it.

Export and import are done by the person at the dashboard. Agents cannot export or import a company.

A harnsy Max key turns it on.

harnsy Max

Export / Import is part of harnsy Max.

Limits, honestly

  • Prompts and documents can name folders outside the company. Import warns you how many there are; they come along as written, and this machine may not have them.
  • Tasks and their history do not move with the file.

Your first team is one prompt away.

Installing takes one sentence to your agent. To open agents for you, harnsy drives a terminal: tmux on Linux and macOS, its own terminal host on Windows.

Install harnsy following https://harnsy.dev/llms.txt
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.

❯