Notable customer-visible changes to the Moss SDK (@viamoss/moss-sdk) and the
Moss dashboard. From v0.13.0, the SDK version tracks the Moss platform version.
0.16.26 — 2026-11-18
SDK only: @viamoss/moss-sdk 0.16.26 is on npm. There are no new server
images or Helm chart. SDK 0.16.26 works with a 0.16.25 server, and hosted Moss
is unchanged.
Fixed
The Next button beside the chat input on guide steps is now as tall as the
input and lines up with it. Before, it was slightly shorter and sat a few
pixels lower than the input box.
0.16.24–0.16.25 — 2026-11-16
0.16.24 and 0.16.25 are described together. 0.16.24 wasn’t published to npm
or rolled out to hosted Moss, so the SDK and hosted Moss go from 0.16.23
straight to 0.16.25. 0.16.24’s self-hosted images and Helm chart were
published, but install 0.16.25 instead.
Added
New appearance settings. All of them are optional, and set under
appearance.chrome in your integration’s code; none is in the dashboard.
Unset, nothing looks different.
relatedArticles.variant: 'list' shows the related articles under an
answer as plain rows, with titles in the primary text color, a small
sentence-case “Related articles” label and a document icon in the primary
color. 'cards', the default, keeps the bordered cards.
guideOffer.label and guideOffer.icon: the text and icon of the button
that offers a guide. The icon is 'emoji' (🚀, the default), 'outline'
(an outline rocket in the button’s text color) or 'none'.
message.paragraphGap: the space between paragraphs, lists and other
blocks in an answer, as a CSS length. Unset, they sit directly on one
another.
startScreen.queryIcons: your own icon for each built-in
suggested-question icon name. Every question uses document unless
zeroState.suggestedQueryIcons is 'per-query'. A name without an entry
keeps the built-in icon.
startScreen.queryFontWeight, queryGap, articlesPaddingX and
articlesRowGap: the weight of the suggested questions and the gap
between them, and the side padding of the recommended articles and the gap
between their rows.
inputBar.paddingY and inputBar.lineHeight: the input text’s top and
bottom padding, and its line height as a number ('1.5'), a length
('20px') or a percentage ('150%').
inputBar.focusBorder: the input’s border color while it has focus.
icon on the footer links: 'external-link', 'ticket', 'none', or
your own element, such as an inline SVG. The Help center icon follows its
label, and the Open a ticket icon precedes it. Unset, Help center keeps
”↗” and Open a ticket has no icon.
guide.pageTint: dims the page around a guide’s highlight. true lays a
36% dark tint over it. An object sets color, opacity (0 to 1), or
both. The chat never dims, clicks still reach the page, and an open modal
dialog stays clear. The tint holds through step changes and lifts on a
step with nothing highlighted. Off by default.
guide.targetBadges: 'step' numbers the highlight’s badge
with the guide’s step number, as in the guide bar. Every target of a step
shows that same number, so several targets don’t read as separate steps,
and targets in one group, such as a row of tabs, share one badge.
'within-step', the default, keeps today’s numbering.
guide.nextInBar: false moves Next from the guide bar to
beside the input box. Next moves beside the input on every step, click
steps included, and hides while Moss works and once the guide is finished.
The guide bar then shows only the plan and its progress, and the chat’s
step loader shows that Moss is working. Unset or true, the default,
keeps the guide bar’s Next. With both
nextInBar and nextBesideInput set to false there’s no Next at all,
and development builds warn in the console.
loader: 'steps' shows a short list of what Moss is doing
while it works, such as “Reading the page” and “Planning the next step”.
Screen readers hear the row in progress, except while the guide bar is
already announcing “Working…”. 'line', the default, keeps the one-line
indicator.
Next beside the input box. On a guide step with nothing to click, and on
file-upload and confirmation steps, Next also shows beside the input box.
Other click steps look the same as before, and it doesn’t show once the
guide is finished. The guide bar’s Next stays. To keep Next only in the
guide bar, set chrome.guide.nextBesideInput: false.
Self-hosted: Zendesk calls through a proxy. A new backend setting,
ZENDESK_USE_ENV_PROXY, is off by default. When it’s on, Moss’s Zendesk
calls (connecting, syncing the ticket form and filing tickets) go through the
http:// proxy named in HTTPS_PROXY. A value without a scheme, such as
proxy.example.com:3128, is read as http://, and NO_PROXY is honoured.
An https:// or malformed proxy value isn’t used: the request isn’t sent,
and the sync banner or the connection check says this server couldn’t reach
Zendesk through the proxy. With the setting off, nothing changes.
Changed
You can type while Moss answers. The input stays editable during a
reply. Send and Enter wait until the reply has arrived, and the text stays
in the box. The input is disabled only while the connection is down.
Next sends what you typed. With text in the input, a guide’s Next sends
it as your message. With an empty input, Next goes to the next step, as
before.
No related articles while a guide runs. Replies during a running guide
don’t show the related-articles list. The answer that offers the guide keeps
it. Sources that your application’s instructions ask for in the answer text
are unchanged.
The guide bar shows when Moss is working. While a request runs, a spinner and “Working…” take
Next’s place, and screen readers announce it. When the request ends, Next
comes back, with the focus if it had it.
The guide offer’s default label is “Start guide”, and it’s translated.
It was “Guide me”, in English for every user. Korean users now see 가이드
시작.
One line of input text is centred on the send button. When
chrome.inputBar is set, in code or in the dashboard, the send button sits a
few pixels higher. With several lines, it stays level with the last one.
Zendesk connection errors name the cause. With host-brokered filing,
when Test & connect or Test connection can’t read the end-user ticket
form, the message now says why: the HTTP status, a DNS failure, a timeout, a
TLS failure, a failed connection, or a reply that isn’t a ticket form. A 404
also asks you to check the subdomain. Zendesk’s reply itself is never shown.
Zendesk sync errors name the cause too. When a ticket-form sync fails,
the “Last sync had a problem” banner, in Configure > Integrations > Zendesk
and on the Ticket intake page, now says why: the HTTP status Zendesk
answered, a DNS failure, a timeout, a TLS failure, a failed connection, or a
reply that couldn’t be read. It no longer shows text from Zendesk’s reply.
Guide steps and guide offers.
When a step only asks the user to check something, such as a setting or a
status, and the page shows the check passing, Moss says so and gives the
next step in the same reply. If the page shows something else, Moss says
what it shows and stays on the step.
Choices on the page, such as radio buttons, selects and links, are
highlighted, and the user’s pick moves the guide on.
A step with nothing to click ends by pointing to Next, without saying
where Next is on the screen.
Moss treats a “where is…” question as a how-to. When the answer lists
several places in your application, Moss names the most common one and
offers a guide there. Questions about places outside your application get
no offer. The offer is the answer’s last sentence, before any Sources list
your instructions ask for.
Browser extensions send the SDK version they bundle, so they get the
current guide behavior. Extension builds sent no SDK version, so their
sessions got the older guide behavior whatever the application’s
stateless_turn_policy setting said. Every extension built from this release
sends it. Once its new build is installed:
Ending a guide in the chat ends it for Moss too, so the next question
isn’t answered inside the guide the user left. That covers closing the
chat when closingChatEndsGuide is on, and filing a support ticket during
a guide.
Asking Moss to stop (“stop guiding me”, “exit the guide”) ends the guide.
A guide with no progress ends on its own: after 2 hours if it was only
offered, after 24 hours if it was running.
Moss decides on each question whether to answer it or guide, instead of
keeping the mode an earlier question set.
An extension switches only when its new build is installed. Pages that load
a released SDK from npm or the CDN already had this behavior. An application
with stateless_turn_policy: false keeps the older behavior.
SDK pre-releases get the current guide behavior. A pre-release of any
version after 0.10.0, such as 0.17.0-beta.3, is now treated like a release.
A page that loads one switches when the backend is upgraded, with no new
install. Before, every pre-release got the older behavior. A pre-release of
0.10.0 itself still does.
Several highlighted places are named, not numbered. With
guide.targetBadges: 'step', every highlight of a step shows the step’s
number. When a guide step highlights more than one place, Moss’s reply now
names each one (“Click Search or Share”) instead of numbering
them 1, 2, 3. This needs the SDK from this release. It also covers the
reply that starts a guide and highlights its first step.
No database migrations in this release.
Fixed
A guide’s Exit button is back. Open the guide bar’s step list: “Exit
guide” is at the end of it, and asks before it ends the guide. Exiting
removes the guide’s highlight, and Moss ends the guide too.
After a guide’s Exit, clicking the element its step highlighted no longer
sends the step.
After pressing Next, clicking the highlighted element no longer sends the
step a second time. If Next’s request fails, the step comes back, so Next
can be pressed again.
After exiting a guide with the keyboard, the focus stays in the message
input.
The chat panel fits short browser windows. In a window shorter than
the panel, the panel opened with its header, and the New chat and Close
buttons, off screen. It now fits inside the window, shrinking if it has
to, and gets its full size back in a taller window. The same goes after a
resize, after Reset Chat Position, and for a position saved on an earlier
visit.
Screen readers name the chat header’s buttons. New chat and Close, and
on the classic header Reset Chat Position and Change Language, now have
names.
Screen readers hear once that Moss is working. With the default
loader, a running guide was announced twice, and nothing was announced
while a request ran after a guide had finished. Each is now announced
once, and the default loader no longer re-announces as its text animates.
Coming back to a session too old to resume. The “Starting fresh” card
no longer has a working indicator behind it, and nothing can be sent to
the old session from behind the card.
One session per first open. Loading a page or opening the chat for the
first time starts at most one session. Before, it could start a second,
empty one. The app’s settings are also read once per page load, not twice.
Dashboard: long application names. The desktop sidebar keeps its
width, and at phone width the pages no longer scroll sideways.
openChat and toggleChat open the chat at the position you pass.
The position applies to that open only and isn’t saved. If the user moves
or resizes the chat during that open, their placement is kept.
Next stays available when a click step’s setup gives up. When a
step’s target couldn’t be found, or Next or Exit was pressed while it was
being set up, Next beside the input could stay hidden for the rest of the
guide.
Guides work on more pages whose forms have fields named after built-in
page properties or methods, such as submit, closest or matches.
A request the model provider’s safety filter blocks gets its own answer.
When a filter such as Model Armor or Gemini’s safety settings blocks a
request or its reply, Moss answers “A safety filter blocked this request, so
I can’t answer it. If it keeps happening on this page, please contact your
administrator.” It used to ask the user to rephrase. A blocked request counts
as blocked, not as an error, and the session shows a blocked step.
SDK rate limits: an unreachable limit store is logged as an error. With
SDK_RATE_LIMITS_ENABLED on, a run of skipped checks is logged as an error
whatever the cause. Before, only timeouts counted, so a store that refused
connections was logged as a warning only.
Each question reaches Moss once. With the conversation log that’s the
default since 0.16.1, every typed question went twice into the conversation
Moss reads. So Moss took a conversation’s first question for a later one and
didn’t work out the user’s goal for the first answer, and a very short
question searched the help articles with its words repeated. The first
answer stays as fast as before, and Moss now works out the goal alongside it.
Clicking a guide’s first step right after Moss offers it no longer ends
the guide with “I couldn’t recover this guide.”
Pressing Next while a click step is still setting up now moves the guide on.
Before, the press could be lost, and the guide bar kept showing “Working…”.
With closingChatEndsGuide on, closing the chat right after pressing Next or
sending a message no longer leaves the chat busy when it’s reopened.
Guide highlights no longer fail on pages whose forms have fields named after
built-in page properties.
Self-hosted: deleting a user’s data and missing buckets. A deletion is
no longer certified complete when the user’s files were stored in a bucket
that the dashboard backend can’t find. The certificate notes the missing
bucket, and the request can be retried once the bucket is configured.
Helm:global.storageBuckets.recordings and .screenshots now set the
bucket names for both backends. Rendering fails when the two backends name
different buckets, so helm template, install and upgrade stop with a
message that names the setting. Set each name to the bucket the install
already uses; nothing moves.
Upgrading with --reuse-values: add
--set global.storageBuckets.recordings=rrweb-recordings, or upgrade
without --reuse-values. An install that never changed these names and
upgrades without it needs no action.
Known limit: for an application that recorded sessions before 0.16.1
and has since set session recording to anything but on, recordings from
before 0.16.1 may not be checked.
Security
Python, CVE-2026-119170 (High): fixed. The backend and worker images
require the Python 3.14.10 build that fixes it.
soupsieve 4.0 in the backend and worker, which fixes CVE-2026-126190
and CVE-2026-126191 (High).
opentelemetry-api 1.45.2 in the backend and worker, which fixes
CVE-2026-126360 (Medium).
URL rules: page addresses are matched against URL rules with a length
limit and a time limit, so an unusual address can’t hold up the service.
Known issues
The 0.16.23 known issues still apply, except the one about a guide’s Exit
control and the note about a missing recordings or snapshots bucket, both
fixed above.
0.16.23 — 2026-11-13
Added
Closing the chat can end a running guide. With
closingChatEndsGuide: true in the SDK config, closing the chat while a
guide runs ends the guide, as its Exit control does. The highlight comes
off, and a page refresh brings nothing back. It applies to the close button,
a data-moss-trigger toggle, AssistantButton, closeChat() and
toggleChat(). A guide only offered, a guide already finished, a guide
running in another tab and Moss’s own closes are left alone. It is off by
default, and nothing changes until you turn it on.
New optional backend settings, all off or unchanged by default:
SDK_REQUIRE_ORIGIN: when on, SDK requests that carry no Origin or
Referer, and every request for an application with no allowed domains,
get 403 ORIGIN_REQUIRED. Leave it off unless every application has its
list filled in.
SDK_RATE_LIMITS_ENABLED: per-minute limits on SDK session starts,
queries, streams and recording uploads, kept in Redis. A slow or
unreachable Redis lets requests through. Current SDKs don’t wait out a
429, so a limited request fails its turn.
LLM_REQUEST_TIMEOUT_SECONDS (default 45): the first attempt’s timeout
for each model request in a chat turn.
Changed
Allowed domains are checked by exact host, on every SDK request. Check
each application’s list before you upgrade:
An entry matches only that exact host: example.com no longer matches
app.example.com. For subdomains, add a *. entry such as
*.example.com. A *. entry matches subdomains at any depth but not the
bare domain, so list both if Moss runs on both.
The check covers every SDK request from the page, not only the first
configuration load. A page the list doesn’t cover gets 403
DOMAIN_NOT_ALLOWED, and Moss doesn’t load there.
An entry with a port matches only that port. Browsers leave out the
default port, so an entry ending in :443 never matches an https page.
Origin: null, which browsers send from sandboxed iframes and local
files, is refused when the list isn’t empty.
An empty list is unchanged.
Screenshot uploads need the user’s token. SDK 0.16.23 sends it. Older
SDKs fall back to sending the screenshot inside the chat request, a few MB
each, so check that your ingress accepts bodies that size on
/api/v1/query until the SDK is upgraded. Upgrade the backend and
dashboard first, then the SDK.
Saving a guide from the SDK needs the authoring grant. Save as Guide in
debug mode and in Moss Studio now needs a token with authoring: true, and
saves only the token user’s own session. An ordinary end-user token gets
403, and the button says the user may not save guides. The dashboard’s own
save is unchanged.
A signed token with an empty subject is refused. A JWT whose sub is
empty, blank or not a string gets 401 INVALID_TOKEN, instead of running as
the user named in the request. Tokens with a real subject are unaffected.
A model request that hangs ends sooner. Each request a chat turn makes
has a timeout, then one retry with what is left of the turn’s 120 seconds.
A hung request now ends at about 118 seconds with “I’m sorry, that took too
long to answer. Please try again.” instead of the high-traffic message. A
slow but working request completes on its retry.
Deletion requests that fail are marked failed, with details, instead of
staying in progress, and can be retried.
No database migrations in this release, and the Helm chart’s values are
unchanged.
Fixed
A native modal dialog opened with showModal() no longer turns the page
grey under Moss when the page styles ::backdrop, and the chat no longer
inherits the dialog’s text layout, so its messages wrap.
A page whose form has a control named after a form property, such as
parentElement or id, no longer hangs the tab or breaks page capture.
Deleting a user’s data now completes when their chats have analytics
insights, evaluation scores, monitor flags, action logs, page snapshots or
guides. It also removes their model-call logs and proactive-guide events.
A rate-limited model request that the client gave up on is retried.
Security
Redaction. Redacted content no longer reaches Moss through a parent’s
text, accessible names and labels, interaction HTML, element fingerprints,
the validation summary or a clicked element’s text. This holds across open
shadow roots and same-origin frames. Redacted alerts and fields are listed
by tag only, so the summary still shows that they’re there.
glibc, CVE-2026-84243 (High): fixed. All four images ship glibc 2.44-r17,
which includes the 2.44-r16 fix.
Python, CVE-2026-119170 (High): not affected. It applies only when
OpenSSL runs in FIPS mode, and no image installs a FIPS provider. Scanners
may still report it.
Chrome for Testing 157.0.8103.78 in the worker, which fixes
CVE-2026-125350 (High) and the advisories published on 11 November.
Python dependency updates, and addresses containing a NUL character are
refused before any lookup.
The SDK package is published with an exact, integrity-checked npm.
Known issues
After a guide’s own Exit control, a click on the step’s target still sends
the step. Closing the chat with closingChatEndsGuide on doesn’t have this
gap.
Self-hosted: if RECORDINGS_BUCKET or DOM_SNAPSHOTS_BUCKET names a bucket
that doesn’t exist, the deletion certificate reports the erasure complete
without the request’s note about the missing bucket. Check that both name
your real buckets. A fix is planned for 0.16.24.
The 0.16.22 known issues still apply.
0.16.22 — 2026-11-10
Added
Returning after inactivity. Configure > Behavior > Session Behavior has
a new field, “When a user returns after inactivity”: “Ask to continue or
start new” (the default, as before) or “Start a new chat”. With “Start a new
chat”, a user who comes back to a session past its inactivity timeout (30
minutes by default) or its max age (2 hours by default) gets a new chat, with
no card and no rating. This applies when Moss loads into a timed-out session,
and when the user reopens the chat on a page left open, with the launcher,
openChat() or a data-moss-trigger element. The previous chat can’t be
reopened.
In the SDK, sessionConfig.onReturnAfterInactivity takes 'new_chat' or
'ask'. A value in your config wins. Left unset, the application’s
dashboard setting applies, delivered at session start by backend 0.16.22
and later; without one, 'ask'. For npm embeds, only this field comes
from the dashboard: the inactivity timeout, max age and showNotification
stay the ones in your config. A config built with convertBackendConfig()
takes all four from the dashboard.
Update the backend and dashboard before the SDK. An older backend drops
the setting on save without an error, and an older SDK ignores it. SDK
0.16.22 on an older backend asks, unless your config sets the field.
Moss’s own opens, such as askMoss() and proactive or onboarding flows,
don’t check. openChat() followed by sendMessage() sends the message in
the new chat once it connects. Moss holds one such message, and logs a
console warning when it can’t send it.
Guide steps taken with the chat closed, and activity on the same session
in another tab, count as activity. A guide idle past the timeout ends with
its session; if it ran in this tab, Moss Plan Finished reports it with
outcome: 'abandoned' under the old session’s sessionId.
Moving the chat window. The chat window also moves from the empty space
in the conversation and around the message box, not only from its header and
edges, so a window whose header is off screen can be dragged back. Messages,
links, buttons, cards, the guide bar and the scrollbar don’t drag, and a drag
selects no text. On touch, the conversation scrolls, and the window moves
from the header, the edges and the area around the message box.
Changed
The worker refuses private addresses on its own fetches. Image
downloads, sitemaps, discovery’s page sampling, and Document360 discovery and
scraping now reach public addresses only. Check these before you upgrade:
A forward proxy is no longer used for Document360, image and sitemap
fetches. These fetches connect directly and ignore HTTP_PROXY and
HTTPS_PROXY, and there is no setting yet to send them through a proxy.
If your worker’s egress requires one, contact us before upgrading. Firecrawl,
the LLM and embedding providers, Pinecone, storage uploads, Slack and the
browser’s page loads during discovery are unchanged.
Images and sitemaps on an intranet stop working until their host or range
is listed in the new worker setting WORKER_FETCH_ALLOWLIST
(comma-separated hosts and CIDRs, such as
wiki.corp.example.com,10.20.0.0/16). It is empty by default.
localhost needs its own entry. Cloud metadata addresses can never be
allowed. An invalid entry stops the worker at boot. Your object storage
(S3_ENDPOINT) needs no entry.
A refused image is recorded as failed and keeps its original address. A
discovery start URL on a refused host fails at once. A downloaded body that
isn’t an image is never stored.
Document360 API host. It must be a Document360 host
(*.document360.io or *.document360.com, such as apihub.document360.io).
Any other host is refused when it’s saved, and one saved earlier is refused
at sync, with a message to enter it again. A help center on its own domain
is fine, because that isn’t the API host.
Zendesk subdomain. It must be the account name only, such as acme, not
a full address. Upper case is accepted and stored in lower case.
CSV exports (conversations, traffic logs and the audit log). A cell that
starts with =, +, -, @, a tab or a carriage return gets a leading
apostrophe, so spreadsheets open it as text, never as a formula. That
includes negative numbers: -1 exports as '-1.
Slack alerts. Alert text is escaped and length-limited. Worker job
alerts carry the outcome, an error code and counts, but not the raw error
text; the details stay in the job’s record in Moss.
New optional setting: WORKER_FETCH_ALLOWLIST, on the worker. In the Helm
chart’s values.yaml, only commented examples for it are added.
Support tickets during a guide. While a ticket card is open, the guide
bar is hidden. Cancelling the card brings the guide back on the same step.
When the ticket is filed, or its outcome is unconfirmed, the guide ends and
stays ended: onEvent reports Moss Ticket Submitted, then
Moss Plan Finished with outcome: 'abandoned'. A ticket reported as failed
leaves the guide running. A guide started after the ticket shows its bar as
usual.
The ticket card opens on Moss’s reply. When Moss drafts a support ticket,
the chat opens on Moss’s message above the ticket form, not on the bottom of
the form.
Rating after a filed ticket. Once a support ticket is filed, “Was this
conversation helpful?” appears at once, under the ticket confirmation, so the
ticket number and its link stay in view. Answering it leaves the conversation
as it is, and New chat doesn’t ask again for that conversation. The next
message or guide step removes it. It doesn’t appear for a ticket that failed,
came back unconfirmed or was cancelled. A rating that can’t be sent brings
the buttons back.
A guide step after a long pause. When a user idles past the inactivity
timeout mid-guide, then clicks a step’s target that loads a new page, the new
page keeps the session and continues the guide, with no card to continue or
start new.
Saving session settings. A configuration save merges sessionConfig
with the stored settings: a save that sends only some session settings keeps
the others, and a setting sent as null is cleared. A save with
sessionConfig: null no longer clears them all.
Default loading-indicator selectors. With the loading-indicators
stability layer on and its default selectors, skeleton, spinner and
loader classes match in any case.
Every SDK change in this release works on any backend, except the dashboard
setting for returning after inactivity, which needs backend 0.16.22.
No database migrations in this release. The one new environment setting is
the worker’s optional WORKER_FETCH_ALLOWLIST, above.
Fixed
Moss no longer reads a page that is still drawing its loading placeholders.
Before it sends a turn’s page context, the SDK waits up to 4 seconds for
visible placeholders, such as skeletons, to clear, so answers describe the
loaded page instead of saying it is still loading. With none on screen there
is no wait. Placeholders that never clear cost one wait, and are then skipped
until they’re gone or the page’s address changes. The settings are under
stability.placeholderGuard (enabled, timeoutMs, excludeSelectors,
additionalSelectors and selectors). When you set
stability.loadingIndicators.selectors, the wait uses that list.
A turn that starts while an earlier one is still waiting for the page to
settle now waits too. It could read the page with no wait.
A guide step whose click opens a new tab, through a target=_blank link,
window.open() or a link that redirects, brings the chat up in the new tab
at the next step, and the step is sent once. A same-tab redirect, or a page
that rewrites its address as it loads, no longer stalls the guide. Switching
tabs right after a step’s click no longer ends the guide. This fixes the
0.16.21 known issue for a page whose address changes as it loads.
Security
Integration hosts for Document360 and Zendesk are now validated, and CSV
exports open safely in spreadsheets.
Alerts and audit records are hardened against untrusted input.
Worker fetches of private addresses (High). A crawled page could point
an image or sitemap link at an internal address, and the worker would fetch
it. The worker now refuses private, loopback, link-local and metadata
addresses on its own fetches, and stores only bodies that are images.
The images are rebuilt on current base-image packages, with no dependency
changes.
Known issues
Some valid images are refused and keep their original address: a UTF-16
SVG, an SVG that ends in a comment containing </svg>, an AVIF or HEIC whose
last box has size 0, and an SVG with a prefixed DOCTYPE name.
The 0.16.21 known issues for a guide whose starting answer is lost, in one
tab or with a second tab, still apply, as do the other two 0.16.20 known
issues for guides in more than one tab.
“Retry failed pages” counts and retries only pages that couldn’t be fetched.
To run pages that failed indexing again, refresh the source or edit the page.
With “Start a new chat”, a chat left open while the user is away keeps its
conversation: Moss checks only as it loads and as the chat opens. Calling
openChat() and then askMoss() in one handler, past the timeout, starts
one extra session that is never used.
If the page reloads mid-guide while a ticket card is open, the step’s
highlight comes back with the guide bar hidden, and a click on it completes
the step. When a ticket is filed in a tab that only shows the guide, the tab
running it reports Moss Plan Finished but keeps the guide bar until a later
answer clears it.
Placeholders inside shadow roots aren’t seen. A placeholder the page
re-creates on every render is waited on at each turn; exclude it with
stability.placeholderGuard.excludeSelectors.
The guide stays in the first tab when a step’s new tab can’t be tied to the
click: the tab opened in the background on a different address, the page
opened it only after the step was sent, a page-wide no-referrer policy or
window.open(url, '_blank', 'noreferrer') hid where it came from, or it was
reached through more than one intermediate page. A target=_blank link to a
page without Moss waits out the step’s window, 30 seconds by default, as
since 0.16.19.
Within 5 seconds of a step’s click, a tab the user opens by hand after a link
that sends no referrer, or another link the user opens from the same page,
can take the step.
0.16.21 — 2026-11-06
Changed
A source whose pages can’t be indexed ends in Error. It used to end
Ready with no content or with part of it. Each such page shows “Re-indexing
failed” in its page view. A refresh that fails this way keeps the current
version serving, with all of its content. The processing count on a source
advances while pages are indexed.
A Ready source that still has a page from an earlier run that can never be
indexed stays Ready. Until that page is refreshed or edited, each later
processing run records the error on it and sends a failed notification.
The failed notification (CHUNKING_FAILED) and the worker’s log say how
many pages failed, as N/M pages failed chunking (K indexed)., then give
the latest error as one of a fixed set of descriptions, never the raw
error text.
This also covers the 0.16.19 known issue on Vertex AI eu and us: a
source on gemini-embedding-001 now ends in Error instead of Ready with no
content.
Ingestion errors keep no raw error text. A page’s or a job’s error in the
ingestion API, and a source’s last error, are now a fixed description: an
error code, an HTTP status, an exception type or a provider name, such as
OpenAI. They no longer include an exception’s message or a provider’s
response. Errors stored before the upgrade are returned the same way. What
the dashboard shows is unchanged: it shows these errors in dev mode only. The
worker’s log keeps the full message.
Document360 API token on save. Spaces and line breaks at the ends of a
token are removed when it’s saved. A token with a line break, or another
character that isn’t printable ASCII, inside it is refused, with a message
to paste it again. A token saved earlier with a trailing line break is now
sent without it.
No database migrations or new settings in this release.
Fixed
Direct Zendesk filing sends nested branch fields. Fields that a
conditional field opens at any depth, such as a recording type under a
product area, are now sent. Tickets on those branches used to be held back
as missing a required field.
Host-brokered ticket card. When a branch of the ticket form requires a
text field that Moss fills with the user’s role, such as “Your Role”, the
card now shows the role the user gave. It used to show an empty row.
Plan events with Moss open in more than one tab (SDK only).
A guide step the user completes with a click, in a tab that was only
showing the guide, now reports Moss Plan Step Completed, and
Moss Plan Finished when it was the last step. The click takes the guide
over in that tab, as in 0.16.20. In 0.16.20 the tab could report neither
event for a step that doesn’t open another page, which covers most
“Click …” steps.
Pressing Start Guide on an offer after another tab has already started
that guide no longer reports Moss Plan Started, or the other tab’s
completed steps, a second time. The tab only shows the guide, and takes it
over when the user continues it there, with Next or a step.
Security
Browser in moss-worker. Chrome for Testing moves from 156.0.8078.80 to
157.0.8103.38, which fixes 26 Critical and 54 High advisories in 156. The
other three images don’t include the browser.
glibc, CVE-2026-84243 (High): no fix yet, assessed. Your scanner may
report it in glibc 2.44 in all four images, and no fixed glibc is published
yet. Exploiting it needs an attacker-controlled LANGUAGE, an active
message locale other than C or POSIX, and a crafted message catalog the
process can read. The 0.16.21 images run with the C locale, set no locale
variable and install no other locale definition. The fixed glibc ships in
the first release after one is published. If your deployment sets LANG,
LANGUAGE, LC_ALL, LC_MESSAGES or LOCPATH, or mounts locale files,
contact us and we’ll reassess.
sqlite-libs, CVE-2026-119586 (High): not affected. The advisory is in the
SQLite command-line shell’s .recover command. No image includes the
sqlite CLI, and the library in the backend and worker images has no
recover functions. Your scanner may still report it, with no fixed version.
Error text in the ingestion API. Through 0.16.20, the ingestion API
returned a page’s or a job’s stored error text to any member of the source’s
organization. In rare cases that text repeated a credential: a Document360
token saved with a line break in it, or a token in a source’s URL. 0.16.21
stores no such text, and returns only the fixed description for errors
stored before the upgrade. If a Document360 token was saved with a line
break, rotate it.
Backend dependency security update (idna), to its first patched version,
3.15, for a Medium advisory.
The images are rebuilt on current base-image packages. The moss-backend
and moss-worker builds also place a copy of each installed Python
package’s own SBOM where scanners look, so image scans see those packages’
components. Nothing changes at run time.
Known issues
This replaces the first 0.16.20 known issue. If the backend starts a guide
but the answer doesn’t reach the tab, that tab only shows the guide. This
happens when the answer to a typed yes is lost, or when the SDK’s automatic
retry of a 503 answers instead of the first attempt. The tab doesn’t
continue the guide after a reload until the user continues it there, with
Next or a step. It never reports that guide’s Moss Plan Started, even
then: Next or a step there reports only Moss Plan Step Completed. When the
answer to Start Guide is lost to a network or server error, pressing Start
Guide again runs the guide in that tab and reports Moss Plan Started once.
If a tab’s Start Guide gets no answer because of a network or server error,
and another tab starts the same guide before this tab’s next answer, both
tabs report Moss Plan Started. After a guide overview, the same applies to
any guide another tab starts before the user presses Start Guide again.
The other two 0.16.20 known issues for guides in more than one tab still
apply.
A guide step into a page that redirects or changes its address as it loads,
such as a changed query value, may not bring up the chat in the new tab; the
guide then carries on in the first tab after 30 seconds. In the same tab,
the chat comes back but the guide can stall. Fixed in 0.16.22.
“Retry failed pages” counts and retries only pages that couldn’t be fetched.
To run pages that failed indexing again, refresh the source or edit the page.
0.16.20 — 2026-11-04
Added
Pinecone private endpoint (AWS PrivateLink). With
PINECONE_USE_PRIVATE_ENDPOINT=true (off by default), sdk-backend,
dashboard-backend and the worker still look the index up on
api.pinecone.io, then send all data-plane traffic (search, fetch, upsert
and delete) to the index’s private host,
<index>.svc.private.<...>.pinecone.io, which Moss reads from the index
description; there is no host to configure. api.pinecone.io must stay
reachable from all three workloads.
There is no fallback to the public host. If the index’s Pinecone project
has no private endpoint, Moss doesn’t connect to the index: chats answer
without the application’s knowledge base, deleting a source fails, and
chunking jobs fail before they touch a source’s pages or vectors. Each
logs an error that names the index and the setting.
Set it on all three workloads, with the upper-case name and the same
value. true, t, yes, y, on and 1 turn it on, in any case;
false, f, no, n, off and 0 leave it off. Any other value,
including an empty one or one with surrounding spaces or quotes, stops the
backends from starting and fails every chunking job.
Each process logs Pinecone data-plane host: private (or public) the
first time it opens the index. The line shows the host Moss picked, not
that it is reachable.
Before turning on Pinecone’s private-endpoint-only restriction for the
project, check that Pinecone answers through the private host, since a
wrong DNS record or security group still logs private. On sdk-backend,
one chat turn that uses the knowledge base logs the private line, then
Pinecone multi-namespace search completed with results=N/M and N above
0, and no search failed. On the worker, one knowledge-source refresh logs
the private line and the source ends Ready with more than 0 chunks. On
dashboard-backend, which may not log the line for a while, confirm the
variable is set on its deployment. With the restriction on, Pinecone
rejects data-plane requests that don’t come through the endpoint, so a
workload still on the public host loses retrieval or indexing.
The setting was tested against a mocked Pinecone API, not a live
PrivateLink endpoint, so the check above is the test on your install.
Changed
New optional setting: PINECONE_USE_PRIVATE_ENDPOINT. In the Helm chart’s
values.yaml, only commented examples for it are added, on sdk-backend,
dashboard-backend and the worker; the chart README documents it. With the
setting off, Moss sends the same Pinecone requests to the same hosts as
0.16.19.
No database migrations in this release.
Fixed
With Moss open in more than one tab, a guide runs only in the tab where the
user started it. Another tab can show it, and takes it over only when the
user continues it there. Plan events (Moss Plan Started,
Moss Plan Step Completed, Moss Plan Finished) come only from the tab the
guide runs in, so each guide counts once; in 0.16.19 a second tab could
report them again. A guide exited from another tab is reported as
Moss Plan Finished with outcome: 'abandoned' by the tab that ran it. The
fix needs both the 0.16.20 backend and SDK 0.16.20.
Security
Backend dependency security updates (h2, hpack, langgraph,
langgraph-sdk, soupsieve) and worker dependency security updates
(multidict, soupsieve), each to its first patched version, for Medium
advisories.
The moss-dashboard and moss-dashboard-oidc builds install one exact,
hash-checked pnpm, 10.34.7, instead of a floating pnpm at build time.
There is no other Dockerfile change. The images are rebuilt on current
base-image packages.
Known issues
If the answer that starts a guide doesn’t reach the tab, for example after
a retried 503, that tab only shows the guide. It reports no
Moss Plan Started, and doesn’t continue the guide after a reload until the
user continues it there, with Next or a step.
When another tab takes a guide over, with Next or a step there, the original
tab still reports Moss Plan Step Completed for the other tab’s steps if its
user asks something later. A New chat in the original tab still ends the
guide on the device and reports it finished there.
If the tab running a guide is mid page load when a tab that only shows the
guide exits it, no tab reports that Moss Plan Finished.
0.16.19 — 2026-11-03
Added
SDK analytics events. Pass onEvent in the provider config to forward
Moss usage to your analytics, for example
onEvent: (e) => window.analytics?.track(e.name, e.properties). Each event
is { name, properties }, named in Segment’s “Object Action” form. Twelve
events cover the chat, questions and answers, errors, guided plans, feedback
and support tickets. MOSS_EVENT_NAMES lists them, and the SDK README
documents each event’s properties. Moss Question Asked carries
source: 'user' | 'host', where 'host' marks a question sent with
askMoss(), counted once as its request leaves. Question text is left out
unless you set eventQueryText to 'include' or a function. A handler that
throws is logged and ignored, and leaving onEvent unset changes nothing.
Starting Moss on demand. For hosts that mount Moss only when the user
asks for it, shouldStartMoss() from @viamoss/moss-sdk/start (no React)
tells the page, as it loads, whether to mount Moss. It returns true when the
chat was open in this tab before the page changed, while a guide is running
in this tab, while an askMoss() question waits in this tab, or when a guide
step the user took is waiting to continue on this page (30 seconds by
default). Mount Moss when it returns true, and don’t open or toggle the chat
yourself. It needs stability.afterReload.enabled: true; if you set
stability.afterReload.pendingTTL, pass the same value. It only reads
browser storage and never throws.
Opening Moss with a question.askMoss(question), also exported from
@viamoss/moss-sdk/start, hands a question from your own assistant or help
widget to Moss: Moss starts a new chat, opens it and sends the question as
the user’s first message. It returns { accepted: true, id, queued } or
{ accepted: false, reason: 'empty' | 'unavailable' }, and never throws.
With queued: true, mount Moss without opening the chat within 30 seconds
(ttlMs changes that). Call it in the same window and on the same origin as
Moss, and open the chat with openChat(), not a toggle or a
[data-moss-trigger] click: a toggle while a question waits closes the chat
and drops the question. A chat or guide in progress ends as New chat ends it.
Vertex AI eu and us multi-regions. With GOOGLE_AUTH_MODE=vertex
and GOOGLE_CLOUD_LOCATION=eu, chat, gemini-embedding-2 embeddings and
image annotation all go to aiplatform.eu.rep.googleapis.com; us works the
same way on aiplatform.us.rep.googleapis.com. Set the location on both
backends and the worker, and allow egress to that host from all three.
Vertex on global or a single region sends the same requests to the same
hosts as before.
OIDC session renewal. With OIDC_REFRESH_TOKENS=true (off by default) on
the moss-dashboard-oidc container, the dashboard renews the user’s ID token
with a refresh token, so sessions outlast the IdP’s ID-token lifetime (60
minutes on Okta). Allow the Refresh Token grant for the Moss application in
the IdP first and, for an Okta custom authorization server, offline_access
in its access policy. Without the access-policy change, every sign-in fails
once the setting is on.
security.txt. The backend serves an RFC 9116 file at
/.well-known/security.txt, without sign-in and in every service mode, and
/security.txt redirects there. The contact defaults to
mailto:security@viamoss.ai; set SECURITY_TXT_CONTACT to a mailto: or
https: URI to list your own.
Changed
Image annotator default model. With ANNOTATOR_LLM_MODEL unset, the
worker uses gemini-3.8-flash at low thinking, replacing gemini-2.5-flash,
which Google retired on 2026-10-20. An explicit gemini-3.8-flash also moves
to low thinking, with a 4,096-token output limit. Other models are
unchanged.
OIDC sign-in. Users in neither OIDC_ADMIN_GROUPS nor
OIDC_MEMBER_GROUPS see an Access Denied page at sign-in. If the
dashboard-serving backend’s OIDC_AUDIENCE lacks the OIDC client ID, users
return to sign-in after each sign-in; add the client ID. Users signed in
before the upgrade sign in once more.
Dashboard toasts appear at the bottom right, in both dashboard images. They
move up when they would cover the Copilot or Playground message box, or the
Save and Discard bar on Suggested Content.
In the SDK, each tab keeps its own chat and guide. A tab opened with
window.open() starts with the chat closed and no guide, and a guide
continues after a reload only in the tab it runs in. When a guide step opens
a new tab, the chat opens there if it was open in the first tab.
New optional settings: OIDC_REFRESH_TOKENS on the dashboard and
SECURITY_TXT_CONTACT on the backend. GOOGLE_CLOUD_LOCATION also accepts
eu and us. In the Helm chart’s values.yaml, only the commented
ANNOTATOR_LLM_MODEL example changes.
No database migrations in this release.
Fixed
OIDC dashboard sessions no longer outlive their ID token. Before, about an
hour after sign-in on Okta, every API call failed with 401 while the
dashboard still showed the user as signed in. Now the next page load goes to
sign-in (“Your session has expired”) and then back to the same page; with an
active IdP session, usually without asking for credentials.
The dashboard’s retry after a 401 asks for a fresh token, and a sign-in the
IdP refuses says so on the sign-in page.
LLM_THINKING=minimal on gemini-3.8-flash is sent as low. Every chat
request with it failed with a 400 before.
In the SDK, a chat start that fails after New chat has replaced it no longer
leaves the new chat’s message box disabled with no Retry.
Security
API action identity. Configured API actions take the user’s company and
user ID from the signed SDK token, never from the conversation. The company
comes from company_id (or companyId) in the JWT metadata claim.
Company-type fields (company_id, tenant_id, organization_id, org_id
and their X- header forms) are filled by the server, and an action with one
is refused when the token carries no company. user_id is filled with the
signed-in user, and a call that names another user is refused. Applications
without API actions see no change.
Role-limited procedures. A procedure with allowed_roles runs only for
users whose token signs one of those roles in metadata.role. Until the host
signs role, such a procedure is hidden from every user. A malformed
allowed_roles value admits nobody.
A missing or blank APP_ENV now means production. Workers that don’t set it
report production in telemetry, so dashboards that filter on local may
shift.
The images are rebuilt on current base-image packages, with no dependency
changes.
Known issues
With Moss open in two tabs during one guide, the tab that isn’t running the
guide also emits Moss Plan Started, Moss Plan Step Completed and
Moss Plan Finished for it, so those can be counted twice. With one tab the
counts are right. Fixed in 0.16.20.
gemini-embedding-001 isn’t supported on eu or us: ingestion with it
fails, and chats answer without the application’s knowledge base. An
application’s embedding model can’t be changed, so moving to
gemini-embedding-2 means a new application whose sources are ingested
again.
The chart’s chat default, gemini-3-flash-preview, is served on global
only. On eu or us, set LLM_MODEL_NAME on both backends to a model
Google serves there, such as gemini-3.8-flash.
Analytics chat, the daily insight sweep, monitor scoring, procedure
authoring, self-healing and session evaluations call the Gemini Developer
API with LLM_API_KEY, whatever GOOGLE_AUTH_MODE says. On eu or us,
leave LLM_API_KEY unset on both backends so these calls fail instead of
leaving the region, and set INSIGHT_SWEEP_ENABLED=false on the dashboard
backend.
Okta has been reported to leave the groups claim out of refreshed ID tokens.
The dashboard then doesn’t use them, and sessions still end every hour. Try
OIDC_REFRESH_TOKENS on a staging install first.
0.16.18 — 2026-11-03
Security
Backend and worker image security update: libexpat 2.10.0
(CVE-2026-113351, CVE-2026-115506), replacing the patched library shipped in
0.16.16. The worker keeps refusing sitemaps that declare a DTD.
The Guidance Flows empty state now says only that there are no flows.
No database migrations in this release.
0.16.17 — 2026-11-02
Changed
Build fix only. The images run the same software as 0.16.16, and
deployments already on 0.16.16 don’t need to upgrade.
No database migrations in this release.
0.16.16 — 2026-11-02
Changed
Support tickets: the card comes first. With host-brokered filing, once a
ticket is called for, Moss shows the editable ticket card as soon as it has a
subject and a description. It no longer writes the ticket out in chat, asks
for a confirmation there, or asks for an email address or other contact
details. Nothing is filed until the user submits the card, and Moss says a
ticket was filed only once the filing is confirmed. Remove procedure text
that asks for a confirmation in chat.
Ticket fields are pre-filled only from what the user said, in both
filing modes, and values for anything outside the ticket’s fields are
dropped. The user can still change every field the card shows. The impact
level follows the user’s own words in the subject, the description and their
messages, so the request type no longer raises it. Critical is pre-filled
when the user reports an outage, or says work has stopped or everyone is
affected. Without such a signal, a host-brokered card leaves the impact empty
and a direct ticket defaults to Medium.
The Filing switch is the single on/off for tickets. Off, in the Filing
row of Configure > Integrations > Zendesk, applies in every procedure, in the
default reply, to a ticket request under way and at Submit, and direct
connections no longer dry-run. Procedures also offer no tickets while a
connection is Paused or otherwise can’t file. Only an Admin can see or change
the switch.
Before upgrading, decide each Zendesk connection’s Filing setting. A
connection that shows Off while its procedures still offer tickets stops
offering them at the upgrade. Switch host-brokered connections to Live only
after the upgrade, because on earlier releases Live also turns on a
default-reply ticket offer that asks for the user’s email address. To keep
the default reply from offering tickets, set
procedures.default_reply_policy to false in the application’s
configuration; this also drops its suggestion to contact support. Where a
direct connection’s Zendesk form requires the requester’s role, pin a value
for that field on the Ticket intake page, or have the ticket procedures ask
for the role.
SDK 0.16.16 types the outcome’s ticketId as string | number and sends it
as text.
LLM_CLIENT_TYPE no longer accepts baseten, and the provider-failover
settings LLM_AUTOROUTER_ENABLED and LLM_FALLBACK_PROVIDERS are ignored.
The backend uses the one provider that LLM_CLIENT_TYPE names.
Traffic-log audit events from Bearer sign-ins record auth_methodjwt
instead of clerk_jwt. Older events keep clerk_jwt, so update any SIEM
filter on the value.
The worker refuses sitemaps that declare a DTD.
Upgrading from 0.16.7 also brings in 0.16.8 through 0.16.15, none of which
has a database migration or a Helm values change.
No database migrations in this release. The Helm chart’s values.yaml
changes only in a comment.
Fixed
A repeated Submit of the same card before your backend’s answer is recorded,
for example after a lost response, is accepted and handed to your backend
under the same handoffId. Deduplicating on handoffId gives the user one
ticket. A repeat with changed values is still refused.
Your backend can return ticketId as a number or as text, and a
whole-number errorCode or errorDetail is kept as text. These were refused
before, and the outcome went unrecorded.
The dashboard’s Broker contract page describes what your backend receives: a
timeout, a callback that throws or an answer without a boolean ok leaves
the outcome unknown, not failed; custom-field values are strings; and the
ticket body is the description followed by the last 12 chat messages, each
cut at 400 characters.
Security
Admin-only access. These need an Admin: changing, testing or importing
an integration’s configuration, including Zendesk and custom API
connections and actions, which Members can still read; the traffic logs,
which now also work with OIDC sign-in; accepting AI-instruction proposals;
and reading deletion requests. Members see Accept disabled on instruction
proposals and Save disabled on Suggested Content. A Member refused on the
audit log or the traffic logs is recorded as an auth.denied audit event.
Integration credentials are kept out of application reads, the SDK
session response, logs and audit events, and the session response carries
only the settings the SDK uses. Audit lists and exports mask credential
fields in earlier events as [REDACTED]. An Admin API client that sends back
a configuration it read keeps the stored credentials, unless a block’s
address, such as the Zendesk subdomain, changed.
Image security updates:
Brotli (CVE-2026-111497), all four images. No path lets untrusted input
reach the decoder.
Chrome for Testing 156.0.8078.80, worker. Affected in principle, since the
worker browser loads the help sites you configure; fixed by the update.
PostgreSQL client libpq-18 in place of libpq-16, backend and worker. Not
affected.
Expat, patched library (CVE-2026-113351), backend and worker. Refusing
sitemaps that declare a DTD mitigates CVE-2026-115506, since the worker
never parses a DTD.
Python 3.14.10 (CVE-2026-115557), backend and worker. The image build
refuses an older Python.
CA certificates (CVE-2026-111943), backend and worker, with the distrusted
emSign roots removed from the system and Python stores.
pyasn1 0.6.5, Pillow 13 and certifi 2026.10.23, backend and worker.
Next.js 15.5.28 (GHSA-2464-fhr4-w9xw, GHSA-p3m5-59mp-jv5r) and Node.js 24
(CVE-2026-105482, CVE-2026-106069), dashboards.
Playwright 1.63.0, worker.
An unused LLM client library, which carried its own OpenSSL, is removed
from the backend.
Known issues
Outage detection depends on wording: some outage reports aren’t read as
Critical, and some other reports are. The user can change the impact on the
card wherever the ticket intake shows it (by default, under Review details).
With Filing Off, a card drafted before the switch shows “Couldn’t submit
right now. Nothing was sent — please try again.” at Submit; switching back to
Live lets it through. The procedure Playground and Copilot’s simulations
ignore the switch.
0.16.15 — 2026-10-19
Fixed
Required fields that a conditional branch of the Zendesk form opens, but
that no intake role maps, appear on the ticket card as empty required rows,
so the user can fill them and a validation error points at the row. Fields
the Ticket intake page fills another way (a pinned value, the assistant, or
your backend) keep their handling. A stored intake picks these fields up at
its next form sync.
Security
Worker browser update to Chrome for Testing 155.0.8059.84.
Backend and worker dependency security updates: psycopg 3.3.6 and
psycopg2-binary 2.9.13, which bundle OpenSSL 3.5.8, and cryptography
50.0.2, which bundles OpenSSL 4.0.3.
Changed
No database migrations in this release.
0.16.14 — 2026-10-15
Security
Base image security refresh for all four images: OpenSSL 4.0.3
(CVE-2026-54873, CVE-2026-72897, CVE-2026-84782, CVE-2026-84784) and zlib
(CVE-2026-85091).
Changed
No database migrations in this release.
0.16.13 — 2026-10-15
Fixed
Changing a dropdown on the ticket card refreshes the fields its value
requires, nested conditional fields included, so the fields a branch opens
appear on the card. Values from branches that are no longer selected are
dropped at submit.
When validation rejects a field, the card marks that field’s row with the
reason and opens it, instead of showing only a generic note.
Changed
The refresh after a dropdown change, the per-field reasons and opening
rejected rows need SDK 0.16.13. Older SDKs keep working: nested fields are
offered when the draft already carries their parent values, and a rejected
row is marked “This value wasn’t accepted.”
No database migrations in this release.
0.16.12 — 2026-10-15
Fixed
Refreshing or reprocessing a page that now produces fewer chunks no longer
leaves its old trailing chunks in knowledge search. The worker’s cleanup
before re-chunking failed against Pinecone’s preview fetch API, logged
Batch pinecone cleanup failed, falling back per-page, and deleted nothing.
First ingests and full source refreshes were unaffected apart from the
warning. After upgrading, refresh an affected page, or run a full source
refresh, to remove its stale chunks.
Changed
No database migrations in this release.
0.16.11 — 2026-10-14
Security
Worker browser update to Chrome for Testing 155.0.8059.39.
First complete on-prem image set since 0.16.7. It carries the 0.16.8 and
0.16.9 fixes.
No database migrations in this release.
0.16.9 — 2026-10-13
The worker image for 0.16.9 was not published because it was held by the
vulnerability gate. On-prem deployments should use 0.16.10 or later, which
carries every 0.16.9 fix.
The images for 0.16.8 were not published because they were held by the
vulnerability gate. On-prem deployments should use 0.16.10 or later, which
carries every 0.16.8 fix.
Fixed
Knowledge search returns documents again. Pinecone’s preview search API
began rejecting a reserved field that Moss requested, so every search
returned no documents and the assistant answered without the knowledge base.
Changed
No database migrations in this release.
0.16.7 — 2026-09-17
Added
Multi-architecture on-prem images. Every on-prem image tag
(moss-backend, moss-worker, moss-dashboard, moss-dashboard-oidc)
resolves to an OCI image index with linux/amd64 and linux/arm64 images.
Cosign signatures and CycloneDX SBOM attestations cover the index digest and
each architecture digest. Mirror the full index together with its signature
and attestation tags; docker pull and docker push flatten it to one
architecture.
Changed
Each image tag resolves to an index digest instead of a single-image digest.
Verification by tag is unaffected. Deployments that pin a digest re-pin
once, to the index digest or to the architecture digest they want.
The SDK package loads in CommonJS projects: main and the require
condition point at a CommonJS build with its own type declarations.
getAppearance and the appearance preset objects are no longer declared by
the SDK; select a preset with the appearance config option.
SDK tokens whose metadata claim is present but not an object are rejected
with 401 INVALID_TOKEN. A non-empty list, string or number caused a server
error before, and an empty one ([], "", 0, false) was accepted.
The worker drops unused dependencies, nltk among them.
Base image refresh.
No database migrations in this release.
Fixed
FloatingActionBar, fetchAppConfig, convertBackendConfig,
mergeAppearance, MOSS_TRIGGER_ATTR and installModalDialogEscape can be
imported from the SDK package. Its type declarations listed them, but the
bundle did not carry them.
Application export and import. Admins can export a versioned bundle
from Configure > General and import one from the application list through
an Import dialog. The bundle covers the authored application alongside its
configuration: procedures, API connections and actions, integration
connections, monitors, intent tags, and the self-healing schedule.
Credentials are never included and are re-entered on the target.
Integration connections in direct-filing mode are reported for completion
rather than created. Import runs in one transaction, and the dry-run report
lists what would be created, remapped identifiers, every value written
differently from the bundle, and a re-entry checklist. The dashboard export
produces the full bundle by default, and the configuration-only bundle
remains available. Guidance flows are not part of the bundle. The endpoints
are GET /api/v1/applications/{id}/export and
POST /api/v1/applications/import?dry_run=true.
Dashboard-managed appearance controls (first pass). A new theme slice
and a footer background tint can be edited from the dashboard. The SDK
applies dashboard-saved values over the host prop per leaf, so precedence
is preset, then host prop, then dashboard value. Hosts must upgrade the SDK
to 0.16.6 to see dashboard theme values.
The SDK chat window can now be dragged from the full header and from the
window edges.
Dashboard toasts have a dismiss button, and error toasts stay until
dismissed.
Changed
Clearing the last leaf of a configuration slice now removes the slice
instead of storing an empty object.
The SDK package no longer ships sourcemaps in the tarball and now carries a
public README and package metadata.
Upgrade order for split deployments: backend, then dashboard, then SDK.
The application prune script now covers every application-owned table,
removes stored DOM snapshot objects, resolves tables through the configured
database schema, and refuses to run when it detects cross-application
references or cannot count a table.
No database migrations in this release.
Known issues
For a stored footer that contains only links, the public configuration
endpoint reports enabled: false.
Importing into an organization whose install already holds an application
with the same name is refused. Application names are currently unique per
install.
0.16.5 — 2026-09-02
Security
Worker dependency security update (nltk).
Changed
First complete on-prem image set that carries the 0.16.4 fixes. On-prem
deployments that skipped 0.16.4 should upgrade directly to 0.16.5.
For split deployments, upgrade the backend before the dashboard.
0.16.4 — 2026-09-02
The worker image for 0.16.4 was not published because it was held by the
vulnerability gate. On-prem deployments should use 0.16.5, which carries
every 0.16.4 fix.
Fixed
The dashboard pages for Procedures, Custom API Actions, Integrations,
Monitors, and Proposals now work on deployments that sign in with OIDC.
Per-prompt zero-state icons configured in the dashboard now render in the
SDK exactly as configured, and turning them on takes a single save.
The public SDK configuration endpoint now tolerates unknown zero-state keys
instead of failing.
Changed
Base image refresh.
0.16.3 — 2026-08-27
Fixed
SDK tokens that carry an audience (aud) claim are no longer rejected when
the deployment does not require one.
Reasoning levels that the configured model does not support are now
coerced to the nearest supported level instead of failing the request.
Saving the dashboard Appearance or Security form no longer overwrites SDK
appearance presets, and each form saves only its own fields.
0.16.2 — 2026-08-23
Security
Base image security refresh. This is the first published on-prem image set
of the 0.16 line.
0.16.1 — 2026-08-23
The images for 0.16.1 were not published because they were held by the
vulnerability gate. On-prem deployments should use 0.16.2 or later, which
carries every 0.16.1 fix.
Fixed
The public SDK configuration endpoint is now served in every backend
service mode, so split deployments that expose only the SDK backend can
bootstrap the SDK.
The public key field on the dashboard Security page no longer overflows
its container.
Security
Dashboard dependency security update (nanoid).
0.16.0 — 2026-08-17
Added
Support Ticket Handoff — the assistant can collect a support request,
show the user a review card, and hand the confirmed ticket to your
application to file through your own backend. See
Support Ticket Handoff. Ticket filing is
offered only on applications where it is configured and only to sessions
whose host registered the onSupportTicket callback.
Session detail — the dashboard session page groups the transcript more
clearly and closes several display gaps.
Fixed
Multiline input (Shift+Enter) now also works in the compact guide bubble.
Dashboard deep links that cross organizations now recover to the
application’s owning organization instead of failing.
0.15.4 — 2026-08-10
Security
Dependency security updates.
0.15.3 — 2026-08-10
Added
Knowledge base progress — documentation sources show a segmented
progress bar with separate scrape and process phases.
Fixed
Continuing a guide no longer records a duplicate user turn in the session
transcript.
On-prem OIDC sign-in hardening, including support for multiple accepted
audiences.
0.15.0–0.15.2 — 2026-08-06
Added
Session transcripts redesigned — the dashboard renders sessions as a
chat stream with paired stimulus/response cards, user role labels, and date
dividers.
Fixed
Soft line breaks in assistant responses now render correctly in chat,
streaming, and guide instructions.
0.14.0 — 2026-08-06
Added
Multiline chat input — Enter sends, Shift+Enter adds a line.
Assistant responses in dashboard session transcripts render as markdown.
Citations from Document360 sources now link to the public portal URL.
0.13.0 — 2026-08-05
Changed
The SDK version now tracks the Moss platform version.
Session resume card redesigned: centered rating prompt and a compact
choice between continuing and starting a new session.
Fixed
Prevented stale responses from appearing after starting a new chat.
Prevented resuming onto a stale pending interaction.
{"docsConfig":{"theme":"mint","$schema":"https://mintlify.com/docs.json","name":"Moss Documentation","colors":{"primary":"#000000","light":"#333333","dark":"#000000"},"logo":{"light":"https://mintcdn.com/moss-d7c5ed60/S5aXHXmoaZpUr-nV/logo/light.svg?fit=max\u0026auto=format\u0026n=S5aXHXmoaZpUr-nV\u0026q=85\u0026s=fec775d374812338dc1ed50c0fa278ca","dark":"https://mintcdn.com/moss-d7c5ed60/S5aXHXmoaZpUr-nV/logo/dark.svg?fit=max\u0026auto=format\u0026n=S5aXHXmoaZpUr-nV\u0026q=85\u0026s=6afe327af21c007efa5e76a21e500df1"},"favicon":"https://mintcdn.com/moss-d7c5ed60/bStaGBmKk1RIZaQA/favicon.svg?fit=max\u0026auto=format\u0026n=bStaGBmKk1RIZaQA\u0026q=85\u0026s=895a6357c555f668928a87c7c0f9416b","navbar":{"links":[]},"footer":{"socials":{}},"styling":{"latex":false},"navigation":{"languages":[{"language":"en","href":"en"},{"language":"ko","href":"ko"}]}},"deployment":{"deploymentMetadataValue":{"subdomain":"moss-d7c5ed60","hasAudioNarration":false,"actualSubdomain":"moss-d7c5ed60","customDomains":["docs.viamoss.ai"],"gitSource":{"type":"github","owner":"viamoss","repo":"docs","deployBranch":"main","contentDirectory":"","isPrivate":false,"mountPath":"","label":""},"entitlements":{},"buildId":"6afd3c55e69f8818411bb530","clientVersion":"0.0.4177","searchFilterCounts":[{"language":"en","tag":"SDK","count":9},{"language":"ko","tag":"SDK","count":9},{"language":"en","tag":"Security","count":5},{"language":"ko","tag":"보안","count":5},{"language":"en","tag":"Configuration","count":4},{"language":"ko","tag":"설정","count":4},{"language":"en","tag":"API Reference","count":3},{"language":"ko","tag":"API Reference","count":3},{"language":"en","tag":"Resources","count":2},{"language":"en","tag":"Getting Started","count":2},{"language":"ko","tag":"리소스","count":2},{"language":"ko","tag":"시작하기","count":2},{"language":"en","tag":"Dashboard","count":1},{"language":"en","tag":"Guides","count":1},{"language":"ko","tag":"대시보드","count":1},{"language":"ko","tag":"가이드","count":1}]},"assistantConfig":{"enableAskAiButton":false,"enableStarterQuestions":false,"enableAskAiSearchBar":true},"basePath":"","hasChatPermissions":false,"hasWebMcpPermissions":false,"toggles":[{"name":"kill-isr","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"custom-rbac-roles","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"agent-mintlify-slack","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"agent-integrations-settings","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"rbac-expansion","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automations-pr-grouping","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"custom-prefix","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"analytics-v7","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"user-flows-analytics","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"no-publish-flow","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-onboarding","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"snapshot-serving-live","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"stripTemperatureMiddleware","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"support-platform-pylon-zendesk","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"snapshot-serving","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"instant-rollback","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"granular-notifications-server","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"granular-notifications","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automations-fable","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"fixed-ai-action-pricing","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automation-resolve-merge-conflict","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"scoped-publishing","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"mintql","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"page-level-analytics","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"editor-version-history-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"billing-page-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"full-page-search","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workspace-projects","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"assistant-v5","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"fork-pr-previews","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"revalidation-jwt","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-sso-scim","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"hobby-abuse-scan","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"dashboard-inbox","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-signup","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"turbopuffer-dual-write","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-enabled","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"approve-review-flow","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"editor-metadata","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"sso-setup-deadline-banner","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"turbopuffer-serve","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"live-agents","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"starter-pricing","enabled":true,"variant":{"name":"treatment","enabled":true,"payload":{"type":"string","value":"treatment"},"feature_enabled":true},"impressionData":false},{"name":"llms-txt-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"wildcard-email-auth","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false}],"googleFontsInlined":false},"customCss":[],"page":{"pagePath":"en/changelog","slug":"/en/changelog","pageMetadata":{"title":"Changelog","description":"Notable changes to the Moss SDK and dashboard","icon":"clock-rotate-left","href":"/en/changelog"},"description":{"compiledSource":"\"use strict\";\nconst {jsx: _jsx} = arguments[0];\nconst {useMDXComponents: _provideComponents} = arguments[0];\nfunction _createMdxContent(props) {\n const _components = {\n p: \"p\",\n ..._provideComponents(),\n ...props.components\n };\n return _jsx(_components.p, {\n children: \"Notable changes to the Moss SDK and dashboard\"\n });\n}\nfunction MDXContent(props = {}) {\n const {wrapper: MDXLayout} = {\n ..._provideComponents(),\n ...props.components\n };\n return MDXLayout ? _jsx(MDXLayout, {\n ...props,\n children: _jsx(_createMdxContent, {\n ...props\n })\n }) : _createMdxContent(props);\n}\nreturn {\n default: MDXContent\n};\n","frontmatter":{},"scope":{}},"pageType":"default","mdx":{"mdxSource":{"compiledSource":"\"use strict\";const{Fragment:_Fragment,jsx:_jsx,jsxs:_jsxs}=arguments[0];const{useMDXComponents:_provideComponents}=arguments[0];function _createMdxContent(props){const _components={a:`a`,code:`code`,li:`li`,p:`p`,strong:`strong`,ul:`ul`,..._provideComponents(),...props.components},{Heading,Warning}=_components;if(!Heading)_missingMdxReference(`Heading`,true);if(!Warning)_missingMdxReference(`Warning`,true);return _jsxs(_Fragment,{children:[_jsx(Heading,{level:`1`,id:`changelog`,children:`Changelog`}),`\n`,_jsxs(_components.p,{children:[`Notable customer-visible changes to the Moss SDK (`,_jsx(_components.code,{children:`@viamoss/moss-sdk`}),`) and the\nMoss dashboard. From v0.13.0, the SDK version tracks the Moss platform version.`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-26-—-2026-11-18`,children:`0.16.26 — 2026-11-18`}),`\n`,_jsxs(_components.p,{children:[`SDK only: `,_jsx(_components.code,{children:`@viamoss/moss-sdk`}),` 0.16.26 is on npm. There are no new server\nimages or Helm chart. SDK 0.16.26 works with a 0.16.25 server, and hosted Moss\nis unchanged.`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`The Next button beside the chat input on guide steps is now as tall as the\ninput and lines up with it. Before, it was slightly shorter and sat a few\npixels lower than the input box.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-24–0-16-25-—-2026-11-16`,children:`0.16.24–0.16.25 — 2026-11-16`}),`\n`,_jsx(_components.p,{children:`0.16.24 and 0.16.25 are described together. 0.16.24 wasn’t published to npm\nor rolled out to hosted Moss, so the SDK and hosted Moss go from 0.16.23\nstraight to 0.16.25. 0.16.24’s self-hosted images and Helm chart were\npublished, but install 0.16.25 instead.`}),`\n`,_jsx(Heading,{level:`3`,id:`added`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`New appearance settings.`}),` All of them are optional, and set under\n`,_jsx(_components.code,{children:`appearance.chrome`}),` in your integration’s code; none is in the dashboard.\nUnset, nothing looks different.`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`relatedArticles.variant`}),`: `,_jsx(_components.code,{children:`'list'`}),` shows the related articles under an\nanswer as plain rows, with titles in the primary text color, a small\nsentence-case “Related articles” label and a document icon in the primary\ncolor. `,_jsx(_components.code,{children:`'cards'`}),`, the default, keeps the bordered cards.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`guideOffer.label`}),` and `,_jsx(_components.code,{children:`guideOffer.icon`}),`: the text and icon of the button\nthat offers a guide. The icon is `,_jsx(_components.code,{children:`'emoji'`}),` (🚀, the default), `,_jsx(_components.code,{children:`'outline'`}),`\n(an outline rocket in the button’s text color) or `,_jsx(_components.code,{children:`'none'`}),`.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`message.paragraphGap`}),`: the space between paragraphs, lists and other\nblocks in an answer, as a CSS length. Unset, they sit directly on one\nanother.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`startScreen.queryIcons`}),`: your own icon for each built-in\nsuggested-question icon name. Every question uses `,_jsx(_components.code,{children:`document`}),` unless\n`,_jsx(_components.code,{children:`zeroState.suggestedQueryIcons`}),` is `,_jsx(_components.code,{children:`'per-query'`}),`. A name without an entry\nkeeps the built-in icon.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`startScreen.queryFontWeight`}),`, `,_jsx(_components.code,{children:`queryGap`}),`, `,_jsx(_components.code,{children:`articlesPaddingX`}),` and\n`,_jsx(_components.code,{children:`articlesRowGap`}),`: the weight of the suggested questions and the gap\nbetween them, and the side padding of the recommended articles and the gap\nbetween their rows.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`inputBar.paddingY`}),` and `,_jsx(_components.code,{children:`inputBar.lineHeight`}),`: the input text’s top and\nbottom padding, and its line height as a number (`,_jsx(_components.code,{children:`'1.5'`}),`), a length\n(`,_jsx(_components.code,{children:`'20px'`}),`) or a percentage (`,_jsx(_components.code,{children:`'150%'`}),`).`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`inputBar.focusBorder`}),`: the input’s border color while it has focus.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`icon`}),` on the footer links: `,_jsx(_components.code,{children:`'external-link'`}),`, `,_jsx(_components.code,{children:`'ticket'`}),`, `,_jsx(_components.code,{children:`'none'`}),`, or\nyour own element, such as an inline SVG. The Help center icon follows its\nlabel, and the Open a ticket icon precedes it. Unset, Help center keeps\n”↗” and Open a ticket has no icon.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`guide.pageTint`}),`: dims the page around a guide’s highlight. `,_jsx(_components.code,{children:`true`}),` lays a\n36% dark tint over it. An object sets `,_jsx(_components.code,{children:`color`}),`, `,_jsx(_components.code,{children:`opacity`}),` (0 to 1), or\nboth. The chat never dims, clicks still reach the page, and an open modal\ndialog stays clear. The tint holds through step changes and lifts on a\nstep with nothing highlighted. Off by default.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`guide.targetBadges`}),`: `,_jsx(_components.code,{children:`'step'`}),` numbers the highlight’s badge\nwith the guide’s step number, as in the guide bar. Every target of a step\nshows that same number, so several targets don’t read as separate steps,\nand targets in one group, such as a row of tabs, share one badge.\n`,_jsx(_components.code,{children:`'within-step'`}),`, the default, keeps today’s numbering.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`guide.nextInBar`}),`: `,_jsx(_components.code,{children:`false`}),` moves Next from the guide bar to\nbeside the input box. Next moves beside the input on every step, click\nsteps included, and hides while Moss works and once the guide is finished.\nThe guide bar then shows only the plan and its progress, and the chat’s\nstep loader shows that Moss is working. Unset or `,_jsx(_components.code,{children:`true`}),`, the default,\nkeeps the guide bar’s Next. With both\n`,_jsx(_components.code,{children:`nextInBar`}),` and `,_jsx(_components.code,{children:`nextBesideInput`}),` set to `,_jsx(_components.code,{children:`false`}),` there’s no Next at all,\nand development builds warn in the console.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`loader`}),`: `,_jsx(_components.code,{children:`'steps'`}),` shows a short list of what Moss is doing\nwhile it works, such as “Reading the page” and “Planning the next step”.\nScreen readers hear the row in progress, except while the guide bar is\nalready announcing “Working…”. `,_jsx(_components.code,{children:`'line'`}),`, the default, keeps the one-line\nindicator.`]}),`\n`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Next beside the input box.`}),` On a guide step with nothing to click, and on\nfile-upload and confirmation steps, Next also shows beside the input box.\nOther click steps look the same as before, and it doesn’t show once the\nguide is finished. The guide bar’s Next stays. To keep Next only in the\nguide bar, set `,_jsx(_components.code,{children:`chrome.guide.nextBesideInput: false`}),`.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Self-hosted: Zendesk calls through a proxy.`}),` A new backend setting,\n`,_jsx(_components.code,{children:`ZENDESK_USE_ENV_PROXY`}),`, is off by default. When it’s on, Moss’s Zendesk\ncalls (connecting, syncing the ticket form and filing tickets) go through the\n`,_jsx(_components.code,{children:`http://`}),` proxy named in `,_jsx(_components.code,{children:`HTTPS_PROXY`}),`. A value without a scheme, such as\n`,_jsx(_components.code,{children:`proxy.example.com:3128`}),`, is read as `,_jsx(_components.code,{children:`http://`}),`, and `,_jsx(_components.code,{children:`NO_PROXY`}),` is honoured.\nAn `,_jsx(_components.code,{children:`https://`}),` or malformed proxy value isn’t used: the request isn’t sent,\nand the sync banner or the connection check says this server couldn’t reach\nZendesk through the proxy. With the setting off, nothing changes.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`You can type while Moss answers.`}),` The input stays editable during a\nreply. Send and Enter wait until the reply has arrived, and the text stays\nin the box. The input is disabled only while the connection is down.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`Next sends what you typed.`}),` With text in the input, a guide’s Next sends\nit as your message. With an empty input, Next goes to the next step, as\nbefore.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`No related articles while a guide runs.`}),` Replies during a running guide\ndon’t show the related-articles list. The answer that offers the guide keeps\nit. Sources that your application’s instructions ask for in the answer text\nare unchanged.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`The guide bar shows when Moss is working.`}),` While a request runs, a spinner and “Working…” take\nNext’s place, and screen readers announce it. When the request ends, Next\ncomes back, with the focus if it had it.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`The guide offer’s default label is “Start guide”, and it’s translated.`}),`\nIt was “Guide me”, in English for every user. Korean users now see 가이드\n시작.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`One line of input text is centred on the send button.`}),` When\n`,_jsx(_components.code,{children:`chrome.inputBar`}),` is set, in code or in the dashboard, the send button sits a\nfew pixels higher. With several lines, it stays level with the last one.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`Zendesk connection errors name the cause.`}),` With host-brokered filing,\nwhen `,_jsx(_components.strong,{children:`Test \u0026 connect`}),` or `,_jsx(_components.strong,{children:`Test connection`}),` can’t read the end-user ticket\nform, the message now says why: the HTTP status, a DNS failure, a timeout, a\nTLS failure, a failed connection, or a reply that isn’t a ticket form. A 404\nalso asks you to check the subdomain. Zendesk’s reply itself is never shown.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`Zendesk sync errors name the cause too.`}),` When a ticket-form sync fails,\nthe “Last sync had a problem” banner, in Configure > Integrations > Zendesk\nand on the Ticket intake page, now says why: the HTTP status Zendesk\nanswered, a DNS failure, a timeout, a TLS failure, a failed connection, or a\nreply that couldn’t be read. It no longer shows text from Zendesk’s reply.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsx(_components.p,{children:_jsx(_components.strong,{children:`Guide steps and guide offers.`})}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`When a step only asks the user to check something, such as a setting or a\nstatus, and the page shows the check passing, Moss says so and gives the\nnext step in the same reply. If the page shows something else, Moss says\nwhat it shows and stays on the step.`}),`\n`,_jsx(_components.li,{children:`Choices on the page, such as radio buttons, selects and links, are\nhighlighted, and the user’s pick moves the guide on.`}),`\n`,_jsx(_components.li,{children:`A step with nothing to click ends by pointing to Next, without saying\nwhere Next is on the screen.`}),`\n`,_jsx(_components.li,{children:`Moss treats a “where is…” question as a how-to. When the answer lists\nseveral places in your application, Moss names the most common one and\noffers a guide there. Questions about places outside your application get\nno offer. The offer is the answer’s last sentence, before any Sources list\nyour instructions ask for.`}),`\n`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`Browser extensions send the SDK version they bundle, so they get the\ncurrent guide behavior.`}),` Extension builds sent no SDK version, so their\nsessions got the older guide behavior whatever the application’s\n`,_jsx(_components.code,{children:`stateless_turn_policy`}),` setting said. Every extension built from this release\nsends it. Once its new build is installed:`]}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Ending a guide in the chat ends it for Moss too, so the next question\nisn’t answered inside the guide the user left. That covers closing the\nchat when `,_jsx(_components.code,{children:`closingChatEndsGuide`}),` is on, and filing a support ticket during\na guide.`]}),`\n`,_jsx(_components.li,{children:`Asking Moss to stop (“stop guiding me”, “exit the guide”) ends the guide.`}),`\n`,_jsx(_components.li,{children:`A guide with no progress ends on its own: after 2 hours if it was only\noffered, after 24 hours if it was running.`}),`\n`,_jsx(_components.li,{children:`Moss decides on each question whether to answer it or guide, instead of\nkeeping the mode an earlier question set.`}),`\n`]}),`\n`,_jsxs(_components.p,{children:[`An extension switches only when its new build is installed. Pages that load\na released SDK from npm or the CDN already had this behavior. An application\nwith `,_jsx(_components.code,{children:`stateless_turn_policy: false`}),` keeps the older behavior.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`SDK pre-releases get the current guide behavior.`}),` A pre-release of any\nversion after 0.10.0, such as `,_jsx(_components.code,{children:`0.17.0-beta.3`}),`, is now treated like a release.\nA page that loads one switches when the backend is upgraded, with no new\ninstall. Before, every pre-release got the older behavior. A pre-release of\n0.10.0 itself still does.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsxs(_components.p,{children:[_jsx(_components.strong,{children:`Several highlighted places are named, not numbered.`}),` With\n`,_jsx(_components.code,{children:`guide.targetBadges: 'step'`}),`, every highlight of a step shows the step’s\nnumber. When a guide step highlights more than one place, Moss’s reply now\nnames each one (“Click `,_jsx(_components.strong,{children:`Search`}),` or `,_jsx(_components.strong,{children:`Share`}),`”) instead of numbering\nthem 1, 2, 3. This needs the SDK from this release. It also covers the\nreply that starts a guide and highlights its first step.`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[`\n`,_jsx(_components.p,{children:`No database migrations in this release.`}),`\n`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-2`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`A guide’s Exit button is back.`}),` Open the guide bar’s step list: “Exit\nguide” is at the end of it, and asks before it ends the guide. Exiting\nremoves the guide’s highlight, and Moss ends the guide too.`]}),`\n`,_jsx(_components.li,{children:`After a guide’s Exit, clicking the element its step highlighted no longer\nsends the step.`}),`\n`,_jsx(_components.li,{children:`After pressing Next, clicking the highlighted element no longer sends the\nstep a second time. If Next’s request fails, the step comes back, so Next\ncan be pressed again.`}),`\n`,_jsx(_components.li,{children:`After exiting a guide with the keyboard, the focus stays in the message\ninput.`}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`The chat panel fits short browser windows.`}),` In a window shorter than\nthe panel, the panel opened with its header, and the New chat and Close\nbuttons, off screen. It now fits inside the window, shrinking if it has\nto, and gets its full size back in a taller window. The same goes after a\nresize, after Reset Chat Position, and for a position saved on an earlier\nvisit.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Screen readers name the chat header’s buttons.`}),` New chat and Close, and\non the classic header Reset Chat Position and Change Language, now have\nnames.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Screen readers hear once that Moss is working.`}),` With the default\nloader, a running guide was announced twice, and nothing was announced\nwhile a request ran after a guide had finished. Each is now announced\nonce, and the default loader no longer re-announces as its text animates.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Coming back to a session too old to resume.`}),` The “Starting fresh” card\nno longer has a working indicator behind it, and nothing can be sent to\nthe old session from behind the card.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`One session per first open.`}),` Loading a page or opening the chat for the\nfirst time starts at most one session. Before, it could start a second,\nempty one. The app’s settings are also read once per page load, not twice.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Dashboard: long application names.`}),` The desktop sidebar keeps its\nwidth, and at phone width the pages no longer scroll sideways.`]}),`\n`,_jsxs(_components.li,{children:[_jsxs(_components.strong,{children:[_jsx(_components.code,{children:`openChat`}),` and `,_jsx(_components.code,{children:`toggleChat`}),` open the chat at the position you pass.`]}),`\nThe position applies to that open only and isn’t saved. If the user moves\nor resizes the chat during that open, their placement is kept.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Next stays available when a click step’s setup gives up.`}),` When a\nstep’s target couldn’t be found, or Next or Exit was pressed while it was\nbeing set up, Next beside the input could stay hidden for the rest of the\nguide.`]}),`\n`,_jsxs(_components.li,{children:[`Guides work on more pages whose forms have fields named after built-in\npage properties or methods, such as `,_jsx(_components.code,{children:`submit`}),`, `,_jsx(_components.code,{children:`closest`}),` or `,_jsx(_components.code,{children:`matches`}),`.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`A request the model provider’s safety filter blocks gets its own answer.`}),`\nWhen a filter such as Model Armor or Gemini’s safety settings blocks a\nrequest or its reply, Moss answers “A safety filter blocked this request, so\nI can’t answer it. If it keeps happening on this page, please contact your\nadministrator.” It used to ask the user to rephrase. A blocked request counts\nas blocked, not as an error, and the session shows a blocked step.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`SDK rate limits: an unreachable limit store is logged as an error.`}),` With\n`,_jsx(_components.code,{children:`SDK_RATE_LIMITS_ENABLED`}),` on, a run of skipped checks is logged as an error\nwhatever the cause. Before, only timeouts counted, so a store that refused\nconnections was logged as a warning only.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Each question reaches Moss once.`}),` With the conversation log that’s the\ndefault since 0.16.1, every typed question went twice into the conversation\nMoss reads. So Moss took a conversation’s first question for a later one and\ndidn’t work out the user’s goal for the first answer, and a very short\nquestion searched the help articles with its words repeated. The first\nanswer stays as fast as before, and Moss now works out the goal alongside it.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Clicking a guide’s first step right after Moss offers it no longer ends\nthe guide`}),` with “I couldn’t recover this guide.”`]}),`\n`,_jsx(_components.li,{children:`Pressing Next while a click step is still setting up now moves the guide on.\nBefore, the press could be lost, and the guide bar kept showing “Working…”.`}),`\n`,_jsxs(_components.li,{children:[`With `,_jsx(_components.code,{children:`closingChatEndsGuide`}),` on, closing the chat right after pressing Next or\nsending a message no longer leaves the chat busy when it’s reopened.`]}),`\n`,_jsx(_components.li,{children:`Guide highlights no longer fail on pages whose forms have fields named after\nbuilt-in page properties.`}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Self-hosted: deleting a user’s data and missing buckets.`}),` A deletion is\nno longer certified complete when the user’s files were stored in a bucket\nthat the dashboard backend can’t find. The certificate notes the missing\nbucket, and the request can be retried once the bucket is configured.`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Helm:`}),` `,_jsx(_components.code,{children:`global.storageBuckets.recordings`}),` and `,_jsx(_components.code,{children:`.screenshots`}),` now set the\nbucket names for both backends. Rendering fails when the two backends name\ndifferent buckets, so `,_jsx(_components.code,{children:`helm template`}),`, `,_jsx(_components.code,{children:`install`}),` and `,_jsx(_components.code,{children:`upgrade`}),` stop with a\nmessage that names the setting. Set each name to the bucket the install\nalready uses; nothing moves.`]}),`\n`,_jsxs(_components.li,{children:[_jsxs(_components.strong,{children:[`Upgrading with `,_jsx(_components.code,{children:`--reuse-values`}),`:`]}),` add\n`,_jsx(_components.code,{children:`--set global.storageBuckets.recordings=rrweb-recordings`}),`, or upgrade\nwithout `,_jsx(_components.code,{children:`--reuse-values`}),`. An install that never changed these names and\nupgrades without it needs no action.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Known limit:`}),` for an application that recorded sessions before 0.16.1\nand has since set session recording to anything but on, recordings from\nbefore 0.16.1 may not be checked.`]}),`\n`]}),`\n`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Python, CVE-2026-119170 (High): fixed.`}),` The backend and worker images\nrequire the Python 3.14.10 build that fixes it.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`soupsieve 4.0`}),` in the backend and worker, which fixes CVE-2026-126190\nand CVE-2026-126191 (High).`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`opentelemetry-api 1.45.2`}),` in the backend and worker, which fixes\nCVE-2026-126360 (Medium).`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`URL rules:`}),` page addresses are matched against URL rules with a length\nlimit and a time limit, so an unusual address can’t hold up the service.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`known-issues`,children:`Known issues`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`The 0.16.23 known issues still apply, except the one about a guide’s Exit\ncontrol and the note about a missing recordings or snapshots bucket, both\nfixed above.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-23-—-2026-11-13`,children:`0.16.23 — 2026-11-13`}),`\n`,_jsx(Heading,{level:`3`,id:`added-2`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Closing the chat can end a running guide.`}),` With\n`,_jsx(_components.code,{children:`closingChatEndsGuide: true`}),` in the SDK config, closing the chat while a\nguide runs ends the guide, as its Exit control does. The highlight comes\noff, and a page refresh brings nothing back. It applies to the close button,\na `,_jsx(_components.code,{children:`data-moss-trigger`}),` toggle, `,_jsx(_components.code,{children:`AssistantButton`}),`, `,_jsx(_components.code,{children:`closeChat()`}),` and\n`,_jsx(_components.code,{children:`toggleChat()`}),`. A guide only offered, a guide already finished, a guide\nrunning in another tab and Moss’s own closes are left alone. It is off by\ndefault, and nothing changes until you turn it on.`]}),`\n`,_jsxs(_components.li,{children:[`New optional backend settings, all off or unchanged by default:`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`SDK_REQUIRE_ORIGIN`}),`: when on, SDK requests that carry no Origin or\nReferer, and every request for an application with no allowed domains,\nget 403 `,_jsx(_components.code,{children:`ORIGIN_REQUIRED`}),`. Leave it off unless every application has its\nlist filled in.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`SDK_RATE_LIMITS_ENABLED`}),`: per-minute limits on SDK session starts,\nqueries, streams and recording uploads, kept in Redis. A slow or\nunreachable Redis lets requests through. Current SDKs don’t wait out a\n429, so a limited request fails its turn.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`LLM_REQUEST_TIMEOUT_SECONDS`}),` (default `,_jsx(_components.code,{children:`45`}),`): the first attempt’s timeout\nfor each model request in a chat turn.`]}),`\n`]}),`\n`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-2`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Allowed domains are checked by exact host, on every SDK request.`}),` Check\neach application’s list before you upgrade:`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`An entry matches only that exact host: `,_jsx(_components.code,{children:`example.com`}),` no longer matches\n`,_jsx(_components.code,{children:`app.example.com`}),`. For subdomains, add a `,_jsx(_components.code,{children:`*.`}),` entry such as\n`,_jsx(_components.code,{children:`*.example.com`}),`. A `,_jsx(_components.code,{children:`*.`}),` entry matches subdomains at any depth but not the\nbare domain, so list both if Moss runs on both.`]}),`\n`,_jsxs(_components.li,{children:[`The check covers every SDK request from the page, not only the first\nconfiguration load. A page the list doesn’t cover gets 403\n`,_jsx(_components.code,{children:`DOMAIN_NOT_ALLOWED`}),`, and Moss doesn’t load there.`]}),`\n`,_jsxs(_components.li,{children:[`An entry with a port matches only that port. Browsers leave out the\ndefault port, so an entry ending in `,_jsx(_components.code,{children:`:443`}),` never matches an https page.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`Origin: null`}),`, which browsers send from sandboxed iframes and local\nfiles, is refused when the list isn’t empty.`]}),`\n`,_jsx(_components.li,{children:`An empty list is unchanged.`}),`\n`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Screenshot uploads need the user’s token.`}),` SDK 0.16.23 sends it. Older\nSDKs fall back to sending the screenshot inside the chat request, a few MB\neach, so check that your ingress accepts bodies that size on\n`,_jsx(_components.code,{children:`/api/v1/query`}),` until the SDK is upgraded. Upgrade the backend and\ndashboard first, then the SDK.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Saving a guide from the SDK needs the authoring grant.`}),` Save as Guide in\ndebug mode and in Moss Studio now needs a token with `,_jsx(_components.code,{children:`authoring: true`}),`, and\nsaves only the token user’s own session. An ordinary end-user token gets\n403, and the button says the user may not save guides. The dashboard’s own\nsave is unchanged.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`A signed token with an empty subject is refused.`}),` A JWT whose `,_jsx(_components.code,{children:`sub`}),` is\nempty, blank or not a string gets 401 `,_jsx(_components.code,{children:`INVALID_TOKEN`}),`, instead of running as\nthe user named in the request. Tokens with a real subject are unaffected.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`A model request that hangs ends sooner.`}),` Each request a chat turn makes\nhas a timeout, then one retry with what is left of the turn’s 120 seconds.\nA hung request now ends at about 118 seconds with “I’m sorry, that took too\nlong to answer. Please try again.” instead of the high-traffic message. A\nslow but working request completes on its retry.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Deletion requests that fail are marked failed,`}),` with details, instead of\nstaying in progress, and can be retried.`]}),`\n`,_jsx(_components.li,{children:`No database migrations in this release, and the Helm chart’s values are\nunchanged.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-3`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`A native modal dialog opened with `,_jsx(_components.code,{children:`showModal()`}),` no longer turns the page\ngrey under Moss when the page styles `,_jsx(_components.code,{children:`::backdrop`}),`, and the chat no longer\ninherits the dialog’s text layout, so its messages wrap.`]}),`\n`,_jsxs(_components.li,{children:[`A page whose form has a control named after a form property, such as\n`,_jsx(_components.code,{children:`parentElement`}),` or `,_jsx(_components.code,{children:`id`}),`, no longer hangs the tab or breaks page capture.`]}),`\n`,_jsx(_components.li,{children:`Deleting a user’s data now completes when their chats have analytics\ninsights, evaluation scores, monitor flags, action logs, page snapshots or\nguides. It also removes their model-call logs and proactive-guide events.`}),`\n`,_jsx(_components.li,{children:`A rate-limited model request that the client gave up on is retried.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-2`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Redaction.`}),` Redacted content no longer reaches Moss through a parent’s\ntext, accessible names and labels, interaction HTML, element fingerprints,\nthe validation summary or a clicked element’s text. This holds across open\nshadow roots and same-origin frames. Redacted alerts and fields are listed\nby tag only, so the summary still shows that they’re there.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`glibc, CVE-2026-84243 (High): fixed.`}),` All four images ship glibc 2.44-r17,\nwhich includes the 2.44-r16 fix.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Python, CVE-2026-119170 (High): not affected.`}),` It applies only when\nOpenSSL runs in FIPS mode, and no image installs a FIPS provider. Scanners\nmay still report it.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Chrome for Testing 157.0.8103.78`}),` in the worker, which fixes\nCVE-2026-125350 (High) and the advisories published on 11 November.`]}),`\n`,_jsx(_components.li,{children:`Python dependency updates, and addresses containing a NUL character are\nrefused before any lookup.`}),`\n`,_jsx(_components.li,{children:`The SDK package is published with an exact, integrity-checked npm.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`known-issues-2`,children:`Known issues`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`After a guide’s own Exit control, a click on the step’s target still sends\nthe step. Closing the chat with `,_jsx(_components.code,{children:`closingChatEndsGuide`}),` on doesn’t have this\ngap.`]}),`\n`,_jsxs(_components.li,{children:[`Self-hosted: if `,_jsx(_components.code,{children:`RECORDINGS_BUCKET`}),` or `,_jsx(_components.code,{children:`DOM_SNAPSHOTS_BUCKET`}),` names a bucket\nthat doesn’t exist, the deletion certificate reports the erasure complete\nwithout the request’s note about the missing bucket. Check that both name\nyour real buckets. A fix is planned for 0.16.24.`]}),`\n`,_jsx(_components.li,{children:`The 0.16.22 known issues still apply.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-22-—-2026-11-10`,children:`0.16.22 — 2026-11-10`}),`\n`,_jsx(Heading,{level:`3`,id:`added-3`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Returning after inactivity.`}),` Configure > Behavior > Session Behavior has\na new field, “When a user returns after inactivity”: “Ask to continue or\nstart new” (the default, as before) or “Start a new chat”. With “Start a new\nchat”, a user who comes back to a session past its inactivity timeout (30\nminutes by default) or its max age (2 hours by default) gets a new chat, with\nno card and no rating. This applies when Moss loads into a timed-out session,\nand when the user reopens the chat on a page left open, with the launcher,\n`,_jsx(_components.code,{children:`openChat()`}),` or a `,_jsx(_components.code,{children:`data-moss-trigger`}),` element. The previous chat can’t be\nreopened.`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`In the SDK, `,_jsx(_components.code,{children:`sessionConfig.onReturnAfterInactivity`}),` takes `,_jsx(_components.code,{children:`'new_chat'`}),` or\n`,_jsx(_components.code,{children:`'ask'`}),`. A value in your config wins. Left unset, the application’s\ndashboard setting applies, delivered at session start by backend 0.16.22\nand later; without one, `,_jsx(_components.code,{children:`'ask'`}),`. For npm embeds, only this field comes\nfrom the dashboard: the inactivity timeout, max age and `,_jsx(_components.code,{children:`showNotification`}),`\nstay the ones in your config. A config built with `,_jsx(_components.code,{children:`convertBackendConfig()`}),`\ntakes all four from the dashboard.`]}),`\n`,_jsx(_components.li,{children:`Update the backend and dashboard before the SDK. An older backend drops\nthe setting on save without an error, and an older SDK ignores it. SDK\n0.16.22 on an older backend asks, unless your config sets the field.`}),`\n`,_jsxs(_components.li,{children:[`Moss’s own opens, such as `,_jsx(_components.code,{children:`askMoss()`}),` and proactive or onboarding flows,\ndon’t check. `,_jsx(_components.code,{children:`openChat()`}),` followed by `,_jsx(_components.code,{children:`sendMessage()`}),` sends the message in\nthe new chat once it connects. Moss holds one such message, and logs a\nconsole warning when it can’t send it.`]}),`\n`,_jsxs(_components.li,{children:[`Guide steps taken with the chat closed, and activity on the same session\nin another tab, count as activity. A guide idle past the timeout ends with\nits session; if it ran in this tab, `,_jsx(_components.code,{children:`Moss Plan Finished`}),` reports it with\n`,_jsx(_components.code,{children:`outcome: 'abandoned'`}),` under the old session’s `,_jsx(_components.code,{children:`sessionId`}),`.`]}),`\n`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Moving the chat window.`}),` The chat window also moves from the empty space\nin the conversation and around the message box, not only from its header and\nedges, so a window whose header is off screen can be dragged back. Messages,\nlinks, buttons, cards, the guide bar and the scrollbar don’t drag, and a drag\nselects no text. On touch, the conversation scrolls, and the window moves\nfrom the header, the edges and the area around the message box.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-3`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`The worker refuses private addresses on its own fetches.`}),` Image\ndownloads, sitemaps, discovery’s page sampling, and Document360 discovery and\nscraping now reach public addresses only. Check these before you upgrade:`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`A forward proxy is no longer used for Document360, image and sitemap\nfetches.`}),` These fetches connect directly and ignore `,_jsx(_components.code,{children:`HTTP_PROXY`}),` and\n`,_jsx(_components.code,{children:`HTTPS_PROXY`}),`, and there is no setting yet to send them through a proxy.\nIf your worker’s egress requires one, contact us before upgrading. Firecrawl,\nthe LLM and embedding providers, Pinecone, storage uploads, Slack and the\nbrowser’s page loads during discovery are unchanged.`]}),`\n`,_jsxs(_components.li,{children:[`Images and sitemaps on an intranet stop working until their host or range\nis listed in the new worker setting `,_jsx(_components.code,{children:`WORKER_FETCH_ALLOWLIST`}),`\n(comma-separated hosts and CIDRs, such as\n`,_jsx(_components.code,{children:`wiki.corp.example.com,10.20.0.0/16`}),`). It is empty by default.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`localhost`}),` needs its own entry. Cloud metadata addresses can never be\nallowed. An invalid entry stops the worker at boot. Your object storage\n(`,_jsx(_components.code,{children:`S3_ENDPOINT`}),`) needs no entry.`]}),`\n`,_jsx(_components.li,{children:`A refused image is recorded as failed and keeps its original address. A\ndiscovery start URL on a refused host fails at once. A downloaded body that\nisn’t an image is never stored.`}),`\n`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Document360 API host.`}),` It must be a Document360 host\n(`,_jsx(_components.code,{children:`*.document360.io`}),` or `,_jsx(_components.code,{children:`*.document360.com`}),`, such as `,_jsx(_components.code,{children:`apihub.document360.io`}),`).\nAny other host is refused when it’s saved, and one saved earlier is refused\nat sync, with a message to enter it again. A help center on its own domain\nis fine, because that isn’t the API host.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Zendesk subdomain.`}),` It must be the account name only, such as `,_jsx(_components.code,{children:`acme`}),`, not\na full address. Upper case is accepted and stored in lower case.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`CSV exports`}),` (conversations, traffic logs and the audit log). A cell that\nstarts with `,_jsx(_components.code,{children:`=`}),`, `,_jsx(_components.code,{children:`+`}),`, `,_jsx(_components.code,{children:`-`}),`, `,_jsx(_components.code,{children:`@`}),`, a tab or a carriage return gets a leading\napostrophe, so spreadsheets open it as text, never as a formula. That\nincludes negative numbers: `,_jsx(_components.code,{children:`-1`}),` exports as `,_jsx(_components.code,{children:`'-1`}),`.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Slack alerts.`}),` Alert text is escaped and length-limited. Worker job\nalerts carry the outcome, an error code and counts, but not the raw error\ntext; the details stay in the job’s record in Moss.`]}),`\n`,_jsxs(_components.li,{children:[`New optional setting: `,_jsx(_components.code,{children:`WORKER_FETCH_ALLOWLIST`}),`, on the worker. In the Helm\nchart’s `,_jsx(_components.code,{children:`values.yaml`}),`, only commented examples for it are added.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Support tickets during a guide.`}),` While a ticket card is open, the guide\nbar is hidden. Cancelling the card brings the guide back on the same step.\nWhen the ticket is filed, or its outcome is unconfirmed, the guide ends and\nstays ended: `,_jsx(_components.code,{children:`onEvent`}),` reports `,_jsx(_components.code,{children:`Moss Ticket Submitted`}),`, then\n`,_jsx(_components.code,{children:`Moss Plan Finished`}),` with `,_jsx(_components.code,{children:`outcome: 'abandoned'`}),`. A ticket reported as failed\nleaves the guide running. A guide started after the ticket shows its bar as\nusual.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`The ticket card opens on Moss’s reply.`}),` When Moss drafts a support ticket,\nthe chat opens on Moss’s message above the ticket form, not on the bottom of\nthe form.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Rating after a filed ticket.`}),` Once a support ticket is filed, “Was this\nconversation helpful?” appears at once, under the ticket confirmation, so the\nticket number and its link stay in view. Answering it leaves the conversation\nas it is, and New chat doesn’t ask again for that conversation. The next\nmessage or guide step removes it. It doesn’t appear for a ticket that failed,\ncame back unconfirmed or was cancelled. A rating that can’t be sent brings\nthe buttons back.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`A guide step after a long pause.`}),` When a user idles past the inactivity\ntimeout mid-guide, then clicks a step’s target that loads a new page, the new\npage keeps the session and continues the guide, with no card to continue or\nstart new.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Saving session settings.`}),` A configuration save merges `,_jsx(_components.code,{children:`sessionConfig`}),`\nwith the stored settings: a save that sends only some session settings keeps\nthe others, and a setting sent as `,_jsx(_components.code,{children:`null`}),` is cleared. A save with\n`,_jsx(_components.code,{children:`sessionConfig: null`}),` no longer clears them all.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Default loading-indicator selectors.`}),` With the loading-indicators\nstability layer on and its default selectors, `,_jsx(_components.code,{children:`skeleton`}),`, `,_jsx(_components.code,{children:`spinner`}),` and\n`,_jsx(_components.code,{children:`loader`}),` classes match in any case.`]}),`\n`,_jsx(_components.li,{children:`Every SDK change in this release works on any backend, except the dashboard\nsetting for returning after inactivity, which needs backend 0.16.22.`}),`\n`,_jsxs(_components.li,{children:[`No database migrations in this release. The one new environment setting is\nthe worker’s optional `,_jsx(_components.code,{children:`WORKER_FETCH_ALLOWLIST`}),`, above.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-4`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Moss no longer reads a page that is still drawing its loading placeholders.\nBefore it sends a turn’s page context, the SDK waits up to 4 seconds for\nvisible placeholders, such as skeletons, to clear, so answers describe the\nloaded page instead of saying it is still loading. With none on screen there\nis no wait. Placeholders that never clear cost one wait, and are then skipped\nuntil they’re gone or the page’s address changes. The settings are under\n`,_jsx(_components.code,{children:`stability.placeholderGuard`}),` (`,_jsx(_components.code,{children:`enabled`}),`, `,_jsx(_components.code,{children:`timeoutMs`}),`, `,_jsx(_components.code,{children:`excludeSelectors`}),`,\n`,_jsx(_components.code,{children:`additionalSelectors`}),` and `,_jsx(_components.code,{children:`selectors`}),`). When you set\n`,_jsx(_components.code,{children:`stability.loadingIndicators.selectors`}),`, the wait uses that list.`]}),`\n`,_jsx(_components.li,{children:`A turn that starts while an earlier one is still waiting for the page to\nsettle now waits too. It could read the page with no wait.`}),`\n`,_jsxs(_components.li,{children:[`A guide step whose click opens a new tab, through a `,_jsx(_components.code,{children:`target=_blank`}),` link,\n`,_jsx(_components.code,{children:`window.open()`}),` or a link that redirects, brings the chat up in the new tab\nat the next step, and the step is sent once. A same-tab redirect, or a page\nthat rewrites its address as it loads, no longer stalls the guide. Switching\ntabs right after a step’s click no longer ends the guide. This fixes the\n0.16.21 known issue for a page whose address changes as it loads.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-3`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Integration hosts for Document360 and Zendesk are now validated, and CSV\nexports open safely in spreadsheets.`}),`\n`,_jsx(_components.li,{children:`Alerts and audit records are hardened against untrusted input.`}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Worker fetches of private addresses (High).`}),` A crawled page could point\nan image or sitemap link at an internal address, and the worker would fetch\nit. The worker now refuses private, loopback, link-local and metadata\naddresses on its own fetches, and stores only bodies that are images.`]}),`\n`,_jsx(_components.li,{children:`The images are rebuilt on current base-image packages, with no dependency\nchanges.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`known-issues-3`,children:`Known issues`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Some valid images are refused and keep their original address: a UTF-16\nSVG, an SVG that ends in a comment containing `,_jsx(_components.code,{children:`\u003c/svg>`}),`, an AVIF or HEIC whose\nlast box has size 0, and an SVG with a prefixed DOCTYPE name.`]}),`\n`,_jsx(_components.li,{children:`The 0.16.21 known issues for a guide whose starting answer is lost, in one\ntab or with a second tab, still apply, as do the other two 0.16.20 known\nissues for guides in more than one tab.`}),`\n`,_jsx(_components.li,{children:`“Retry failed pages” counts and retries only pages that couldn’t be fetched.\nTo run pages that failed indexing again, refresh the source or edit the page.`}),`\n`,_jsxs(_components.li,{children:[`With “Start a new chat”, a chat left open while the user is away keeps its\nconversation: Moss checks only as it loads and as the chat opens. Calling\n`,_jsx(_components.code,{children:`openChat()`}),` and then `,_jsx(_components.code,{children:`askMoss()`}),` in one handler, past the timeout, starts\none extra session that is never used.`]}),`\n`,_jsxs(_components.li,{children:[`If the page reloads mid-guide while a ticket card is open, the step’s\nhighlight comes back with the guide bar hidden, and a click on it completes\nthe step. When a ticket is filed in a tab that only shows the guide, the tab\nrunning it reports `,_jsx(_components.code,{children:`Moss Plan Finished`}),` but keeps the guide bar until a later\nanswer clears it.`]}),`\n`,_jsxs(_components.li,{children:[`Placeholders inside shadow roots aren’t seen. A placeholder the page\nre-creates on every render is waited on at each turn; exclude it with\n`,_jsx(_components.code,{children:`stability.placeholderGuard.excludeSelectors`}),`.`]}),`\n`,_jsxs(_components.li,{children:[`The guide stays in the first tab when a step’s new tab can’t be tied to the\nclick: the tab opened in the background on a different address, the page\nopened it only after the step was sent, a page-wide `,_jsx(_components.code,{children:`no-referrer`}),` policy or\n`,_jsx(_components.code,{children:`window.open(url, '_blank', 'noreferrer')`}),` hid where it came from, or it was\nreached through more than one intermediate page. A `,_jsx(_components.code,{children:`target=_blank`}),` link to a\npage without Moss waits out the step’s window, 30 seconds by default, as\nsince 0.16.19.`]}),`\n`,_jsx(_components.li,{children:`Within 5 seconds of a step’s click, a tab the user opens by hand after a link\nthat sends no referrer, or another link the user opens from the same page,\ncan take the step.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-21-—-2026-11-06`,children:`0.16.21 — 2026-11-06`}),`\n`,_jsx(Heading,{level:`3`,id:`changed-4`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`A source whose pages can’t be indexed ends in Error.`}),` It used to end\nReady with no content or with part of it. Each such page shows “Re-indexing\nfailed” in its page view. A refresh that fails this way keeps the current\nversion serving, with all of its content. The processing count on a source\nadvances while pages are indexed.`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`A Ready source that still has a page from an earlier run that can never be\nindexed stays Ready. Until that page is refreshed or edited, each later\nprocessing run records the error on it and sends a failed notification.`}),`\n`,_jsxs(_components.li,{children:[`The failed notification (`,_jsx(_components.code,{children:`CHUNKING_FAILED`}),`) and the worker’s log say how\nmany pages failed, as `,_jsx(_components.code,{children:`N/M pages failed chunking (K indexed).`}),`, then give\nthe latest error as one of a fixed set of descriptions, never the raw\nerror text.`]}),`\n`,_jsxs(_components.li,{children:[`This also covers the 0.16.19 known issue on Vertex AI `,_jsx(_components.code,{children:`eu`}),` and `,_jsx(_components.code,{children:`us`}),`: a\nsource on `,_jsx(_components.code,{children:`gemini-embedding-001`}),` now ends in Error instead of Ready with no\ncontent.`]}),`\n`]}),`\n`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Ingestion errors keep no raw error text.`}),` A page’s or a job’s error in the\ningestion API, and a source’s last error, are now a fixed description: an\nerror code, an HTTP status, an exception type or a provider name, such as\nOpenAI. They no longer include an exception’s message or a provider’s\nresponse. Errors stored before the upgrade are returned the same way. What\nthe dashboard shows is unchanged: it shows these errors in dev mode only. The\nworker’s log keeps the full message.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Document360 API token on save.`}),` Spaces and line breaks at the ends of a\ntoken are removed when it’s saved. A token with a line break, or another\ncharacter that isn’t printable ASCII, inside it is refused, with a message\nto paste it again. A token saved earlier with a trailing line break is now\nsent without it.`]}),`\n`,_jsx(_components.li,{children:`No database migrations or new settings in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-5`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Direct Zendesk filing sends nested branch fields.`}),` Fields that a\nconditional field opens at any depth, such as a recording type under a\nproduct area, are now sent. Tickets on those branches used to be held back\nas missing a required field.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Host-brokered ticket card.`}),` When a branch of the ticket form requires a\ntext field that Moss fills with the user’s role, such as “Your Role”, the\ncard now shows the role the user gave. It used to show an empty row.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Plan events with Moss open in more than one tab`}),` (SDK only).`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`A guide step the user completes with a click, in a tab that was only\nshowing the guide, now reports `,_jsx(_components.code,{children:`Moss Plan Step Completed`}),`, and\n`,_jsx(_components.code,{children:`Moss Plan Finished`}),` when it was the last step. The click takes the guide\nover in that tab, as in 0.16.20. In 0.16.20 the tab could report neither\nevent for a step that doesn’t open another page, which covers most\n“Click …” steps.`]}),`\n`,_jsxs(_components.li,{children:[`Pressing Start Guide on an offer after another tab has already started\nthat guide no longer reports `,_jsx(_components.code,{children:`Moss Plan Started`}),`, or the other tab’s\ncompleted steps, a second time. The tab only shows the guide, and takes it\nover when the user continues it there, with Next or a step.`]}),`\n`]}),`\n`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-4`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsxs(_components.strong,{children:[`Browser in `,_jsx(_components.code,{children:`moss-worker`}),`.`]}),` Chrome for Testing moves from 156.0.8078.80 to\n157.0.8103.38, which fixes 26 Critical and 54 High advisories in 156. The\nother three images don’t include the browser.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`glibc, CVE-2026-84243 (High): no fix yet, assessed.`}),` Your scanner may\nreport it in glibc 2.44 in all four images, and no fixed glibc is published\nyet. Exploiting it needs an attacker-controlled `,_jsx(_components.code,{children:`LANGUAGE`}),`, an active\nmessage locale other than C or POSIX, and a crafted message catalog the\nprocess can read. The 0.16.21 images run with the C locale, set no locale\nvariable and install no other locale definition. The fixed glibc ships in\nthe first release after one is published. If your deployment sets `,_jsx(_components.code,{children:`LANG`}),`,\n`,_jsx(_components.code,{children:`LANGUAGE`}),`, `,_jsx(_components.code,{children:`LC_ALL`}),`, `,_jsx(_components.code,{children:`LC_MESSAGES`}),` or `,_jsx(_components.code,{children:`LOCPATH`}),`, or mounts locale files,\ncontact us and we’ll reassess.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`sqlite-libs, CVE-2026-119586 (High): not affected.`}),` The advisory is in the\nSQLite command-line shell’s `,_jsx(_components.code,{children:`.recover`}),` command. No image includes the\n`,_jsx(_components.code,{children:`sqlite`}),` CLI, and the library in the backend and worker images has no\nrecover functions. Your scanner may still report it, with no fixed version.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Error text in the ingestion API.`}),` Through 0.16.20, the ingestion API\nreturned a page’s or a job’s stored error text to any member of the source’s\norganization. In rare cases that text repeated a credential: a Document360\ntoken saved with a line break in it, or a token in a source’s URL. 0.16.21\nstores no such text, and returns only the fixed description for errors\nstored before the upgrade. If a Document360 token was saved with a line\nbreak, rotate it.`]}),`\n`,_jsxs(_components.li,{children:[`Backend dependency security update (`,_jsx(_components.code,{children:`idna`}),`), to its first patched version,\n3.15, for a Medium advisory.`]}),`\n`,_jsxs(_components.li,{children:[`The images are rebuilt on current base-image packages. The `,_jsx(_components.code,{children:`moss-backend`}),`\nand `,_jsx(_components.code,{children:`moss-worker`}),` builds also place a copy of each installed Python\npackage’s own SBOM where scanners look, so image scans see those packages’\ncomponents. Nothing changes at run time.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`known-issues-4`,children:`Known issues`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`This replaces the first 0.16.20 known issue. If the backend starts a guide\nbut the answer doesn’t reach the tab, that tab only shows the guide. This\nhappens when the answer to a typed yes is lost, or when the SDK’s automatic\nretry of a 503 answers instead of the first attempt. The tab doesn’t\ncontinue the guide after a reload until the user continues it there, with\nNext or a step. It never reports that guide’s `,_jsx(_components.code,{children:`Moss Plan Started`}),`, even\nthen: Next or a step there reports only `,_jsx(_components.code,{children:`Moss Plan Step Completed`}),`. When the\nanswer to Start Guide is lost to a network or server error, pressing Start\nGuide again runs the guide in that tab and reports `,_jsx(_components.code,{children:`Moss Plan Started`}),` once.`]}),`\n`,_jsxs(_components.li,{children:[`If a tab’s Start Guide gets no answer because of a network or server error,\nand another tab starts the same guide before this tab’s next answer, both\ntabs report `,_jsx(_components.code,{children:`Moss Plan Started`}),`. After a guide overview, the same applies to\nany guide another tab starts before the user presses Start Guide again.`]}),`\n`,_jsx(_components.li,{children:`The other two 0.16.20 known issues for guides in more than one tab still\napply.`}),`\n`,_jsx(_components.li,{children:`A guide step into a page that redirects or changes its address as it loads,\nsuch as a changed query value, may not bring up the chat in the new tab; the\nguide then carries on in the first tab after 30 seconds. In the same tab,\nthe chat comes back but the guide can stall. Fixed in 0.16.22.`}),`\n`,_jsx(_components.li,{children:`“Retry failed pages” counts and retries only pages that couldn’t be fetched.\nTo run pages that failed indexing again, refresh the source or edit the page.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-20-—-2026-11-04`,children:`0.16.20 — 2026-11-04`}),`\n`,_jsx(Heading,{level:`3`,id:`added-4`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Pinecone private endpoint (AWS PrivateLink).`}),` With\n`,_jsx(_components.code,{children:`PINECONE_USE_PRIVATE_ENDPOINT=true`}),` (off by default), sdk-backend,\ndashboard-backend and the worker still look the index up on\n`,_jsx(_components.code,{children:`api.pinecone.io`}),`, then send all data-plane traffic (search, fetch, upsert\nand delete) to the index’s private host,\n`,_jsx(_components.code,{children:`\u003cindex>.svc.private.\u003c...>.pinecone.io`}),`, which Moss reads from the index\ndescription; there is no host to configure. `,_jsx(_components.code,{children:`api.pinecone.io`}),` must stay\nreachable from all three workloads.`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`There is no fallback to the public host. If the index’s Pinecone project\nhas no private endpoint, Moss doesn’t connect to the index: chats answer\nwithout the application’s knowledge base, deleting a source fails, and\nchunking jobs fail before they touch a source’s pages or vectors. Each\nlogs an error that names the index and the setting.`}),`\n`,_jsxs(_components.li,{children:[`Set it on all three workloads, with the upper-case name and the same\nvalue. `,_jsx(_components.code,{children:`true`}),`, `,_jsx(_components.code,{children:`t`}),`, `,_jsx(_components.code,{children:`yes`}),`, `,_jsx(_components.code,{children:`y`}),`, `,_jsx(_components.code,{children:`on`}),` and `,_jsx(_components.code,{children:`1`}),` turn it on, in any case;\n`,_jsx(_components.code,{children:`false`}),`, `,_jsx(_components.code,{children:`f`}),`, `,_jsx(_components.code,{children:`no`}),`, `,_jsx(_components.code,{children:`n`}),`, `,_jsx(_components.code,{children:`off`}),` and `,_jsx(_components.code,{children:`0`}),` leave it off. Any other value,\nincluding an empty one or one with surrounding spaces or quotes, stops the\nbackends from starting and fails every chunking job.`]}),`\n`,_jsxs(_components.li,{children:[`Each process logs `,_jsx(_components.code,{children:`Pinecone data-plane host: private`}),` (or `,_jsx(_components.code,{children:`public`}),`) the\nfirst time it opens the index. The line shows the host Moss picked, not\nthat it is reachable.`]}),`\n`,_jsxs(_components.li,{children:[`Before turning on Pinecone’s private-endpoint-only restriction for the\nproject, check that Pinecone answers through the private host, since a\nwrong DNS record or security group still logs `,_jsx(_components.code,{children:`private`}),`. On sdk-backend,\none chat turn that uses the knowledge base logs the `,_jsx(_components.code,{children:`private`}),` line, then\n`,_jsx(_components.code,{children:`Pinecone multi-namespace search completed`}),` with `,_jsx(_components.code,{children:`results=N/M`}),` and N above\n0, and no `,_jsx(_components.code,{children:`search failed`}),`. On the worker, one knowledge-source refresh logs\nthe `,_jsx(_components.code,{children:`private`}),` line and the source ends Ready with more than 0 chunks. On\ndashboard-backend, which may not log the line for a while, confirm the\nvariable is set on its deployment. With the restriction on, Pinecone\nrejects data-plane requests that don’t come through the endpoint, so a\nworkload still on the public host loses retrieval or indexing.`]}),`\n`,_jsx(_components.li,{children:`The setting was tested against a mocked Pinecone API, not a live\nPrivateLink endpoint, so the check above is the test on your install.`}),`\n`]}),`\n`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-5`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`New optional setting: `,_jsx(_components.code,{children:`PINECONE_USE_PRIVATE_ENDPOINT`}),`. In the Helm chart’s\n`,_jsx(_components.code,{children:`values.yaml`}),`, only commented examples for it are added, on sdk-backend,\ndashboard-backend and the worker; the chart README documents it. With the\nsetting off, Moss sends the same Pinecone requests to the same hosts as\n0.16.19.`]}),`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-6`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`With Moss open in more than one tab, a guide runs only in the tab where the\nuser started it. Another tab can show it, and takes it over only when the\nuser continues it there. Plan events (`,_jsx(_components.code,{children:`Moss Plan Started`}),`,\n`,_jsx(_components.code,{children:`Moss Plan Step Completed`}),`, `,_jsx(_components.code,{children:`Moss Plan Finished`}),`) come only from the tab the\nguide runs in, so each guide counts once; in 0.16.19 a second tab could\nreport them again. A guide exited from another tab is reported as\n`,_jsx(_components.code,{children:`Moss Plan Finished`}),` with `,_jsx(_components.code,{children:`outcome: 'abandoned'`}),` by the tab that ran it. The\nfix needs both the 0.16.20 backend and SDK 0.16.20.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-5`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Backend dependency security updates (`,_jsx(_components.code,{children:`h2`}),`, `,_jsx(_components.code,{children:`hpack`}),`, `,_jsx(_components.code,{children:`langgraph`}),`,\n`,_jsx(_components.code,{children:`langgraph-sdk`}),`, `,_jsx(_components.code,{children:`soupsieve`}),`) and worker dependency security updates\n(`,_jsx(_components.code,{children:`multidict`}),`, `,_jsx(_components.code,{children:`soupsieve`}),`), each to its first patched version, for Medium\nadvisories.`]}),`\n`,_jsxs(_components.li,{children:[`The `,_jsx(_components.code,{children:`moss-dashboard`}),` and `,_jsx(_components.code,{children:`moss-dashboard-oidc`}),` builds install one exact,\nhash-checked pnpm, 10.34.7, instead of a floating pnpm at build time.`]}),`\n`,_jsx(_components.li,{children:`There is no other Dockerfile change. The images are rebuilt on current\nbase-image packages.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`known-issues-5`,children:`Known issues`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`If the answer that starts a guide doesn’t reach the tab, for example after\na retried 503, that tab only shows the guide. It reports no\n`,_jsx(_components.code,{children:`Moss Plan Started`}),`, and doesn’t continue the guide after a reload until the\nuser continues it there, with Next or a step.`]}),`\n`,_jsxs(_components.li,{children:[`When another tab takes a guide over, with Next or a step there, the original\ntab still reports `,_jsx(_components.code,{children:`Moss Plan Step Completed`}),` for the other tab’s steps if its\nuser asks something later. A New chat in the original tab still ends the\nguide on the device and reports it finished there.`]}),`\n`,_jsxs(_components.li,{children:[`If the tab running a guide is mid page load when a tab that only shows the\nguide exits it, no tab reports that `,_jsx(_components.code,{children:`Moss Plan Finished`}),`.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-19-—-2026-11-03`,children:`0.16.19 — 2026-11-03`}),`\n`,_jsx(Heading,{level:`3`,id:`added-5`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`SDK analytics events.`}),` Pass `,_jsx(_components.code,{children:`onEvent`}),` in the provider config to forward\nMoss usage to your analytics, for example\n`,_jsx(_components.code,{children:`onEvent: (e) => window.analytics?.track(e.name, e.properties)`}),`. Each event\nis `,_jsx(_components.code,{children:`{ name, properties }`}),`, named in Segment’s “Object Action” form. Twelve\nevents cover the chat, questions and answers, errors, guided plans, feedback\nand support tickets. `,_jsx(_components.code,{children:`MOSS_EVENT_NAMES`}),` lists them, and the SDK README\ndocuments each event’s properties. `,_jsx(_components.code,{children:`Moss Question Asked`}),` carries\n`,_jsx(_components.code,{children:`source: 'user' | 'host'`}),`, where `,_jsx(_components.code,{children:`'host'`}),` marks a question sent with\n`,_jsx(_components.code,{children:`askMoss()`}),`, counted once as its request leaves. Question text is left out\nunless you set `,_jsx(_components.code,{children:`eventQueryText`}),` to `,_jsx(_components.code,{children:`'include'`}),` or a function. A handler that\nthrows is logged and ignored, and leaving `,_jsx(_components.code,{children:`onEvent`}),` unset changes nothing.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Starting Moss on demand.`}),` For hosts that mount Moss only when the user\nasks for it, `,_jsx(_components.code,{children:`shouldStartMoss()`}),` from `,_jsx(_components.code,{children:`@viamoss/moss-sdk/start`}),` (no React)\ntells the page, as it loads, whether to mount Moss. It returns true when the\nchat was open in this tab before the page changed, while a guide is running\nin this tab, while an `,_jsx(_components.code,{children:`askMoss()`}),` question waits in this tab, or when a guide\nstep the user took is waiting to continue on this page (30 seconds by\ndefault). Mount Moss when it returns true, and don’t open or toggle the chat\nyourself. It needs `,_jsx(_components.code,{children:`stability.afterReload.enabled: true`}),`; if you set\n`,_jsx(_components.code,{children:`stability.afterReload.pendingTTL`}),`, pass the same value. It only reads\nbrowser storage and never throws.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Opening Moss with a question.`}),` `,_jsx(_components.code,{children:`askMoss(question)`}),`, also exported from\n`,_jsx(_components.code,{children:`@viamoss/moss-sdk/start`}),`, hands a question from your own assistant or help\nwidget to Moss: Moss starts a new chat, opens it and sends the question as\nthe user’s first message. It returns `,_jsx(_components.code,{children:`{ accepted: true, id, queued }`}),` or\n`,_jsx(_components.code,{children:`{ accepted: false, reason: 'empty' | 'unavailable' }`}),`, and never throws.\nWith `,_jsx(_components.code,{children:`queued: true`}),`, mount Moss without opening the chat within 30 seconds\n(`,_jsx(_components.code,{children:`ttlMs`}),` changes that). Call it in the same window and on the same origin as\nMoss, and open the chat with `,_jsx(_components.code,{children:`openChat()`}),`, not a toggle or a\n`,_jsx(_components.code,{children:`[data-moss-trigger]`}),` click: a toggle while a question waits closes the chat\nand drops the question. A chat or guide in progress ends as New chat ends it.`]}),`\n`,_jsxs(_components.li,{children:[_jsxs(_components.strong,{children:[`Vertex AI `,_jsx(_components.code,{children:`eu`}),` and `,_jsx(_components.code,{children:`us`}),` multi-regions.`]}),` With `,_jsx(_components.code,{children:`GOOGLE_AUTH_MODE=vertex`}),`\nand `,_jsx(_components.code,{children:`GOOGLE_CLOUD_LOCATION=eu`}),`, chat, `,_jsx(_components.code,{children:`gemini-embedding-2`}),` embeddings and\nimage annotation all go to `,_jsx(_components.code,{children:`aiplatform.eu.rep.googleapis.com`}),`; `,_jsx(_components.code,{children:`us`}),` works the\nsame way on `,_jsx(_components.code,{children:`aiplatform.us.rep.googleapis.com`}),`. Set the location on both\nbackends and the worker, and allow egress to that host from all three.\nVertex on `,_jsx(_components.code,{children:`global`}),` or a single region sends the same requests to the same\nhosts as before.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`OIDC session renewal.`}),` With `,_jsx(_components.code,{children:`OIDC_REFRESH_TOKENS=true`}),` (off by default) on\nthe `,_jsx(_components.code,{children:`moss-dashboard-oidc`}),` container, the dashboard renews the user’s ID token\nwith a refresh token, so sessions outlast the IdP’s ID-token lifetime (60\nminutes on Okta). Allow the Refresh Token grant for the Moss application in\nthe IdP first and, for an Okta custom authorization server, `,_jsx(_components.code,{children:`offline_access`}),`\nin its access policy. Without the access-policy change, every sign-in fails\nonce the setting is on.`]}),`\n`,_jsxs(_components.li,{children:[_jsxs(_components.strong,{children:[_jsx(_components.code,{children:`security.txt`}),`.`]}),` The backend serves an RFC 9116 file at\n`,_jsx(_components.code,{children:`/.well-known/security.txt`}),`, without sign-in and in every service mode, and\n`,_jsx(_components.code,{children:`/security.txt`}),` redirects there. The contact defaults to\n`,_jsx(_components.code,{children:`mailto:security@viamoss.ai`}),`; set `,_jsx(_components.code,{children:`SECURITY_TXT_CONTACT`}),` to a `,_jsx(_components.code,{children:`mailto:`}),` or\n`,_jsx(_components.code,{children:`https:`}),` URI to list your own.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-6`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Image annotator default model.`}),` With `,_jsx(_components.code,{children:`ANNOTATOR_LLM_MODEL`}),` unset, the\nworker uses `,_jsx(_components.code,{children:`gemini-3.8-flash`}),` at low thinking, replacing `,_jsx(_components.code,{children:`gemini-2.5-flash`}),`,\nwhich Google retired on 2026-10-20. An explicit `,_jsx(_components.code,{children:`gemini-3.8-flash`}),` also moves\nto low thinking, with a 4,096-token output limit. Other models are\nunchanged.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`OIDC sign-in.`}),` Users in neither `,_jsx(_components.code,{children:`OIDC_ADMIN_GROUPS`}),` nor\n`,_jsx(_components.code,{children:`OIDC_MEMBER_GROUPS`}),` see an Access Denied page at sign-in. If the\ndashboard-serving backend’s `,_jsx(_components.code,{children:`OIDC_AUDIENCE`}),` lacks the OIDC client ID, users\nreturn to sign-in after each sign-in; add the client ID. Users signed in\nbefore the upgrade sign in once more.`]}),`\n`,_jsx(_components.li,{children:`Dashboard toasts appear at the bottom right, in both dashboard images. They\nmove up when they would cover the Copilot or Playground message box, or the\nSave and Discard bar on Suggested Content.`}),`\n`,_jsxs(_components.li,{children:[`In the SDK, each tab keeps its own chat and guide. A tab opened with\n`,_jsx(_components.code,{children:`window.open()`}),` starts with the chat closed and no guide, and a guide\ncontinues after a reload only in the tab it runs in. When a guide step opens\na new tab, the chat opens there if it was open in the first tab.`]}),`\n`,_jsxs(_components.li,{children:[`New optional settings: `,_jsx(_components.code,{children:`OIDC_REFRESH_TOKENS`}),` on the dashboard and\n`,_jsx(_components.code,{children:`SECURITY_TXT_CONTACT`}),` on the backend. `,_jsx(_components.code,{children:`GOOGLE_CLOUD_LOCATION`}),` also accepts\n`,_jsx(_components.code,{children:`eu`}),` and `,_jsx(_components.code,{children:`us`}),`. In the Helm chart’s `,_jsx(_components.code,{children:`values.yaml`}),`, only the commented\n`,_jsx(_components.code,{children:`ANNOTATOR_LLM_MODEL`}),` example changes.`]}),`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-7`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`OIDC dashboard sessions no longer outlive their ID token. Before, about an\nhour after sign-in on Okta, every API call failed with 401 while the\ndashboard still showed the user as signed in. Now the next page load goes to\nsign-in (“Your session has expired”) and then back to the same page; with an\nactive IdP session, usually without asking for credentials.`}),`\n`,_jsx(_components.li,{children:`The dashboard’s retry after a 401 asks for a fresh token, and a sign-in the\nIdP refuses says so on the sign-in page.`}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`LLM_THINKING=minimal`}),` on `,_jsx(_components.code,{children:`gemini-3.8-flash`}),` is sent as `,_jsx(_components.code,{children:`low`}),`. Every chat\nrequest with it failed with a 400 before.`]}),`\n`,_jsx(_components.li,{children:`In the SDK, a chat start that fails after New chat has replaced it no longer\nleaves the new chat’s message box disabled with no Retry.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-6`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`API action identity.`}),` Configured API actions take the user’s company and\nuser ID from the signed SDK token, never from the conversation. The company\ncomes from `,_jsx(_components.code,{children:`company_id`}),` (or `,_jsx(_components.code,{children:`companyId`}),`) in the JWT `,_jsx(_components.code,{children:`metadata`}),` claim.\nCompany-type fields (`,_jsx(_components.code,{children:`company_id`}),`, `,_jsx(_components.code,{children:`tenant_id`}),`, `,_jsx(_components.code,{children:`organization_id`}),`, `,_jsx(_components.code,{children:`org_id`}),`\nand their `,_jsx(_components.code,{children:`X-`}),` header forms) are filled by the server, and an action with one\nis refused when the token carries no company. `,_jsx(_components.code,{children:`user_id`}),` is filled with the\nsigned-in user, and a call that names another user is refused. Applications\nwithout API actions see no change.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Role-limited procedures.`}),` A procedure with `,_jsx(_components.code,{children:`allowed_roles`}),` runs only for\nusers whose token signs one of those roles in `,_jsx(_components.code,{children:`metadata.role`}),`. Until the host\nsigns `,_jsx(_components.code,{children:`role`}),`, such a procedure is hidden from every user. A malformed\n`,_jsx(_components.code,{children:`allowed_roles`}),` value admits nobody.`]}),`\n`,_jsxs(_components.li,{children:[`A missing or blank `,_jsx(_components.code,{children:`APP_ENV`}),` now means production. Workers that don’t set it\nreport `,_jsx(_components.code,{children:`production`}),` in telemetry, so dashboards that filter on `,_jsx(_components.code,{children:`local`}),` may\nshift.`]}),`\n`,_jsx(_components.li,{children:`The images are rebuilt on current base-image packages, with no dependency\nchanges.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`known-issues-6`,children:`Known issues`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`With Moss open in two tabs during one guide, the tab that isn’t running the\nguide also emits `,_jsx(_components.code,{children:`Moss Plan Started`}),`, `,_jsx(_components.code,{children:`Moss Plan Step Completed`}),` and\n`,_jsx(_components.code,{children:`Moss Plan Finished`}),` for it, so those can be counted twice. With one tab the\ncounts are right. Fixed in 0.16.20.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`gemini-embedding-001`}),` isn’t supported on `,_jsx(_components.code,{children:`eu`}),` or `,_jsx(_components.code,{children:`us`}),`: ingestion with it\nfails, and chats answer without the application’s knowledge base. An\napplication’s embedding model can’t be changed, so moving to\n`,_jsx(_components.code,{children:`gemini-embedding-2`}),` means a new application whose sources are ingested\nagain.`]}),`\n`,_jsxs(_components.li,{children:[`The chart’s chat default, `,_jsx(_components.code,{children:`gemini-3-flash-preview`}),`, is served on `,_jsx(_components.code,{children:`global`}),`\nonly. On `,_jsx(_components.code,{children:`eu`}),` or `,_jsx(_components.code,{children:`us`}),`, set `,_jsx(_components.code,{children:`LLM_MODEL_NAME`}),` on both backends to a model\nGoogle serves there, such as `,_jsx(_components.code,{children:`gemini-3.8-flash`}),`.`]}),`\n`,_jsxs(_components.li,{children:[`Analytics chat, the daily insight sweep, monitor scoring, procedure\nauthoring, self-healing and session evaluations call the Gemini Developer\nAPI with `,_jsx(_components.code,{children:`LLM_API_KEY`}),`, whatever `,_jsx(_components.code,{children:`GOOGLE_AUTH_MODE`}),` says. On `,_jsx(_components.code,{children:`eu`}),` or `,_jsx(_components.code,{children:`us`}),`,\nleave `,_jsx(_components.code,{children:`LLM_API_KEY`}),` unset on both backends so these calls fail instead of\nleaving the region, and set `,_jsx(_components.code,{children:`INSIGHT_SWEEP_ENABLED=false`}),` on the dashboard\nbackend.`]}),`\n`,_jsxs(_components.li,{children:[`Okta has been reported to leave the groups claim out of refreshed ID tokens.\nThe dashboard then doesn’t use them, and sessions still end every hour. Try\n`,_jsx(_components.code,{children:`OIDC_REFRESH_TOKENS`}),` on a staging install first.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-18-—-2026-11-03`,children:`0.16.18 — 2026-11-03`}),`\n`,_jsx(Heading,{level:`3`,id:`security-7`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Backend and worker image security update: libexpat 2.10.0\n(CVE-2026-113351, CVE-2026-115506), replacing the patched library shipped in\n0.16.16. The worker keeps refusing sitemaps that declare a DTD.`}),`\n`,_jsxs(_components.li,{children:[`Dashboard dependency security update (`,_jsx(_components.code,{children:`prismjs`}),` 1.30.0, `,_jsx(_components.code,{children:`fflate`}),` 0.4.9).`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-7`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`The Guidance Flows empty state now says only that there are no flows.`}),`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-17-—-2026-11-02`,children:`0.16.17 — 2026-11-02`}),`\n`,_jsx(Heading,{level:`3`,id:`changed-8`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Build fix only. The images run the same software as 0.16.16, and\ndeployments already on 0.16.16 don’t need to upgrade.`}),`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-16-—-2026-11-02`,children:`0.16.16 — 2026-11-02`}),`\n`,_jsx(Heading,{level:`3`,id:`changed-9`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Support tickets: the card comes first.`}),` With host-brokered filing, once a\nticket is called for, Moss shows the editable ticket card as soon as it has a\nsubject and a description. It no longer writes the ticket out in chat, asks\nfor a confirmation there, or asks for an email address or other contact\ndetails. Nothing is filed until the user submits the card, and Moss says a\nticket was filed only once the filing is confirmed. Remove procedure text\nthat asks for a confirmation in chat.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Ticket fields are pre-filled only from what the user said,`}),` in both\nfiling modes, and values for anything outside the ticket’s fields are\ndropped. The user can still change every field the card shows. The impact\nlevel follows the user’s own words in the subject, the description and their\nmessages, so the request type no longer raises it. Critical is pre-filled\nwhen the user reports an outage, or says work has stopped or everyone is\naffected. Without such a signal, a host-brokered card leaves the impact empty\nand a direct ticket defaults to Medium.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`The Filing switch is the single on/off for tickets.`}),` Off, in the Filing\nrow of Configure > Integrations > Zendesk, applies in every procedure, in the\ndefault reply, to a ticket request under way and at Submit, and direct\nconnections no longer dry-run. Procedures also offer no tickets while a\nconnection is Paused or otherwise can’t file. Only an Admin can see or change\nthe switch.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Before upgrading, decide each Zendesk connection’s Filing setting.`}),` A\nconnection that shows Off while its procedures still offer tickets stops\noffering them at the upgrade. Switch host-brokered connections to Live only\nafter the upgrade, because on earlier releases Live also turns on a\ndefault-reply ticket offer that asks for the user’s email address. To keep\nthe default reply from offering tickets, set\n`,_jsx(_components.code,{children:`procedures.default_reply_policy`}),` to `,_jsx(_components.code,{children:`false`}),` in the application’s\nconfiguration; this also drops its suggestion to contact support. Where a\ndirect connection’s Zendesk form requires the requester’s role, pin a value\nfor that field on the Ticket intake page, or have the ticket procedures ask\nfor the role.`]}),`\n`,_jsxs(_components.li,{children:[`SDK 0.16.16 types the outcome’s `,_jsx(_components.code,{children:`ticketId`}),` as `,_jsx(_components.code,{children:`string | number`}),` and sends it\nas text.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`LLM_CLIENT_TYPE`}),` no longer accepts `,_jsx(_components.code,{children:`baseten`}),`, and the provider-failover\nsettings `,_jsx(_components.code,{children:`LLM_AUTOROUTER_ENABLED`}),` and `,_jsx(_components.code,{children:`LLM_FALLBACK_PROVIDERS`}),` are ignored.\nThe backend uses the one provider that `,_jsx(_components.code,{children:`LLM_CLIENT_TYPE`}),` names.`]}),`\n`,_jsxs(_components.li,{children:[`Traffic-log audit events from Bearer sign-ins record `,_jsx(_components.code,{children:`auth_method`}),` `,_jsx(_components.code,{children:`jwt`}),`\ninstead of `,_jsx(_components.code,{children:`clerk_jwt`}),`. Older events keep `,_jsx(_components.code,{children:`clerk_jwt`}),`, so update any SIEM\nfilter on the value.`]}),`\n`,_jsx(_components.li,{children:`The worker refuses sitemaps that declare a DTD.`}),`\n`,_jsx(_components.li,{children:`Upgrading from 0.16.7 also brings in 0.16.8 through 0.16.15, none of which\nhas a database migration or a Helm values change.`}),`\n`,_jsxs(_components.li,{children:[`No database migrations in this release. The Helm chart’s `,_jsx(_components.code,{children:`values.yaml`}),`\nchanges only in a comment.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-8`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`A repeated Submit of the same card before your backend’s answer is recorded,\nfor example after a lost response, is accepted and handed to your backend\nunder the same `,_jsx(_components.code,{children:`handoffId`}),`. Deduplicating on `,_jsx(_components.code,{children:`handoffId`}),` gives the user one\nticket. A repeat with changed values is still refused.`]}),`\n`,_jsxs(_components.li,{children:[`Your backend can return `,_jsx(_components.code,{children:`ticketId`}),` as a number or as text, and a\nwhole-number `,_jsx(_components.code,{children:`errorCode`}),` or `,_jsx(_components.code,{children:`errorDetail`}),` is kept as text. These were refused\nbefore, and the outcome went unrecorded.`]}),`\n`,_jsxs(_components.li,{children:[`The dashboard’s Broker contract page describes what your backend receives: a\ntimeout, a callback that throws or an answer without a boolean `,_jsx(_components.code,{children:`ok`}),` leaves\nthe outcome unknown, not failed; custom-field values are strings; and the\nticket body is the description followed by the last 12 chat messages, each\ncut at 400 characters.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-8`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Admin-only access.`}),` These need an Admin: changing, testing or importing\nan integration’s configuration, including Zendesk and custom API\nconnections and actions, which Members can still read; the traffic logs,\nwhich now also work with OIDC sign-in; accepting AI-instruction proposals;\nand reading deletion requests. Members see Accept disabled on instruction\nproposals and Save disabled on Suggested Content. A Member refused on the\naudit log or the traffic logs is recorded as an `,_jsx(_components.code,{children:`auth.denied`}),` audit event.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Integration credentials`}),` are kept out of application reads, the SDK\nsession response, logs and audit events, and the session response carries\nonly the settings the SDK uses. Audit lists and exports mask credential\nfields in earlier events as `,_jsx(_components.code,{children:`[REDACTED]`}),`. An Admin API client that sends back\na configuration it read keeps the stored credentials, unless a block’s\naddress, such as the Zendesk subdomain, changed.`]}),`\n`,_jsxs(_components.li,{children:[`Image security updates:`,`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Brotli (CVE-2026-111497), all four images. No path lets untrusted input\nreach the decoder.`}),`\n`,_jsx(_components.li,{children:`Chrome for Testing 156.0.8078.80, worker. Affected in principle, since the\nworker browser loads the help sites you configure; fixed by the update.`}),`\n`,_jsx(_components.li,{children:`PostgreSQL client libpq-18 in place of libpq-16, backend and worker. Not\naffected.`}),`\n`,_jsx(_components.li,{children:`Expat, patched library (CVE-2026-113351), backend and worker. Refusing\nsitemaps that declare a DTD mitigates CVE-2026-115506, since the worker\nnever parses a DTD.`}),`\n`,_jsx(_components.li,{children:`Python 3.14.10 (CVE-2026-115557), backend and worker. The image build\nrefuses an older Python.`}),`\n`,_jsx(_components.li,{children:`CA certificates (CVE-2026-111943), backend and worker, with the distrusted\nemSign roots removed from the system and Python stores.`}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`pyasn1`}),` 0.6.5, Pillow 13 and `,_jsx(_components.code,{children:`certifi`}),` 2026.10.23, backend and worker.`]}),`\n`,_jsx(_components.li,{children:`Next.js 15.5.28 (GHSA-2464-fhr4-w9xw, GHSA-p3m5-59mp-jv5r) and Node.js 24\n(CVE-2026-105482, CVE-2026-106069), dashboards.`}),`\n`,_jsx(_components.li,{children:`Playwright 1.63.0, worker.`}),`\n`,_jsx(_components.li,{children:`An unused LLM client library, which carried its own OpenSSL, is removed\nfrom the backend.`}),`\n`]}),`\n`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`known-issues-7`,children:`Known issues`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Outage detection depends on wording: some outage reports aren’t read as\nCritical, and some other reports are. The user can change the impact on the\ncard wherever the ticket intake shows it (by default, under Review details).`}),`\n`,_jsx(_components.li,{children:`With Filing Off, a card drafted before the switch shows “Couldn’t submit\nright now. Nothing was sent — please try again.” at Submit; switching back to\nLive lets it through. The procedure Playground and Copilot’s simulations\nignore the switch.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-15-—-2026-10-19`,children:`0.16.15 — 2026-10-19`}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-9`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Required fields that a conditional branch of the Zendesk form opens, but\nthat no intake role maps, appear on the ticket card as empty required rows,\nso the user can fill them and a validation error points at the row. Fields\nthe Ticket intake page fills another way (a pinned value, the assistant, or\nyour backend) keep their handling. A stored intake picks these fields up at\nits next form sync.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-9`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Worker browser update to Chrome for Testing 155.0.8059.84.`}),`\n`,_jsxs(_components.li,{children:[`Backend and worker dependency security updates: `,_jsx(_components.code,{children:`psycopg`}),` 3.3.6 and\n`,_jsx(_components.code,{children:`psycopg2-binary`}),` 2.9.13, which bundle OpenSSL 3.5.8, and `,_jsx(_components.code,{children:`cryptography`}),`\n50.0.2, which bundles OpenSSL 4.0.3.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-10`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-14-—-2026-10-15`,children:`0.16.14 — 2026-10-15`}),`\n`,_jsx(Heading,{level:`3`,id:`security-10`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Base image security refresh for all four images: OpenSSL 4.0.3\n(CVE-2026-54873, CVE-2026-72897, CVE-2026-84782, CVE-2026-84784) and zlib\n(CVE-2026-85091).`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-11`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-13-—-2026-10-15`,children:`0.16.13 — 2026-10-15`}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-10`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Changing a dropdown on the ticket card refreshes the fields its value\nrequires, nested conditional fields included, so the fields a branch opens\nappear on the card. Values from branches that are no longer selected are\ndropped at submit.`}),`\n`,_jsx(_components.li,{children:`When validation rejects a field, the card marks that field’s row with the\nreason and opens it, instead of showing only a generic note.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-12`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`The refresh after a dropdown change, the per-field reasons and opening\nrejected rows need SDK 0.16.13. Older SDKs keep working: nested fields are\noffered when the draft already carries their parent values, and a rejected\nrow is marked “This value wasn’t accepted.”`}),`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-12-—-2026-10-15`,children:`0.16.12 — 2026-10-15`}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-11`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Refreshing or reprocessing a page that now produces fewer chunks no longer\nleaves its old trailing chunks in knowledge search. The worker’s cleanup\nbefore re-chunking failed against Pinecone’s preview fetch API, logged\n`,_jsx(_components.code,{children:`Batch pinecone cleanup failed, falling back per-page`}),`, and deleted nothing.\nFirst ingests and full source refreshes were unaffected apart from the\nwarning. After upgrading, refresh an affected page, or run a full source\nrefresh, to remove its stale chunks.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-13`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-11-—-2026-10-14`,children:`0.16.11 — 2026-10-14`}),`\n`,_jsx(Heading,{level:`3`,id:`security-11`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Worker browser update to Chrome for Testing 155.0.8059.39.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-14`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-10-—-2026-10-13`,children:`0.16.10 — 2026-10-13`}),`\n`,_jsx(Heading,{level:`3`,id:`security-12`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Worker dependency security updates (`,_jsx(_components.code,{children:`anyio`}),`, `,_jsx(_components.code,{children:`PyJWT`}),`, `,_jsx(_components.code,{children:`CairoSVG`}),`, `,_jsx(_components.code,{children:`fsspec`}),`,\n`,_jsx(_components.code,{children:`urllib3`}),`).`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-15`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`First complete on-prem image set since 0.16.7. It carries the 0.16.8 and\n0.16.9 fixes.`}),`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-9-—-2026-10-13`,children:`0.16.9 — 2026-10-13`}),`\n`,_jsx(Warning,{children:_jsx(_components.p,{children:`The worker image for 0.16.9 was not published because it was held by the\nvulnerability gate. On-prem deployments should use 0.16.10 or later, which\ncarries every 0.16.9 fix.`})}),`\n`,_jsx(Heading,{level:`3`,id:`security-13`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Backend dependency security updates (`,_jsx(_components.code,{children:`anyio`}),`, `,_jsx(_components.code,{children:`PyJWT`}),`, `,_jsx(_components.code,{children:`CairoSVG`}),`,\n`,_jsx(_components.code,{children:`langgraph-sdk`}),`, `,_jsx(_components.code,{children:`urllib3`}),`).`]}),`\n`,_jsxs(_components.li,{children:[`Dashboard dependency security updates: `,_jsx(_components.code,{children:`sharp`}),` 0.35.5\n(GHSA-wq5f-xc86-pv6w) and `,_jsx(_components.code,{children:`source-map-js`}),` 1.2.2 (CVE-2026-93749).`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-16`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-8-—-2026-10-13`,children:`0.16.8 — 2026-10-13`}),`\n`,_jsx(Warning,{children:_jsx(_components.p,{children:`The images for 0.16.8 were not published because they were held by the\nvulnerability gate. On-prem deployments should use 0.16.10 or later, which\ncarries every 0.16.8 fix.`})}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-12`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Knowledge search returns documents again. Pinecone’s preview search API\nbegan rejecting a reserved field that Moss requested, so every search\nreturned no documents and the assistant answered without the knowledge base.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-17`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-7-—-2026-09-17`,children:`0.16.7 — 2026-09-17`}),`\n`,_jsx(Heading,{level:`3`,id:`added-6`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Multi-architecture on-prem images.`}),` Every on-prem image tag\n(`,_jsx(_components.code,{children:`moss-backend`}),`, `,_jsx(_components.code,{children:`moss-worker`}),`, `,_jsx(_components.code,{children:`moss-dashboard`}),`, `,_jsx(_components.code,{children:`moss-dashboard-oidc`}),`)\nresolves to an OCI image index with `,_jsx(_components.code,{children:`linux/amd64`}),` and `,_jsx(_components.code,{children:`linux/arm64`}),` images.\nCosign signatures and CycloneDX SBOM attestations cover the index digest and\neach architecture digest. Mirror the full index together with its signature\nand attestation tags; `,_jsx(_components.code,{children:`docker pull`}),` and `,_jsx(_components.code,{children:`docker push`}),` flatten it to one\narchitecture.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-18`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Each image tag resolves to an index digest instead of a single-image digest.\nVerification by tag is unaffected. Deployments that pin a digest re-pin\nonce, to the index digest or to the architecture digest they want.`}),`\n`,_jsxs(_components.li,{children:[`The SDK package loads in CommonJS projects: `,_jsx(_components.code,{children:`main`}),` and the `,_jsx(_components.code,{children:`require`}),`\ncondition point at a CommonJS build with its own type declarations.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`getAppearance`}),` and the appearance preset objects are no longer declared by\nthe SDK; select a preset with the `,_jsx(_components.code,{children:`appearance`}),` config option.`]}),`\n`,_jsxs(_components.li,{children:[`SDK tokens whose `,_jsx(_components.code,{children:`metadata`}),` claim is present but not an object are rejected\nwith 401 `,_jsx(_components.code,{children:`INVALID_TOKEN`}),`. A non-empty list, string or number caused a server\nerror before, and an empty one (`,_jsx(_components.code,{children:`[]`}),`, `,_jsx(_components.code,{children:`\"\"`}),`, `,_jsx(_components.code,{children:`0`}),`, `,_jsx(_components.code,{children:`false`}),`) was accepted.`]}),`\n`,_jsxs(_components.li,{children:[`The worker drops unused dependencies, `,_jsx(_components.code,{children:`nltk`}),` among them.`]}),`\n`,_jsx(_components.li,{children:`Base image refresh.`}),`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-13`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.code,{children:`FloatingActionBar`}),`, `,_jsx(_components.code,{children:`fetchAppConfig`}),`, `,_jsx(_components.code,{children:`convertBackendConfig`}),`,\n`,_jsx(_components.code,{children:`mergeAppearance`}),`, `,_jsx(_components.code,{children:`MOSS_TRIGGER_ATTR`}),` and `,_jsx(_components.code,{children:`installModalDialogEscape`}),` can be\nimported from the SDK package. Its type declarations listed them, but the\nbundle did not carry them.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-14`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Dashboard dependency security update: Next.js 15.5.24 and `,_jsx(_components.code,{children:`sharp`}),` 0.35.4\n(CVE-2026-75604, GHSA-2xp9-vwfh-vxw4, GHSA-rgj7-g3m4-5g8c).`]}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-6-—-2026-09-05`,children:`0.16.6 — 2026-09-05`}),`\n`,_jsx(Heading,{level:`3`,id:`added-7`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Application export and import.`}),` Admins can export a versioned bundle\nfrom Configure > General and import one from the application list through\nan Import dialog. The bundle covers the authored application alongside its\nconfiguration: procedures, API connections and actions, integration\nconnections, monitors, intent tags, and the self-healing schedule.\nCredentials are never included and are re-entered on the target.\nIntegration connections in direct-filing mode are reported for completion\nrather than created. Import runs in one transaction, and the dry-run report\nlists what would be created, remapped identifiers, every value written\ndifferently from the bundle, and a re-entry checklist. The dashboard export\nproduces the full bundle by default, and the configuration-only bundle\nremains available. Guidance flows are not part of the bundle. The endpoints\nare `,_jsx(_components.code,{children:`GET /api/v1/applications/{id}/export`}),` and\n`,_jsx(_components.code,{children:`POST /api/v1/applications/import?dry_run=true`}),`.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Dashboard-managed appearance controls (first pass).`}),` A new theme slice\nand a footer background tint can be edited from the dashboard. The SDK\napplies dashboard-saved values over the host prop per leaf, so precedence\nis preset, then host prop, then dashboard value. Hosts must upgrade the SDK\nto 0.16.6 to see dashboard theme values.`]}),`\n`,_jsx(_components.li,{children:`The SDK chat window can now be dragged from the full header and from the\nwindow edges.`}),`\n`,_jsx(_components.li,{children:`Dashboard toasts have a dismiss button, and error toasts stay until\ndismissed.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-19`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Clearing the last leaf of a configuration slice now removes the slice\ninstead of storing an empty object.`}),`\n`,_jsx(_components.li,{children:`The SDK package no longer ships sourcemaps in the tarball and now carries a\npublic README and package metadata.`}),`\n`,_jsx(_components.li,{children:`Upgrade order for split deployments: backend, then dashboard, then SDK.`}),`\n`,_jsx(_components.li,{children:`The application prune script now covers every application-owned table,\nremoves stored DOM snapshot objects, resolves tables through the configured\ndatabase schema, and refuses to run when it detects cross-application\nreferences or cannot count a table.`}),`\n`,_jsx(_components.li,{children:`No database migrations in this release.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`known-issues-8`,children:`Known issues`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`For a stored footer that contains only links, the public configuration\nendpoint reports `,_jsx(_components.code,{children:`enabled: false`}),`.`]}),`\n`,_jsx(_components.li,{children:`Importing into an organization whose install already holds an application\nwith the same name is refused. Application names are currently unique per\ninstall.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-5-—-2026-09-02`,children:`0.16.5 — 2026-09-02`}),`\n`,_jsx(Heading,{level:`3`,id:`security-15`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Worker dependency security update (`,_jsx(_components.code,{children:`nltk`}),`).`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-20`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`First complete on-prem image set that carries the 0.16.4 fixes. On-prem\ndeployments that skipped 0.16.4 should upgrade directly to 0.16.5.`}),`\n`,_jsx(_components.li,{children:`For split deployments, upgrade the backend before the dashboard.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-4-—-2026-09-02`,children:`0.16.4 — 2026-09-02`}),`\n`,_jsx(Warning,{children:_jsx(_components.p,{children:`The worker image for 0.16.4 was not published because it was held by the\nvulnerability gate. On-prem deployments should use 0.16.5, which carries\nevery 0.16.4 fix.`})}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-14`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`The dashboard pages for Procedures, Custom API Actions, Integrations,\nMonitors, and Proposals now work on deployments that sign in with OIDC.`}),`\n`,_jsx(_components.li,{children:`Per-prompt zero-state icons configured in the dashboard now render in the\nSDK exactly as configured, and turning them on takes a single save.`}),`\n`,_jsx(_components.li,{children:`The public SDK configuration endpoint now tolerates unknown zero-state keys\ninstead of failing.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`changed-21`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Base image refresh.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-3-—-2026-08-27`,children:`0.16.3 — 2026-08-27`}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-15`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`SDK tokens that carry an audience (`,_jsx(_components.code,{children:`aud`}),`) claim are no longer rejected when\nthe deployment does not require one.`]}),`\n`,_jsx(_components.li,{children:`Reasoning levels that the configured model does not support are now\ncoerced to the nearest supported level instead of failing the request.`}),`\n`,_jsx(_components.li,{children:`Saving the dashboard Appearance or Security form no longer overwrites SDK\nappearance presets, and each form saves only its own fields.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-2-—-2026-08-23`,children:`0.16.2 — 2026-08-23`}),`\n`,_jsx(Heading,{level:`3`,id:`security-16`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Base image security refresh. This is the first published on-prem image set\nof the 0.16 line.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-1-—-2026-08-23`,children:`0.16.1 — 2026-08-23`}),`\n`,_jsx(Warning,{children:_jsx(_components.p,{children:`The images for 0.16.1 were not published because they were held by the\nvulnerability gate. On-prem deployments should use 0.16.2 or later, which\ncarries every 0.16.1 fix.`})}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-16`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`The public SDK configuration endpoint is now served in every backend\nservice mode, so split deployments that expose only the SDK backend can\nbootstrap the SDK.`}),`\n`,_jsx(_components.li,{children:`The public key field on the dashboard Security page no longer overflows\nits container.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`security-17`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[`Dashboard dependency security update (`,_jsx(_components.code,{children:`nanoid`}),`).`]}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-16-0-—-2026-08-17`,children:`0.16.0 — 2026-08-17`}),`\n`,_jsx(Heading,{level:`3`,id:`added-8`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Support Ticket Handoff`}),` — the assistant can collect a support request,\nshow the user a review card, and hand the confirmed ticket to your\napplication to file through your own backend. See\n`,_jsx(_components.a,{href:`/en/sdk/support-ticket-handoff`,children:`Support Ticket Handoff`}),`. Ticket filing is\noffered only on applications where it is configured and only to sessions\nwhose host registered the `,_jsx(_components.code,{children:`onSupportTicket`}),` callback.`]}),`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Session detail`}),` — the dashboard session page groups the transcript more\nclearly and closes several display gaps.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-17`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Multiline input (Shift+Enter) now also works in the compact guide bubble.`}),`\n`,_jsx(_components.li,{children:`Dashboard deep links that cross organizations now recover to the\napplication’s owning organization instead of failing.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-15-4-—-2026-08-10`,children:`0.15.4 — 2026-08-10`}),`\n`,_jsx(Heading,{level:`3`,id:`security-18`,children:`Security`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Dependency security updates.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-15-3-—-2026-08-10`,children:`0.15.3 — 2026-08-10`}),`\n`,_jsx(Heading,{level:`3`,id:`added-9`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Knowledge base progress`}),` — documentation sources show a segmented\nprogress bar with separate scrape and process phases.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-18`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Continuing a guide no longer records a duplicate user turn in the session\ntranscript.`}),`\n`,_jsx(_components.li,{children:`On-prem OIDC sign-in hardening, including support for multiple accepted\naudiences.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-15-0–0-15-2-—-2026-08-06`,children:`0.15.0–0.15.2 — 2026-08-06`}),`\n`,_jsx(Heading,{level:`3`,id:`added-10`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Session transcripts redesigned`}),` — the dashboard renders sessions as a\nchat stream with paired stimulus/response cards, user role labels, and date\ndividers.`]}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-19`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Soft line breaks in assistant responses now render correctly in chat,\nstreaming, and guide instructions.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-14-0-—-2026-08-06`,children:`0.14.0 — 2026-08-06`}),`\n`,_jsx(Heading,{level:`3`,id:`added-11`,children:`Added`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsxs(_components.li,{children:[_jsx(_components.strong,{children:`Multiline chat input`}),` — Enter sends, Shift+Enter adds a line.`]}),`\n`,_jsx(_components.li,{children:`Assistant responses in dashboard session transcripts render as markdown.`}),`\n`,_jsx(_components.li,{children:`Citations from Document360 sources now link to the public portal URL.`}),`\n`]}),`\n`,_jsx(Heading,{level:`2`,id:`0-13-0-—-2026-08-05`,children:`0.13.0 — 2026-08-05`}),`\n`,_jsx(Heading,{level:`3`,id:`changed-22`,children:`Changed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`The SDK version now tracks the Moss platform version.`}),`\n`,_jsx(_components.li,{children:`Session resume card redesigned: centered rating prompt and a compact\nchoice between continuing and starting a new session.`}),`\n`]}),`\n`,_jsx(Heading,{level:`3`,id:`fixed-20`,children:`Fixed`}),`\n`,_jsxs(_components.ul,{children:[`\n`,_jsx(_components.li,{children:`Prevented stale responses from appearing after starting a new chat.`}),`\n`,_jsx(_components.li,{children:`Prevented resuming onto a stale pending interaction.`}),`\n`]})]})}function MDXContent(props={}){const{wrapper:MDXLayout}={..._provideComponents(),...props.components};return MDXLayout?_jsx(MDXLayout,{...props,children:_jsx(_createMdxContent,{...props})}):_createMdxContent(props)}return{default:MDXContent};function _missingMdxReference(id,component){throw new Error(`Expected `+(component?`component`:`object`)+\" `\"+id+\"` to be defined: you likely forgot to import, pass, or provide it.\")}","frontmatter":{},"scope":{"config":{},"pageMetadata":{"title":"Changelog","description":"Notable changes to the Moss SDK and dashboard","icon":"clock-rotate-left","href":"/en/changelog"}}},"mdxSourceWithNoJs":null},"mdxExtracts":{"tableOfContents":[{"title":"Changelog","slug":"changelog","depth":1,"children":[]},{"title":"0.16.26 — 2026-11-18","slug":"0-16-26-—-2026-11-18","depth":2,"children":[{"title":"Fixed","slug":"fixed","depth":3,"children":[]}]},{"title":"0.16.24–0.16.25 — 2026-11-16","slug":"0-16-24–0-16-25-—-2026-11-16","depth":2,"children":[{"title":"Added","slug":"added","depth":3,"children":[]},{"title":"Changed","slug":"changed","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-2","depth":3,"children":[]},{"title":"Security","slug":"security","depth":3,"children":[]},{"title":"Known issues","slug":"known-issues","depth":3,"children":[]}]},{"title":"0.16.23 — 2026-11-13","slug":"0-16-23-—-2026-11-13","depth":2,"children":[{"title":"Added","slug":"added-2","depth":3,"children":[]},{"title":"Changed","slug":"changed-2","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-3","depth":3,"children":[]},{"title":"Security","slug":"security-2","depth":3,"children":[]},{"title":"Known issues","slug":"known-issues-2","depth":3,"children":[]}]},{"title":"0.16.22 — 2026-11-10","slug":"0-16-22-—-2026-11-10","depth":2,"children":[{"title":"Added","slug":"added-3","depth":3,"children":[]},{"title":"Changed","slug":"changed-3","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-4","depth":3,"children":[]},{"title":"Security","slug":"security-3","depth":3,"children":[]},{"title":"Known issues","slug":"known-issues-3","depth":3,"children":[]}]},{"title":"0.16.21 — 2026-11-06","slug":"0-16-21-—-2026-11-06","depth":2,"children":[{"title":"Changed","slug":"changed-4","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-5","depth":3,"children":[]},{"title":"Security","slug":"security-4","depth":3,"children":[]},{"title":"Known issues","slug":"known-issues-4","depth":3,"children":[]}]},{"title":"0.16.20 — 2026-11-04","slug":"0-16-20-—-2026-11-04","depth":2,"children":[{"title":"Added","slug":"added-4","depth":3,"children":[]},{"title":"Changed","slug":"changed-5","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-6","depth":3,"children":[]},{"title":"Security","slug":"security-5","depth":3,"children":[]},{"title":"Known issues","slug":"known-issues-5","depth":3,"children":[]}]},{"title":"0.16.19 — 2026-11-03","slug":"0-16-19-—-2026-11-03","depth":2,"children":[{"title":"Added","slug":"added-5","depth":3,"children":[]},{"title":"Changed","slug":"changed-6","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-7","depth":3,"children":[]},{"title":"Security","slug":"security-6","depth":3,"children":[]},{"title":"Known issues","slug":"known-issues-6","depth":3,"children":[]}]},{"title":"0.16.18 — 2026-11-03","slug":"0-16-18-—-2026-11-03","depth":2,"children":[{"title":"Security","slug":"security-7","depth":3,"children":[]},{"title":"Changed","slug":"changed-7","depth":3,"children":[]}]},{"title":"0.16.17 — 2026-11-02","slug":"0-16-17-—-2026-11-02","depth":2,"children":[{"title":"Changed","slug":"changed-8","depth":3,"children":[]}]},{"title":"0.16.16 — 2026-11-02","slug":"0-16-16-—-2026-11-02","depth":2,"children":[{"title":"Changed","slug":"changed-9","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-8","depth":3,"children":[]},{"title":"Security","slug":"security-8","depth":3,"children":[]},{"title":"Known issues","slug":"known-issues-7","depth":3,"children":[]}]},{"title":"0.16.15 — 2026-10-19","slug":"0-16-15-—-2026-10-19","depth":2,"children":[{"title":"Fixed","slug":"fixed-9","depth":3,"children":[]},{"title":"Security","slug":"security-9","depth":3,"children":[]},{"title":"Changed","slug":"changed-10","depth":3,"children":[]}]},{"title":"0.16.14 — 2026-10-15","slug":"0-16-14-—-2026-10-15","depth":2,"children":[{"title":"Security","slug":"security-10","depth":3,"children":[]},{"title":"Changed","slug":"changed-11","depth":3,"children":[]}]},{"title":"0.16.13 — 2026-10-15","slug":"0-16-13-—-2026-10-15","depth":2,"children":[{"title":"Fixed","slug":"fixed-10","depth":3,"children":[]},{"title":"Changed","slug":"changed-12","depth":3,"children":[]}]},{"title":"0.16.12 — 2026-10-15","slug":"0-16-12-—-2026-10-15","depth":2,"children":[{"title":"Fixed","slug":"fixed-11","depth":3,"children":[]},{"title":"Changed","slug":"changed-13","depth":3,"children":[]}]},{"title":"0.16.11 — 2026-10-14","slug":"0-16-11-—-2026-10-14","depth":2,"children":[{"title":"Security","slug":"security-11","depth":3,"children":[]},{"title":"Changed","slug":"changed-14","depth":3,"children":[]}]},{"title":"0.16.10 — 2026-10-13","slug":"0-16-10-—-2026-10-13","depth":2,"children":[{"title":"Security","slug":"security-12","depth":3,"children":[]},{"title":"Changed","slug":"changed-15","depth":3,"children":[]}]},{"title":"0.16.9 — 2026-10-13","slug":"0-16-9-—-2026-10-13","depth":2,"children":[{"title":"Security","slug":"security-13","depth":3,"children":[]},{"title":"Changed","slug":"changed-16","depth":3,"children":[]}]},{"title":"0.16.8 — 2026-10-13","slug":"0-16-8-—-2026-10-13","depth":2,"children":[{"title":"Fixed","slug":"fixed-12","depth":3,"children":[]},{"title":"Changed","slug":"changed-17","depth":3,"children":[]}]},{"title":"0.16.7 — 2026-09-17","slug":"0-16-7-—-2026-09-17","depth":2,"children":[{"title":"Added","slug":"added-6","depth":3,"children":[]},{"title":"Changed","slug":"changed-18","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-13","depth":3,"children":[]},{"title":"Security","slug":"security-14","depth":3,"children":[]}]},{"title":"0.16.6 — 2026-09-05","slug":"0-16-6-—-2026-09-05","depth":2,"children":[{"title":"Added","slug":"added-7","depth":3,"children":[]},{"title":"Changed","slug":"changed-19","depth":3,"children":[]},{"title":"Known issues","slug":"known-issues-8","depth":3,"children":[]}]},{"title":"0.16.5 — 2026-09-02","slug":"0-16-5-—-2026-09-02","depth":2,"children":[{"title":"Security","slug":"security-15","depth":3,"children":[]},{"title":"Changed","slug":"changed-20","depth":3,"children":[]}]},{"title":"0.16.4 — 2026-09-02","slug":"0-16-4-—-2026-09-02","depth":2,"children":[{"title":"Fixed","slug":"fixed-14","depth":3,"children":[]},{"title":"Changed","slug":"changed-21","depth":3,"children":[]}]},{"title":"0.16.3 — 2026-08-27","slug":"0-16-3-—-2026-08-27","depth":2,"children":[{"title":"Fixed","slug":"fixed-15","depth":3,"children":[]}]},{"title":"0.16.2 — 2026-08-23","slug":"0-16-2-—-2026-08-23","depth":2,"children":[{"title":"Security","slug":"security-16","depth":3,"children":[]}]},{"title":"0.16.1 — 2026-08-23","slug":"0-16-1-—-2026-08-23","depth":2,"children":[{"title":"Fixed","slug":"fixed-16","depth":3,"children":[]},{"title":"Security","slug":"security-17","depth":3,"children":[]}]},{"title":"0.16.0 — 2026-08-17","slug":"0-16-0-—-2026-08-17","depth":2,"children":[{"title":"Added","slug":"added-8","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-17","depth":3,"children":[]}]},{"title":"0.15.4 — 2026-08-10","slug":"0-15-4-—-2026-08-10","depth":2,"children":[{"title":"Security","slug":"security-18","depth":3,"children":[]}]},{"title":"0.15.3 — 2026-08-10","slug":"0-15-3-—-2026-08-10","depth":2,"children":[{"title":"Added","slug":"added-9","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-18","depth":3,"children":[]}]},{"title":"0.15.0–0.15.2 — 2026-08-06","slug":"0-15-0–0-15-2-—-2026-08-06","depth":2,"children":[{"title":"Added","slug":"added-10","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-19","depth":3,"children":[]}]},{"title":"0.14.0 — 2026-08-06","slug":"0-14-0-—-2026-08-06","depth":2,"children":[{"title":"Added","slug":"added-11","depth":3,"children":[]}]},{"title":"0.13.0 — 2026-08-05","slug":"0-13-0-—-2026-08-05","depth":2,"children":[{"title":"Changed","slug":"changed-22","depth":3,"children":[]},{"title":"Fixed","slug":"fixed-20","depth":3,"children":[]}]}],"codeExamples":{}},"jsLinks":[],"subdomain":"moss-d7c5ed60","siteName":"Moss Documentation","title":"Changelog - Moss Documentation","navMaps":{"firstHrefInVersion":{},"firstHrefInLanguage":{"en":{"href":"/en/changelog","matchLevel":0},"ko":{"href":"/ko/changelog","matchLevel":1}}},"lastModified":"2026-11-18T05:49:12.373Z","originalFileLocation":"en/changelog.mdx","locale":"en"},"headHtml":"\u003cscript data-mint-head>(function(){var d=document.documentElement,p=null;if(!p){try{p=localStorage.getItem(\"isDarkMode\")}catch(e){}if(p==='true')p='dark';else if(p==='false')p='light';if(p!=='light'\u0026\u0026p!=='dark'\u0026\u0026p!=='system')p=\"system\"}var r=p==='system'?(matchMedia(\"(prefers-color-scheme: dark)\").matches?'dark':'light'):p;d.classList.remove(r==='dark'?'light':'dark');d.classList.add(r);d.setAttribute(\"data-theme-preference\",p)})();\u003c/script>\u003cmeta data-mint-head name=\"description\" content=\"Notable changes to the Moss SDK and dashboard\">\u003cmeta data-mint-head name=\"application-name\" content=\"Moss Documentation\">\u003cmeta data-mint-head name=\"generator\" content=\"Mintlify\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"192x192\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon/android-chrome-192x192.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"apple-touch-icon\" type=\"image/png\" sizes=\"180x180\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon/apple-touch-icon.png\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"16x16\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon/favicon-16x16.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"32x32\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon/favicon-32x32.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"shortcut icon\" type=\"image/x-icon\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon/favicon.ico\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"192x192\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon-dark/android-chrome-192x192.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"16x16\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon-dark/favicon-16x16.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"32x32\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon-dark/favicon-32x32.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"shortcut icon\" type=\"image/x-icon\" href=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon-dark/favicon.ico\" media=\"(prefers-color-scheme: dark)\">\u003cmeta data-mint-head property=\"og:title\" content=\"Changelog - Moss Documentation\">\u003cmeta data-mint-head property=\"og:description\" content=\"Notable changes to the Moss SDK and dashboard\">\u003cmeta data-mint-head property=\"og:site_name\" content=\"Moss Documentation\">\u003cmeta data-mint-head property=\"og:url\" content=\"https://docs.viamoss.ai/en/changelog\">\u003cmeta data-mint-head property=\"og:type\" content=\"website\">\u003cmeta data-mint-head property=\"og:image\" content=\"https://moss-d7c5ed60.mintlify.site/_mintlify/api/og/v2?division=Resources\u0026amp;title=Changelog\u0026amp;description=Notable+changes+to+the+Moss+SDK+and+dashboard\u0026amp;theme=7e88b92d81ca10ba9ed9e85b\u0026amp;signature=998b435d8138a536b1b46b02a6053d2da802ba599904c66b2eaa5c0d12ca65ed\">\u003cmeta data-mint-head property=\"og:image:width\" content=\"1200\">\u003cmeta data-mint-head property=\"og:image:height\" content=\"630\">\u003cmeta data-mint-head name=\"twitter:card\" content=\"summary_large_image\">\u003cmeta data-mint-head name=\"twitter:title\" content=\"Changelog - Moss Documentation\">\u003cmeta data-mint-head name=\"twitter:description\" content=\"Notable changes to the Moss SDK and dashboard\">\u003cmeta data-mint-head name=\"twitter:image\" content=\"https://moss-d7c5ed60.mintlify.site/_mintlify/api/og/v2?division=Resources\u0026amp;title=Changelog\u0026amp;description=Notable+changes+to+the+Moss+SDK+and+dashboard\u0026amp;theme=7e88b92d81ca10ba9ed9e85b\u0026amp;signature=998b435d8138a536b1b46b02a6053d2da802ba599904c66b2eaa5c0d12ca65ed\">\u003cmeta data-mint-head name=\"twitter:image:width\" content=\"1200\">\u003cmeta data-mint-head name=\"twitter:image:height\" content=\"630\">\u003cmeta data-mint-head name=\"msapplication-config\" content=\"/mintlify-assets/_mintlify/favicons/moss-d7c5ed60/_Msi1hiuco5631c0/_generated/favicon/browserconfig.xml\">\u003cmeta data-mint-head name=\"apple-mobile-web-app-title\" content=\"Moss Documentation\">\u003cmeta data-mint-head name=\"msapplication-TileColor\" content=\"#000000\">\u003clink data-mint-head rel=\"canonical\" href=\"https://docs.viamoss.ai/en/changelog\">\u003clink data-mint-head rel=\"alternate\" type=\"application/xml\" href=\"/sitemap.xml\">\u003clink data-mint-head rel=\"alternate\" type=\"text/markdown\" href=\"/en/changelog.md\">\u003clink data-mint-head rel=\"alternate\" hreflang=\"en\" href=\"https://docs.viamoss.ai/en/changelog\">\u003clink data-mint-head rel=\"alternate\" hreflang=\"ko\" href=\"https://docs.viamoss.ai/ko/changelog\">\u003clink data-mint-head rel=\"alternate\" hreflang=\"x-default\" href=\"https://docs.viamoss.ai/en/changelog\">\u003cscript data-mint-head type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https://docs.viamoss.ai/#organization\",\"name\":\"Moss Documentation\",\"url\":\"https://docs.viamoss.ai\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https://mintcdn.com/moss-d7c5ed60/S5aXHXmoaZpUr-nV/logo/light.svg?fit=max\u0026auto=format\u0026n=S5aXHXmoaZpUr-nV\u0026q=85\u0026s=fec775d374812338dc1ed50c0fa278ca\"}},{\"@type\":\"WebSite\",\"@id\":\"https://docs.viamoss.ai#website\",\"name\":\"Moss Documentation\",\"url\":\"https://docs.viamoss.ai\",\"publisher\":{\"@id\":\"https://docs.viamoss.ai/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https://docs.viamoss.ai/en/changelog#webpage\",\"url\":\"https://docs.viamoss.ai/en/changelog\",\"name\":\"Changelog\",\"description\":\"Notable changes to the Moss SDK and dashboard\",\"dateModified\":\"2026-11-18T05:49:12.373Z\",\"isPartOf\":{\"@id\":\"https://docs.viamoss.ai#website\"},\"breadcrumb\":{\"@id\":\"https://docs.viamoss.ai/en/changelog#breadcrumb\"}},{\"@type\":\"BreadcrumbList\",\"@id\":\"https://docs.viamoss.ai/en/changelog#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Moss Documentation\",\"item\":\"https://docs.viamoss.ai\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Changelog\",\"item\":\"https://docs.viamoss.ai/en/changelog\"}]},{\"@type\":[\"Article\",\"TechArticle\"],\"@id\":\"https://docs.viamoss.ai/en/changelog#article\",\"headline\":\"Changelog\",\"name\":\"Changelog\",\"description\":\"Notable changes to the Moss SDK and dashboard\",\"url\":\"https://docs.viamoss.ai/en/changelog\",\"mainEntityOfPage\":{\"@id\":\"https://docs.viamoss.ai/en/changelog#webpage\"},\"dateModified\":\"2026-11-18T05:49:12.373Z\",\"publisher\":{\"@id\":\"https://docs.viamoss.ai/#organization\"},\"isPartOf\":{\"@id\":\"https://docs.viamoss.ai#website\"}}]}\u003c/script>\u003cscript data-mint-head type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"WebSite\",\"name\":\"Moss Documentation\",\"publisher\":{\"@type\":\"Organization\",\"name\":\"Moss Documentation\"},\"provider\":{\"@type\":\"Organization\",\"name\":\"Mintlify\",\"url\":\"https://mintlify.com\"}}\u003c/script>","agentPointerHref":"/en/changelog.md","siteName":"Moss Documentation","nav":{"global":null,"languages":[{"language":"en","groups":[{"group":"Getting Started","pages":[{"title":"Welcome","href":"/en"},{"title":"Quick Start","icon":"rocket","href":"/en/quickstart"}]},{"group":"SDK","pages":[{"title":"SDK Overview","icon":"cube","href":"/en/sdk/overview"},{"title":"Installation","icon":"download","href":"/en/sdk/installation"},{"title":"Authentication","icon":"lock","href":"/en/sdk/authentication"},{"title":"Configuration","icon":"gear","href":"/en/sdk/configuration"},{"title":"Support Ticket Handoff","icon":"ticket","href":"/en/sdk/support-ticket-handoff"},{"group":"API Reference","icon":"code","pages":[{"title":"Session","icon":"message","href":"/en/sdk/api/session"},{"title":"Hooks","icon":"code","href":"/en/sdk/api/hooks"},{"title":"Types","icon":"brackets-curly","href":"/en/sdk/api/types"}]},{"title":"Advanced","icon":"sliders","href":"/en/sdk/advanced"}]},{"group":"Dashboard","pages":[{"title":"Session Data Export","icon":"table","href":"/en/dashboard/session-data-export"}]},{"group":"Configuration","pages":[{"title":"Configuration Overview","href":"/en/configurations/overview"},{"title":"Dashboard Settings","href":"/en/configurations/dashboard-settings"},{"title":"SDK Options","href":"/en/configurations/sdk-options"},{"title":"Configuration Examples","href":"/en/configurations/examples"}]},{"group":"Security","pages":[{"title":"Security Overview","href":"/en/security/overview"},{"title":"Authentication","href":"/en/security/authentication"},{"title":"Data Protection","href":"/en/security/data-protection"},{"title":"Audit Logging","href":"/en/security/audit-logging"},{"title":"Compliance","href":"/en/security/compliance"}]},{"group":"Guides","pages":[{"title":"Labeling Interactive Elements","description":"How to add accessible labels to icon-only buttons so Moss can identify and guide users to them","href":"/en/guides/accessible-elements"}]},{"group":"Resources","pages":[{"title":"Changelog","icon":"clock-rotate-left","href":"/en/changelog"},{"title":"Versioning \u0026 Compatibility","description":"How SDK versions relate to the Moss platform, and which release the docs describe","icon":"code-branch","href":"/en/versioning"}]}]},{"language":"ko","pages":[{"title":"ko","href":"/ko/changelog"}]}]},"basePath":"","title":"Changelog - Moss Documentation","deploymentId":"dpl_HhUetB7eHHDAmK9T1Teip38TgFx9","buildId":"dpl_HhUetB7eHHDAmK9T1Teip38TgFx9","dynamics":[],"chunks":[]}