harnsy

Assign who answers what, and your agent asks that person

Until now every question your agents asked came to one person: you. In harnsy v0.10.0 a post in your project can belong to someone else. The agent asks that person, only they can answer, and the work waits for them. Here is how to set it up, and what happens when they do not answer.

4 min readPavel Buchnev

Key points

1
person can answer a question about a given post: the one who holds it
24 h
how long the question waits for them by default, then it goes to you
v0.10.0
the version where this ships
In this article
  1. One question, one person
  2. How to assign
  3. In a group
  4. Only that person answers, and it is information
  5. If they do not answer
  6. What stays the same

One question, one person

Take a post in your project, for example “lawyer”. In harnsy you can now give that post to one teammate who is linked in Telegram or Discord.

When an agent of the project has a question for that post, it asks that person, in their private chat with the bot. Not you, and not everyone. The buttons and the free-text answer work the way they do for you today. The question travels through Telegram or Discord, so that service’s own rules apply to the message too. How we handle your data →

How to assign

Four steps, all in the dashboard:

  • Open Connections, and in it the card of the person. They have to be a Telegram or Discord member linked to your node.
  • Find the block “Posts of {name} in the project”.
  • Type the post, for example “lawyer”.
  • Press “Give the post”.

From then on, the project’s agents ask that person about that post. Start with one real question: the last time an agent waited for a person. Name who should have answered it, and give that post to them.

In a group

A question can also go to a group chat. In the group’s settings in Connections, you tick “Agents may ask the project’s posts here”. Then everyone in the group sees the question, with the name of the person it is for. Only that person can answer. If someone else taps a button, it does not count.

Only that person answers, and it is information

A name on a question would only be an address. Here it is also a check on who answered: the agent keeps waiting for the person it asked.

What the person says is information for the agent. It is not your decision as the owner. If a decision is yours, it stays yours.

If they do not answer

A question cannot wait forever. If the person has not answered in 24 hours, the question goes to you, the owner, in “Needs you” (and to your phone, if you have set up notifications). The same happens if you remove the post or unlink the person. So the work does not stand still because someone is on holiday.

The 24 hours is the default. It is a setting of the node, from 10 minutes to 168 hours, and it is not in the dashboard yet.

What stays the same

The agent still asks with buttons and still waits. You are still the owner, and a question for a post that nobody holds still comes to you.

Tell your agents who answers what

harnsy connects your Claude Code, Codex and OpenCode agents into one team with roles. In v0.10.0 a post can belong to a person.

Install harnsy

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.

❯