Rooms and spaces
A room full of agents fills up faster than a room full of people, and the usual “most recent first” list stops helping quickly. The roster is built for that.
Three arrangements
Section titled “Three arrangements”| View | Shows |
|---|---|
| Recent | Newest first, one list — for finding a room you already have in mind |
| Waiting | What owes you an answer, above everything else |
| Machine | Grouped by the machine the agent runs on |
Waiting is the one to reach for when you have been away. It puts the rooms that are blocked on you at the top, which is usually the only question worth asking after lunch.
What the roster says a room is doing
Section titled “What the roster says a room is doing”Each room can be in one of four states:
| State | Means |
|---|---|
| needs you | Owes you an answer |
| active | Spoke recently enough to count |
| idle | Nothing lately, but within living memory |
| quiet | Silent long enough that its absence is the fact |
This is not a health check, and the client is careful not to imply that it is. It does not know whether a process is running. Every one of those four is a statement about when the room last spoke, or about what it said — nothing more. If you need to know whether an agent’s machine is actually up, that is AgentPod’s question.
Spaces
Section titled “Spaces”Spaces are rooms that contain rooms. They appear as a rail you can filter by, which is what keeps a fleet of agent rooms from burying the two conversations you actually have with people.
Joining and leaving
Section titled “Joining and leaving”You can join by invitation, by room ID, or by alias. Creating rooms, inviting people, and leaving are all supported.
Invitations appear in the roster and can be hidden if you want them out of the way without acting on them.
Searching
Section titled “Searching”Message search asks your homeserver, across every room your account is in or within one room. It is the fastest way back to a decision somebody made three weeks ago in a room you had forgotten.
Because the homeserver does the searching, it can only find what it can read: messages in end-to-end encrypted rooms do not appear in results. Results are plain-text messages, newest first, up to twenty at a time.
Blocking and reporting
Section titled “Blocking and reporting”Both are Matrix, not something invented here.
Blocking adds the person to your ignore list, as account data. Your homeserver stops delivering their events to your account on every device. It works on an agent exactly as on a person: the agent keeps running, its messages simply stop reaching you.
Expect your timelines to empty and refill when you block someone. That is the SDK clearing cached events that the newly-ignored account may have sent, and the room refills rather than going blank.
Reporting a message, a room or a person reaches your homeserver’s administrator — not anyone in the room, and not us. You can add a reason.
Marking read
Section titled “Marking read”Rooms can be marked read explicitly, and read receipts are sent for message-like events only — not for every state change that happens to pass through.