session.renamed

What a visit is called, in the harness’s own words (ADR 0040).

Direction: Harness → Chips
Sent by: a harness
Requires a run: no
Schema: session.renamed.json

Fields

Every event also carries the envelope.

Field	Required	Type	Description
v	yes	1	Protocol major version.
type	yes	"session.renamed"
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.
session_ref	yes	string	The harness’s own name for one visit, prefixed by the kind of harness.
title	yes	string	What to call this visit on screen. A harness that names its sessions sends this when the name changes and not otherwise; a visit with no name is shown by where it is running instead.

Example

{
  "v": 1,
  "type": "session.renamed",
  "id": "evt_01K4ZQPX0000000000000000S3",
  "ts": "2026-09-07T09:12:00.000Z",
  "workspace_id": "ws_01K4ZQPX000000000000000001",
  "space_id": "spc_01K4ZQPX000000000000000002",
  "idempotency_key": "scout:3f9c1a-named-1",
  "actor": {
    "kind": "harness",
    "id": "hrn_01K4ZQPX000000000000000004"
  },
  "session_ref": "scout:3f9c1a",
  "title": "Sync spec flakes"
}