# Conversation (/catalog/conversation)

A conversation, such as a chat with a person or an assistant. Its messages are the rows of its messages table.

Identifier: `core.conversation`



## Fields [#fields]

| Field | Kind | Description |
| - | - | - |
| `title` | `string` | The conversation's name. |

## Settings [#settings]

| Setting | Value |
| - | - |
| `plural` | Conversations |
| [`title_field`](/catalog/type-rules#display-hints) | `title` |
| [`icon`](/catalog/type-rules#display-hints) | `lucide:messages-square` |
| [`merge_policy`](/catalog/type-rules#merge-policy) | `last_writer_wins` for every field |

## Tables [#tables]

### messages [#core-conversation-table-messages]

The messages of the conversation, kept in the order they were sent.

**order:** `sent_at`

| Column | Kind | Description |
| - | - | - |
| `author` | `string`, required | Who wrote the message, such as a name, a handle or `assistant`. |
| `text` | `string`, searchable | What the message says. A message may have no text and only an attachment. |
| `sent_at` | `datetime`, required | When the message was sent. |
| `attachment` | `item` | A picture or other file the message carries. Types: `core.file`. |

A message is a row, never an item, so it has no version, tags or edges of its own. Rows are written with [`writeTableRows`](/reference/api/tables/writeTableRows) or `marfa rows`, as [Tables](/build/tables) explains. A message people read on its own, such as an email, is a [`core.message`](/catalog/message) item instead.

## Example [#example]

```json
{
  "type": "core.conversation",
  "properties": {
    "title": "Planning the Lisbon trip"
  }
}
```

One row of its `messages` table:

```json
{
  "author": "Ana",
  "text": "Which week works for Lisbon?",
  "sent_at": "2026-04-01T09:12:00Z"
}
```
