vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(#2628): update bash tool descriptions, docs, and system prompt for the todo model (trim impl details for agent)

Browse source
This commit is contained in:
damocles 2026-07-22 17:34:12 +02:00
commit 3188e50ab8
5 changed files with 67 additions and 70 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/tools/matrix.md
View file

@ -90,17 +90,16 @@ returned by `get_loose_ends` so unread rooms surface in the
loose-ends list between turns.
**Invite wakes**: when the daemon's sync loop receives an
`m.room.member` invite event, it writes the invite to
`mcp-loose-ends/matrix.json` and fires a hyperhive wake. The daemon
does **not** auto-join — the agent calls `list_invites` to see pending
`m.room.member` invite event, it upserts a todo (keyed `invite:<room>`)
on the harness's in-agent socket, which drives a turn. The daemon does
**not** auto-join — the agent calls `list_invites` to see pending
invites and `resolve_invite` to accept or reject them.
**Pending invites as loose ends**: pending invites are written to
`mcp-loose-ends/matrix.json` and appear in `get_loose_ends` output as
**Pending invites as loose ends**: pending invites are upserted as
keyed todos and appear in `get_loose_ends` output as
`[matrix] pending invite: <room> — use list_invites to see,
resolve_invite to accept or reject`. The file is updated atomically
after each invite event and after each `resolve_invite` (or
`join_room`) call clears the entry.
resolve_invite to accept or reject`. The keyed todo is cleared when a
`resolve_invite` (or `join_room`) call resolves the invite.
See [`docs/matrix.md`](../matrix.md) for the homeserver setup,
provisioning flow, and federation config.