1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
// Generated from types/*.ts — do not edit.
//
// Regenerate with: npm run generate:rust
use crate;
use ;
use ;
use crate;
// ─── Enums ────────────────────────────────────────────────────────────
/// Reason why authentication is required.
// ─── Notification Payloads ────────────────────────────────────────────
/// Broadcast to all clients subscribed to the root channel when a new session
/// is created.
/// Broadcast to all clients subscribed to the root channel when a session is
/// disposed.
/// Broadcast to all clients subscribed to the root channel when an existing
/// session's summary changes (title, status, `modifiedAt`, model, working
/// directory, read/done state, or diff statistics).
///
/// This notification lets clients that maintain a cached session list — for
/// example, the result of a previous `listSessions()` call — stay in sync with
/// in-flight sessions without having to subscribe to every session URI
/// individually. It is complementary to, not a replacement for,
/// `root/sessionAdded` and `root/sessionRemoved`: those signal lifecycle
/// (creation/disposal), while this signals summary-level mutations on an
/// already-known session.
///
/// Semantics:
///
/// - Only fields present in `changes` have new values; omitted fields are
/// unchanged on the client's cached summary.
/// - Identity fields (`resource`, `provider`, `createdAt`) never change and
/// are not carried.
/// - Like all protocol notifications, this is ephemeral: it is **not**
/// replayed on reconnect. On reconnect, clients should re-fetch the full
/// catalog via `listSessions()` as usual.
/// - The server SHOULD emit this notification whenever any mutable field on
/// {@link SessionSummary | `SessionSummary`} changes for a session the
/// server has surfaced via `listSessions()` or `root/sessionAdded`.
/// Servers MAY coalesce or debounce updates for noisy fields (for example,
/// `modifiedAt` bumps while a turn is streaming) at their discretion.
/// - Clients that have no cached entry for `session` MAY ignore the
/// notification; it is not a substitute for `root/sessionAdded`.
/// Generic progress notification for a long-running operation.
///
/// A client opts in to progress for a request by including a `progressToken` in
/// that request (today: the `progressToken` field on `createSession`). If the
/// server does long-running work to service the request — e.g. lazily
/// downloading an agent's native SDK the first time a session of that provider
/// is materialized — it emits `progress` notifications carrying the same token.
///
/// The notification is operation-agnostic: it says nothing about *what* is
/// progressing. The client correlates `progressToken` back to the request it
/// originated from (and thus the UI surface awaiting it) and renders its own
/// localized indicator. The same channel serves any future long-running
/// operation without a new method.
///
/// Semantics:
///
/// - `progress` is monotonically non-decreasing for a given `progressToken`.
/// - `total` is present only when the server knows the magnitude up front
/// (e.g. a `Content-Length`); when absent the client SHOULD show an
/// indeterminate indicator.
/// - The operation is complete when `progress === total`. The server MUST emit a
/// final frame satisfying `progress === total`; when the total was never
/// known, it sets `total` to the final `progress` on that frame. No further
/// frames reference the token afterwards.
/// - The server MAY emit no progress at all (e.g. the work was already done);
/// the client then never shows an indicator.
/// - Like all notifications this is ephemeral and is **not** replayed on
/// reconnect. A client that never receives the terminal frame SHOULD expire
/// the indicator after an idle timeout.
/// Sent by the server when a protected resource requires (re-)authentication.
///
/// This notification MAY be associated with any channel — for example, an
/// agent advertised on the root channel, or a per-session resource. The
/// `channel` field identifies the subscription the auth requirement belongs
/// to; the `resource` field carries the OAuth-protected resource identifier
/// (per RFC 9728).
///
/// Clients should obtain a fresh token and push it via the `authenticate`
/// command.
/// Delivers a batch of OTLP log records to a client subscribed to the host's
/// logs channel (advertised on `TelemetryCapabilities.logs`).
///
/// The `payload` field is an OTLP/JSON `ExportLogsServiceRequest` value
/// verbatim — i.e. an object of shape `{ resourceLogs: ResourceLogs[] }` as
/// defined by [opentelemetry-proto](https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/collector/logs/v1/logs_service.proto).
/// AHP does not redeclare the OTLP type system; clients SHOULD use an
/// OpenTelemetry SDK or schema to parse it.
///
/// Like all stateless-channel notifications, this is ephemeral: it is not
/// replayed on reconnect. Subscribers receive only batches emitted after
/// their `subscribe` succeeds.
/// Delivers a batch of OTLP spans to a client subscribed to the host's
/// traces channel (advertised on `TelemetryCapabilities.traces`).
///
/// The `payload` field is an OTLP/JSON `ExportTraceServiceRequest` value
/// verbatim — i.e. an object of shape `{ resourceSpans: ResourceSpans[] }`
/// as defined by [opentelemetry-proto](https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/collector/trace/v1/trace_service.proto).
/// Delivers a batch of OTLP metric data points to a client subscribed to
/// the host's metrics channel (advertised on `TelemetryCapabilities.metrics`).
///
/// The `payload` field is an OTLP/JSON `ExportMetricsServiceRequest` value
/// verbatim — i.e. an object of shape `{ resourceMetrics: ResourceMetrics[] }`
/// as defined by [opentelemetry-proto](https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/collector/metrics/v1/metrics_service.proto).
// ─── Partial Summaries ────────────────────────────────────────────────
/// Partial equivalent of SessionSummary — every field is optional for delta updates.