> ## 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.

# groupSchema

> A bundles multiple messages into one logical unit (e.g.

A `group` bundles multiple messages into one logical unit (e.g. an album
of images sent together). Each item is a full `Message` — addressable by
id, reactable via `.react()`, replyable via `.reply()`.

Groups do not nest, and reactions cannot be group members. Enforced by the
`group()` builder; platforms may additionally reject unsupported item
content types at send time.

```typescript
const groupSchema: z.ZodObject<{ items: z.ZodArray<z.ZodCustom<Message<string, User, Space<unknown>>, Message<string, User, Space<unknown>>>>; type: z.ZodLiteral<"group"> }, z.core.$strip>
```


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