# chat extension

> Source: https://openwop.dev/spec/v2/ext/chat/ · OpenWOP, the open-source protocol for multi-agent workflow orchestration. CC BY 4.0.

> **Status: Stable.**

`chat` names a host service that posts messages and cards into a host-established chat session. It is a discovery-only reservation: v2 defines no portable operations or payload contract for it.

| Field | Value |
| --- | --- |
| **witness:** | `claims-check` |
| **technical:** | `stable` |
| **adoption:** | `multi-witness` |
| **last witnessed:** | `myndhyve-2.46.13-c8d511d84.json` — MyndHyve's legacy `workflow-runtime` (tier 2), suite 2.46.13, 2026-10-16; the host retired 2026-10-29 |
| **peer-dependency id** | `chat` |
| **advertised as** | `extensions.<org>.chat` |
| **declared facets** | none defined |

## Contract boundary

A host MAY advertise `chat` as `extensions["<org>.chat"]`, where `<org>` is its registered organization ([capabilities.md §3.2](https://openwop.dev/spec/v2/core/capabilities.html)). The record is organization-defined, so:

- a client MUST NOT infer portable operations, payloads, or authorization semantics from its presence;
- a pack may name `chat` as a dependency only when the host and pack share an out-of-band definition of it.

## Conformance

The `claims-check` witness checks only that the discovery claim is well formed, not runtime behavior. `conformance/src/scenarios/v2-ext-family-claims.test.ts` records it under `openwop.family.chat`:

- the key `<org>.chat` matches `extensionsKeyPattern`, and `<org>` is registered and not reserved;
- the record is a JSON object;
- `chat` is not also a member of the discovery root.

A host that does not advertise the family records `inapplicable`. A `Stable` label on this page therefore means a host at evidence tier 2 or better advertises the reservation correctly. It does not mean two hosts interoperate on it ([`../README.md`](https://openwop.dev/spec/v2/ext/README.html)).

*Sources: RFC 0144.*