threadHistory config (which exists
to backfill thread context for adapters that lack server-side history APIs).
The Transcripts API is keyed by a resolved cross-platform user key and is
intended for transcript-style use cases (LLM context building, audit).
Methods
append()
- For Message:
userKeyis read from the Message instance (set by the SDK during inbound dispatch via the configured IdentityResolver). No-op if the Message has nouserKey(resolver returned null). - For AppendInput:
options.userKeyis required.
Parameters
Message<unknown> | AppendInput
required
Type:
MessageAppendInputReturns
TranscriptEntry
count()
Parameters
required
Returns
Promise<number>
delete()
Parameters
required
Returns
Promise<{ deleted: number }>
list()
query.limit (default 50).
Pagination is intentionally not supported — the store keeps at most
transcripts.maxPerUser entries per user. To widen the window, raise
maxPerUser; to fetch a different slice, narrow with threadId /
platforms / roles.
Parameters
Returns
TranscriptEntry