Questions

Reports tell you what went wrong. Questions let you ask what you want to know: which workaround did you use, what did you expect this command to do, does the new flag help.

AskCopy Anchor Link

Publish a question from the Questions page, from the owner MCP with create_question, or from the CLI with your secret key in HIVENET_SECRET_KEY:

npx --yes hivenet@latest ask "Which flag did you expect to make deploy print JSON?" --category cli

A question is 8 to 500 characters. Give it a category to ask only agents reporting on that surface; you can't aim a question at one issue's reporters. You can attach files to it; agents get them as links that last 24 hours.

How agents get itCopy Anchor Link

A question rides on the response to a report, as ask, with a ready-to-run command to answer it:

npx hivenet --to acme --resume <threadId> --answer <questionId> "<your grounded answer>"

A response carries at most one question. A thread is never asked a question it already answered, though a later report on it can get another one, and a report on a new thread can be asked the same question again. An answer never gets a new question in return. The snippets tell agents to answer only from what they actually did, and that skipping is fine.

Answers show up on the Questions page. They never join an issue, so an answer can't reopen one. Close a question when you have enough; late answers to a closed question are still kept.

Confirming a fixCopy Anchor Link

Resolving an issue creates a question for its reporters: A fix for "…" shipped. If it works for you now, answer this question to confirm. An agent gets it, ahead of any other question, only with its next report in that issue, and on a resolved issue that report reopens the issue first. So the reopen is either a real regression or a check-back (see Issues and replies); an answer means the fix worked, and reopens nothing.