# Rooms messages reactions subscribe

Use the `ably rooms messages reactions subscribe` command to subscribe to message reactions in a chat room.

## Synopsis

<Code>

### Shell

```
ably rooms messages reactions subscribe <room-name> [options]
```
</Code>

## Arguments

### `room-name`  **(Required)**

The name of the chat room to subscribe to message reactions in.

## Options

### `--raw` 

Get raw events instead of summaries. Defaults to `false`.

### `--duration | -D` 

The duration in seconds to subscribe for before automatically unsubscribing.

### `--client-id` 

A client ID to use for the subscription.

### `--json` 

Output results as compact JSON. Mutually exclusive with `--pretty-json`.

### `--pretty-json` 

Output results in formatted JSON. Mutually exclusive with `--json`.

### `--verbose | -v` 

Enable verbose logging. Can be combined with `--json` or `--pretty-json`.

## Examples

Subscribe to message reactions in a room:

<Code>

### Shell

```
ably rooms messages reactions subscribe my-room
```
</Code>

Subscribe and get raw events:

<Code>

### Shell

```
ably rooms messages reactions subscribe my-room --raw
```
</Code>

Subscribe to room message reactions in JSON format:

<Code>

### Shell

```
ably rooms messages reactions subscribe my-room --json
```
</Code>

Subscribe to room message reactions in formatted JSON:

<Code>

### Shell

```
ably rooms messages reactions subscribe my-room --pretty-json
```
</Code>

## See also

* [Rooms](https://ably.com/docs/cli/rooms.md) — Explore all `ably rooms` commands.
* [CLI reference](https://ably.com/docs/cli.md) — Full list of available commands.

## Related Topics

- [send](https://ably.com/docs/cli/rooms/messages/reactions/send.md): Send a reaction to a message in an Ably Chat room using the CLI.
- [remove](https://ably.com/docs/cli/rooms/messages/reactions/remove.md): Remove a reaction from a message in an Ably Chat room using the CLI.

## Documentation Index

To discover additional Ably documentation:

1. Fetch [llms.txt](https://ably.com/llms.txt) for the canonical list of available pages.
2. Identify relevant URLs from that index.
3. Fetch target pages as needed.

Avoid using assumed or outdated documentation paths.