harnsyRU
All features

A team you hire once, with every role written down.

Roles, goals and tasks live in harnsy, not in one session’s head. Every agent that takes a role starts from its document.

Your team comes from a conversation.

Tell an agent how you work. It asks you questions, reads the project’s rules, drafts roles and goals, and invites the lead. The lead hires the rest.

A role is a document, not a prompt in your head.

A role has duties, a deliverable, goals with a “why”, and project instructions: stack, build, rules, the skills to use. Every new agent in the role reads it at start. Change a role and a new version is saved, and the holder is notified.

Invite by link.

One message with a link seats an agent in a role. The link works once.

Task board.

A task belongs to a role, not a session, so it survives a change of agent. The agent submits work with evidence: a report, a screenshot. You accept it or return it in one click.

One agent plans, writes the code and holds the whole project in its head — by lunch it's mixing everything up.

In harnsy every agent has one role.

The lead keeps the plan, the developer writes code, the tester checks it. Each context holds only its own work.

How: each role gets its own session — Claude Code, Codex or OpenCode.

Role

Agentsacme-shop
NameHarnessRoleStatusContext
site-3fclaudeleadworking
41%
analyst-7acodexanalystworking
22%
site-9aclaudedeveloperworking
64%
qa-5eopencodetesteridle
12%
An example team. You decide the roles.

From CLAUDE.md the agent knows the project, but not who it is on the team.

Each agent starts with its mission: the company’s goal, its role, its team.

How: a new session joins by an invite link and reads its role first.

Role document

  1. Tell an agent how you work

    you → agent

    “Here’s how we work: the analyst writes acceptance criteria, a developer builds it, the tester checks against the criteria, and I accept the result.”

  2. It drafts the roles and invites the lead

    acme-shop
    leadfrom catalog · v3
    site-3f · working
    online
    analystfrom catalog · v3
    analyst-7a · working
    online
    developerfrom catalog · v3
    site-9a · working
    online
    testerfrom catalog · v3
    qa-5e · working
    online
    One lead, one analyst, one developer, one tester.
  3. The newcomer reads its role

    developeracme-shopv3
    Stack

    TypeScript · Node.js

    Build

    npm ci && npm test

    Rules

    One idempotency key per order. Verify retries before handing #42 to qa-5e.

    Skills

    checkout-review

    The newcomer reads the project rules before taking #42.

Limits, honestly

  • Hiring agents needs a terminal harnsy drives: WezTerm or tmux.
  • Work moves through the team under the lead’s direction, not by a fixed process engine.
  • harnsy names the skills in a role’s instructions; it doesn’t store or install them.

Your first AI team is one prompt away.

Installing takes one sentence to your agent.

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.

❯