buddyboss/manage-thread changes a thread’s state for one participant: read state, starring and archiving.
All three are per-person, which is why user_id is not optional.
At a glance
| Ability | buddyboss/manage-thread |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Messages |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
State belongs to a person, not a thread
A thread is never read in itself. It is read by somebody — and unread by everybody else. The same applies to starring and archiving.
So every call here names whose view is being changed, and changing another member’s state alters what their inbox shows them without notifying them.
Marking a thread read on somebody’s behalf is a reliable way to make them miss it. The unread badge is what brings people back to a conversation, and clearing it removes the only prompt they had.
Archiving is the gentler version: the thread leaves the main view but the member can still find it, and nothing about it is destroyed.
That makes archiving the reversible way to get a thread out of somebody’s way, as against buddyboss/delete-thread which removes it from their mailbox entirely.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
thread_id | integer | Yes | The thread. |
user_id | integer | Yes | Whose record this is. Required rather than defaulting, so an administrator’s own account is never acted on by accident. |
read | boolean | No | The read state you want for this member. |
starred | boolean | No | The starred state. |
archived | boolean | No | The archived state. |
What comes back
| Name | Type | What it is |
|---|---|---|
thread_id | integer | The thread. |
state | object | The member’s state for it afterwards. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Archive that thread for this member.
It resolves to one call:
{
"ability": "buddyboss/manage-thread",
"parameters": {
"thread_id": 512,
"user_id": 44,
"archived": true
}
}Worth knowing
- Every state here belongs to one participant, not to the thread.
- Marking read on somebody’s behalf removes the prompt that would have brought them back.
- The member is not told.
- Archiving is the reversible way to clear a mailbox.
Related abilities
- BuddyBoss Delete Message Thread — the irreversible version
- BuddyBoss List Message Threads — see the unread counts
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category