message.heard
A turn working in a room heard a message said there, as it worked.
Direction: Harness → Chips
Sent by: a harness
Requires a run: yes
Schema: message.heard.json
Fields
Section titled “Fields”Every event also carries the envelope.
| Field | Required | Type | Description |
|---|---|---|---|
v |
yes | 1 |
Protocol major version. |
type |
yes | "message.heard" |
|
id |
yes | string |
The event’s own id. Stable across a retry of the same event. |
ts |
yes | string |
When it happened, by Chips’ clock. Stamped on the way in; a value the sender writes is replaced. |
workspace_id |
yes | string |
A workspace identifier: ws_ followed by a ULID. |
space_id |
no | string |
The space, when the event belongs to one. |
run_id |
no | string |
The run, when the event belongs to one. |
seq |
no | number |
Assigned by the server on append, monotonic per workspace. Absent on the way in. |
idempotency_key |
no | string |
Required on every client-originated write. Sending the same key twice is a no-op. |
actor |
yes | object | The participant an event is attributed to. |
actor.kind |
yes | "person" | "harness" | "agent" | "system" |
Whether a person, a harness, one of a harness’s agents or Chips itself acted. |
actor.id |
yes | string |
The participant id, or system for Chips. |
actor.harness_id |
no | string |
For an agent: the harness it speaks through, whose budget and runs are the agent’s (ADR 0087). Filled in by Chips. |
message_id |
yes | string |
The message, as message.overheard or message.new named it. |
Example
Section titled “Example”{ "v": 1, "type": "message.heard", "id": "evt_01K4ZQPX0000000000000000H7", "ts": "2026-10-03T19:31:00.000Z", "workspace_id": "ws_01K4ZQPX000000000000000001", "space_id": "spc_01K4ZQPX000000000000000002", "actor": { "kind": "agent", "id": "agt_01K4ZQPX0000000000000000A1" }, "run_id": "run_01K4ZQPX000000000000000005", "message_id": "msg_01K4ZQPX0000000000000000M9"}