koinon 26.11.8

Help users understand their assistant

The assistant can explain its configured name, purpose, available tools and basic navigation. These answers use the current product configuration and the tools authorized for that conversation. Audit identifies this as product configuration rather than presenting it as a document citation.

English and Spanish responses follow the language requested in the conversation, with the user's preferences providing the fallback. Source quotations remain unchanged so they can be checked against the recorded evidence. Other response languages are not included in this server-rendered language support.

Publish verified responses and inspect their evidence

Tool activity remains visible while the assistant works. Once the complete answer passes its evidence checks, SSE publishes its text in ordered chunks. Reconnecting resumes the recorded stream without repeating text already received. This is progressive delivery of verified text; it does not expose unverified model tokens.

Audit becomes available when the response finishes. It retains the tool results, exact source versions and answer policy used for that response. Completed earlier answers remain inspectable while another response is running. Exports and shared answers preserve the same product configuration or knowledge evidence used by the original response.

An invalid evidence selection receives one bounded repair attempt. A model that declines to answer, a search with no matching evidence, and an invalid final selection now have distinct recorded outcomes. A failed selection is no longer described as an empty search.

Configure knowledge and AI by task

Knowledge & AI opens with an overview of the organization's setup. Model connections hold provider access, model assignments select the available chat and embedding models, and knowledge answers control retrieval behavior. The assistant settings contain the organization's default assistant and conversation memory policy.

Unsaved changes remain protected when moving between these settings. Follow the guided setup to configure each part and check its availability.

Read documents from Library

The document reader shows the extracted text associated with a recorded document version. Page and extraction references remain visible, and long documents load in bounded pages. Downloading the original uses the selected version; opening a document does not silently replace it with a newer source.

Supported images can be previewed, and a prepared PDF opens in the browser's native viewer. Extracted text is presented as text rather than executable content. Closing the reader or changing the signed-in authorization context clears its retained preview.

Library also provides a context menu for folder and item actions. Each action checks the current selection and permissions before proceeding. Read the Library guide for navigation and document workflows.

The context menu includes Read document. File rows show their observed processing availability without a second stale processing badge. Draft, disabled, archived and custom catalog states remain visible alongside that availability.

Keep chat navigation responsive with a bounded connection pool

Conversation, project and assistant navigation share a primary authorization transaction instead of holding one connection while waiting for another nested authority read. Permissions are still checked against the primary database. This fixes the reproduced navigation timeout without increasing the connection pool or weakening revocation checks.

Audit and conversation snapshot orchestration also release their enclosing connection before the final independent authorization checks. PostgreSQL tests cover a bounded pool, concurrent reads and permission or token revocation during output authorization. The change does not remove those final checks or route them to a replica.

Snapshot repository queries explicitly declare their read-only primary transactions. This also preserves export and sharing workflows on SQLite when another transaction holds its write lock.

Measure the complete initial interface bundle

The bundle check follows static JavaScript imports as well as the HTML entry files. Shared workbench services and optional panels now have separate package entry points, while existing public imports remain compatible. Some optional loaders may request panels after the first render; the initial bundle measurement does not imply that all deferred code waits for a click.

Update the installation

Use 26.11.8 consistently across runtime packages, SDKs and interface assets. The runtime remains on pyfly 26.10.32. Preserve the installation identity, uploaded originals, recorded answers and communication history when applying the update.

Wait until both API and worker revisions are ready before verifying the running installation. Follow installation and migration checks, then test upload processing, document reading and a source-backed conversation with your configured models.

Packages include Python, TypeScript, Angular and Java 21+ SDKs, desktop MCP integration, documentation, SBOM and release provenance. Verify downloads with SHA256SUMS.