> ## Documentation Index
> Fetch the complete documentation index at: https://docs.photon.codes/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use Stable documentation by default. Honor an explicit Beta request or a URL under /docs/beta/. If the requested version conflicts with the installed CLI package or API origin, clarify the target before writing integration code.
> Pages under /docs/beta/ document Beta; other product pages document Stable. Keep the CLI package, commands, API origin, and credentials within the selected version. State the documentation version in your answer.
> For MCP search, always pass version: Stable or version: Beta. Unfiltered search mixes both versions. For filesystem reads, keep Beta queries under /beta/ and exclude /beta/ from Stable queries; discover paths before reading them.
> The public docs base is https://photon.codes/docs. Convert MCP page paths to public URLs under that base, preserving /beta/ when present. Read https://photon.codes/docs/skill.md for version selection and https://photon.codes/docs/llms.txt for the version indexes.

# addMemberSchema

> Group-membership management content.

Group-membership management content. Universal content — providers
dispatch by `content.type` in their `send` action and decide their own
support story (e.g. iMessage only supports it for remote group chats;
on a DM it surfaces an `UnsupportedError` telling the caller to create
a group via `space.create` instead).

`space.send(addMember(users))` is the canonical form; `space.add(...)`,
`space.remove(...)`, and `space.leave()` are universal sugar that
delegate here. All three are fire-and-forget — no `Message` is produced.

Bidirectional: providers also surface platform membership events as
inbound `Message`s carrying this content. `message.sender` is the acting
user — who added/removed the members — and may be `undefined` when the
platform recorded no actor. For `leaveSpace` the sender is the leaver
(the content carries no `members`). The agent's own actions are
suppressed: `space.add(...)` does not echo back as an inbound event.

Members are id strings (or `User`s, normalized to their `id`) in the same
platform handle format `space.create` accepts. No async resolution happens
in the builder — ids reach the provider verbatim.

```typescript
const addMemberSchema: z.ZodObject<{ members: z.ZodArray<z.ZodString>; type: z.ZodLiteral<"addMember"> }, z.core.$strip>
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.