@theokit/presenter 0.6.0 → 0.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +78 -0
- package/dist/chunk-Z4QWC7IK.js +7 -0
- package/dist/chunk-Z4QWC7IK.js.map +1 -0
- package/dist/{chunk-schema-PuUWBfl_.d.ts → chunk-schema-DXlG0Qv4.d.ts} +27 -2
- package/dist/index.d.ts +40 -2
- package/dist/index.js +302 -67
- package/dist/index.js.map +1 -1
- package/dist/wire/index.d.ts +23 -3
- package/dist/wire/index.js +164 -38
- package/dist/wire/index.js.map +1 -1
- package/package.json +26 -13
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2026 usetheo.dev
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,78 @@
|
|
|
1
|
+
# `@theokit/presenter`
|
|
2
|
+
|
|
3
|
+
The presentation layer: **one normalized agent-output event, N surfaces.**
|
|
4
|
+
|
|
5
|
+
Agent output has to reach a web stream, a terminal, and a JSON API. Translating the runtime's
|
|
6
|
+
messages separately for each of them gives you N×M translators that drift — the terminal grows a
|
|
7
|
+
tool-call rendering the web never gets, and a new SDK event lands in one path only.
|
|
8
|
+
|
|
9
|
+
This package is the narrow waist that removes the multiplication. Every **source** translates
|
|
10
|
+
*into* `AgentOutputEvent`; every **presenter** translates *out of* it.
|
|
11
|
+
|
|
12
|
+
```
|
|
13
|
+
SDK message ─┐ ┌─→ UIMessageStreamPresenter → web
|
|
14
|
+
├─→ AgentOutputEvent ────┼─→ TerminalPresenter → ANSI rows
|
|
15
|
+
wire chunk ──┘ └─→ JsonPresenter → records
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
The variants are derived from the runtime's own discriminants, never from one surface's wire
|
|
19
|
+
format — so no surface leaks into the contract.
|
|
20
|
+
|
|
21
|
+
## Install
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
pnpm add @theokit/presenter
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
Peers: `@theokit/sdk` and `zod`.
|
|
28
|
+
|
|
29
|
+
## The canonical event
|
|
30
|
+
|
|
31
|
+
Eight variants, discriminated on `type`:
|
|
32
|
+
|
|
33
|
+
| Variant | Carries |
|
|
34
|
+
|---|---|
|
|
35
|
+
| `text` | assistant text output, streamed or whole |
|
|
36
|
+
| `reasoning` | thinking content, distinct from user-visible text |
|
|
37
|
+
| `tool-call` | a tool invocation with its committed input |
|
|
38
|
+
| `partial-tool-call` | incremental tool input while the model streams the args |
|
|
39
|
+
| `tool-result` | the result for a `callId`, with `isError` for failures |
|
|
40
|
+
| `status` | run-level status |
|
|
41
|
+
| `error` | a failed turn |
|
|
42
|
+
| `finish` | the end of the turn plus its metadata |
|
|
43
|
+
|
|
44
|
+
## Sources and presenters
|
|
45
|
+
|
|
46
|
+
```typescript
|
|
47
|
+
import { fromSdkMessage, TerminalPresenter } from '@theokit/presenter'
|
|
48
|
+
|
|
49
|
+
const presenter = new TerminalPresenter()
|
|
50
|
+
for (const message of sdkMessages) {
|
|
51
|
+
for (const event of fromSdkMessage(message)) {
|
|
52
|
+
for (const row of presenter.present(event)) render(row)
|
|
53
|
+
}
|
|
54
|
+
}
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
`fromWireChunk` is the other door — from the transport wire into the canonical event, which is what
|
|
58
|
+
a client-side surface receives. `fromInteractionUpdate` covers interactive runs.
|
|
59
|
+
|
|
60
|
+
A `Presenter<TOut>` is `surface` + `present(event)`, with optional `start()` / `finish()` framing for
|
|
61
|
+
stateful surfaces. `UIMessageStreamPresenter` holds open-block state and is therefore instantiated
|
|
62
|
+
**per stream**; `TerminalPresenter` and `JsonPresenter` are stateless and may be singletons.
|
|
63
|
+
`PresenterRegistry` resolves one by surface key and throws a typed `UnknownPresenterError` when the
|
|
64
|
+
key is unknown — never a silent fallback.
|
|
65
|
+
|
|
66
|
+
`foldTurnLifecycle` collapses a turn's events into a `TurnLifecycle` when a surface wants the
|
|
67
|
+
outcome rather than the stream.
|
|
68
|
+
|
|
69
|
+
## Subpaths
|
|
70
|
+
|
|
71
|
+
| Subpath | What lives there |
|
|
72
|
+
|---|---|
|
|
73
|
+
| `.` | The event, the `Presenter` contract, the registry, the sources, the three presenters |
|
|
74
|
+
| `./wire` | The wire-format types shared with transports |
|
|
75
|
+
|
|
76
|
+
## Licence
|
|
77
|
+
|
|
78
|
+
Apache-2.0 — see `LICENSE`.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"sources":[],"mappings":"","names":[]}
|
|
@@ -119,7 +119,7 @@ type WireChunk = z.infer<typeof fixedChunkSchema> | WireDataPart;
|
|
|
119
119
|
/**
|
|
120
120
|
* The literal discriminators this package speaks, in declaration order.
|
|
121
121
|
*
|
|
122
|
-
*
|
|
122
|
+
* diffs this list against the `ai` union to notice a variant that
|
|
123
123
|
* appeared upstream and that we have not mirrored. It is exported (rather than derived at the call
|
|
124
124
|
* site) so the gate and the schema cannot drift apart — a gate comparing a stale list is a gate
|
|
125
125
|
* whose verdict means nothing.
|
|
@@ -127,5 +127,30 @@ type WireChunk = z.infer<typeof fixedChunkSchema> | WireDataPart;
|
|
|
127
127
|
declare const WIRE_CHUNK_TYPES: readonly string[];
|
|
128
128
|
/** `data-*` parts are matched by shape, not by an enumerated name — the family is open by design. */
|
|
129
129
|
declare const WIRE_DATA_PART_PREFIX = "data-";
|
|
130
|
+
/**
|
|
131
|
+
* The `data-*` part that says WHAT a `tool-approval-request` is asking — usetheokit/theokit#394.
|
|
132
|
+
*
|
|
133
|
+
* `{ type: 'data-approval', data: { approvalId, question?, timeoutMs? }, transient: true }`, emitted
|
|
134
|
+
* immediately before the approval frame it describes. The reader folds it into the same tool part,
|
|
135
|
+
* under `approval`, so a consumer never sees it as a part of its own.
|
|
136
|
+
*
|
|
137
|
+
* ## Why a `data-*` part and not two more fields on the approval frame
|
|
138
|
+
*
|
|
139
|
+
* Because the approval frame is shared vocabulary and `ai`'s validator for it is strict — see the
|
|
140
|
+
* note on that variant above. `data-*` is the one arm of this union that is open by contract on
|
|
141
|
+
* BOTH sides: `ai` validates `data-${string}` with an arbitrary payload, and `transient: true`
|
|
142
|
+
* makes its reader discard the part rather than render it. Measured against `ai@7.0.14`: the frame
|
|
143
|
+
* parses, the transcript is byte-identical with and without it, and the approval still reconstructs
|
|
144
|
+
* as `state: 'approval-requested'`. So the extension costs an ai client nothing and costs ours a
|
|
145
|
+
* lookup.
|
|
146
|
+
*
|
|
147
|
+
* The precedent is `data-checkpoint`, which carries a framework signal the same way and for the
|
|
148
|
+
* same reason (`render-terminal.ts`: "a FRAMEWORK signal carried as a `data-*` part, not agent
|
|
149
|
+
* output").
|
|
150
|
+
*
|
|
151
|
+
* Exported so the producer (`@theokit/agents`) and the reader name it once. Two ends agreeing on a
|
|
152
|
+
* string literal by coincidence is how a wire silently stops carrying something.
|
|
153
|
+
*/
|
|
154
|
+
declare const WIRE_APPROVAL_DETAIL_PART = "data-approval";
|
|
130
155
|
|
|
131
|
-
export { type WireChunk as W,
|
|
156
|
+
export { type WireChunk as W, WIRE_APPROVAL_DETAIL_PART as a, WIRE_CHUNK_TYPES as b, WIRE_DATA_PART_PREFIX as c, type WireDataPart as d, wireChunkSchema as w };
|
package/dist/index.d.ts
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
import { InteractionUpdate } from '@theokit/sdk';
|
|
2
|
-
import { W as WireChunk } from './chunk-schema-
|
|
2
|
+
import { W as WireChunk } from './chunk-schema-DXlG0Qv4.js';
|
|
3
3
|
import 'zod';
|
|
4
4
|
|
|
5
5
|
/**
|
|
@@ -155,6 +155,23 @@ declare function fromSdkMessage(msg: SdkMessage): AgentOutputEvent[];
|
|
|
155
155
|
*/
|
|
156
156
|
declare function fromInteractionUpdate(update: InteractionUpdate): AgentOutputEvent[];
|
|
157
157
|
|
|
158
|
+
/**
|
|
159
|
+
* Translate one wire frame into canonical events.
|
|
160
|
+
*
|
|
161
|
+
* @param chunk one validated frame of the wire
|
|
162
|
+
* @param toolNames callId → tool name, threaded by a stateful caller.
|
|
163
|
+
*
|
|
164
|
+
* The second argument exists because the wire genuinely does not carry the name:
|
|
165
|
+
* `tool-output-available` has `toolCallId` and `output` and nothing else, while the name appears
|
|
166
|
+
* only on the earlier `tool-input-available`. Every consumer that renders tool results therefore
|
|
167
|
+
* keeps this map — including the one this function replaces. Threading it is honest; inventing the
|
|
168
|
+
* name here would not be.
|
|
169
|
+
*
|
|
170
|
+
* Without the map a result still maps, and says the name is unknown. Dropping it would lose a real
|
|
171
|
+
* result, and an empty name would render as a line the operator cannot connect to anything.
|
|
172
|
+
*/
|
|
173
|
+
declare function fromWireChunk(chunk: WireChunk, toolNames?: ReadonlyMap<string, string>): AgentOutputEvent[];
|
|
174
|
+
|
|
158
175
|
/**
|
|
159
176
|
* The frame type is TheoKit's own since the `remove-ai-dependency` plan; it is structurally the
|
|
160
177
|
* ai-sdk `UIMessageChunk`, so the emitted wire is unchanged and an ai-sdk client still reads it.
|
|
@@ -188,9 +205,30 @@ interface TurnMetadata {
|
|
|
188
205
|
readonly durationMs?: number;
|
|
189
206
|
readonly cost?: number;
|
|
190
207
|
}
|
|
208
|
+
/**
|
|
209
|
+
* What the browser is told a failure was (usetheokit/theokit#390).
|
|
210
|
+
*
|
|
211
|
+
* Scoped to THIS presenter on purpose: `terminal` and `json` render for the operator's own console
|
|
212
|
+
* and their own process, where masking would remove the text from the one place it belongs. This
|
|
213
|
+
* one produces the browser's copy, and that is the copy the default protects.
|
|
214
|
+
*/
|
|
215
|
+
type MaskError = (error: {
|
|
216
|
+
message: string;
|
|
217
|
+
code?: string;
|
|
218
|
+
}) => string;
|
|
191
219
|
interface UIMessageStreamPresenterOptions {
|
|
192
220
|
/** A single shared id for every text block — injected for deterministic tests (D3). */
|
|
193
221
|
readonly textId: string;
|
|
222
|
+
/**
|
|
223
|
+
* Masks a failure's text before it reaches the browser. Defaults to a fixed string.
|
|
224
|
+
*
|
|
225
|
+
* Applied to a TOOL failure as well as a run's, and that is not an oversight. This presenter is
|
|
226
|
+
* DOWNSTREAM of the SDK loop: the model's copy of a tool result travelled inside that loop and
|
|
227
|
+
* has already been consumed, so masking here costs the model nothing and protects the only copy
|
|
228
|
+
* that reaches a browser. Two different defaults for "server text reaching a browser" would be a
|
|
229
|
+
* rule nobody could remember.
|
|
230
|
+
*/
|
|
231
|
+
readonly onError?: MaskError;
|
|
194
232
|
}
|
|
195
233
|
declare class UIMessageStreamPresenter implements Presenter<UIMessageChunk> {
|
|
196
234
|
#private;
|
|
@@ -359,4 +397,4 @@ interface TurnLifecycle<E> {
|
|
|
359
397
|
*/
|
|
360
398
|
declare function foldTurnLifecycle<E>(vocabulary: LifecycleVocabulary<E>, threadId: string): TurnLifecycle<E>;
|
|
361
399
|
|
|
362
|
-
export { AGENT_OUTPUT_EVENT_TYPES, type AgentErrorEvent, type AgentFinishEvent, type AgentOutputEvent, type AgentOutputEventType, type AgentPartialToolCallEvent, type AgentReasoningEvent, type AgentStatusEvent, type AgentTextEvent, type AgentToolCallEvent, type AgentToolResultEvent, type ContentChunk, JsonPresenter, type JsonPresenterOptions, type JsonRecord, type LifecycleItem, type LifecycleVocabulary, type Presenter, PresenterRegistry, type SdkMessage, TerminalPresenter, type TerminalPresenterOptions, type TerminalRow, type TurnLifecycle, type TurnMetadata, type TurnOutcome, UIMessageStreamPresenter, type UIMessageStreamPresenterOptions, UnknownPresenterError, foldTurnLifecycle, fromInteractionUpdate, fromSdkMessage, isErrorEvent, isFinishEvent, isPartialToolCallEvent, isReasoningEvent, isStatusEvent, isTextEvent, isToolCallEvent, isToolResultEvent };
|
|
400
|
+
export { AGENT_OUTPUT_EVENT_TYPES, type AgentErrorEvent, type AgentFinishEvent, type AgentOutputEvent, type AgentOutputEventType, type AgentPartialToolCallEvent, type AgentReasoningEvent, type AgentStatusEvent, type AgentTextEvent, type AgentToolCallEvent, type AgentToolResultEvent, type ContentChunk, JsonPresenter, type JsonPresenterOptions, type JsonRecord, type LifecycleItem, type LifecycleVocabulary, type MaskError, type Presenter, PresenterRegistry, type SdkMessage, TerminalPresenter, type TerminalPresenterOptions, type TerminalRow, type TurnLifecycle, type TurnMetadata, type TurnOutcome, UIMessageStreamPresenter, type UIMessageStreamPresenterOptions, UnknownPresenterError, foldTurnLifecycle, fromInteractionUpdate, fromSdkMessage, fromWireChunk, isErrorEvent, isFinishEvent, isPartialToolCallEvent, isReasoningEvent, isStatusEvent, isTextEvent, isToolCallEvent, isToolResultEvent };
|