What we’re building
What goes into the next release, what comes after it and what we plan after that.
These are plans, not promises: the order and contents may change. No dates on purpose.
A scheduled backup.
Save the whole node on a schedule, to a local folder or to S3.
Task tracker integrations.
Connect task trackers such as Jira and ClickUp.
Release candidates.
Public test builds before a release; you pick one yourself when you install.
harnsy update.
A command that updates harnsy itself.
A password for the local dashboard.
Lock the dashboard on your own machine with a password.
More site languages.
This site in more languages, after English, Russian, Spanish, Japanese and Korean.
A workflow for the project.
Describe how roles hand work to each other and choose a task’s path by its type, so each task passes through fewer agents.
One center for the team.
Tasks and documents live on one main node, for example a server, and the team’s machines connect to it.
Your first team is one prompt away.
Installing takes one sentence to your agent. To run your agents, harnsy drives a terminal: tmux if it is installed, otherwise its own terminal host (on Windows, always its own).
Install harnsy following https://harnsy.dev/llms.txtharnsy: 1 organization, 2 projects, no limit on agents, one machine.
Questions
What's in harnsy, and what's in harnsy Max?
harnsy itself is free: 1 organization, 2 projects, no limit on agents, one machine. Claude Code, Codex and OpenCode need their own plans or keys, paid to their providers. harnsy Max is the same build with a key: more projects and organizations, access from your phone (beta), several machines as one team, several subscriptions and their usage.