Skip to content

v6.0.0

Latest

Choose a tag to compare

@kunal0137 kunal0137 released this 01 Nov 22:40
· 13 commits to dev since this release
dc3976e

SEMOSS 6.0.0 Release Notes

Release date: November 1, 2026
Previous release: SEMOSS 5.4.0, released July 26, 2026.

SEMOSS 6.0.0 expands the platform for building agents, automating workflows, and working with enterprise data and communications. This release brings a richer workbench, topic-based collaboration, scheduled routines, model routing, and broader governance and audit controls.

Upgrading an existing installation requires preparation. H2 databases must be migrated before starting 6.0.0. The release also moves to Tomcat 11/Jakarta APIs and Python 3.14, removes legacy KServe/NER integrations, and changes parts of the security database schema.

Highlights

  • Agents and the workbench: Streaming agent runs, subagents, human delegation, run analysis, custom tools, Git, terminal access, notebooks, browser automation, and Office document editing.
  • Workflow Automation: A dedicated project type with visual authoring, loops, decision routing, parameterized database actions, durable run history, file outputs, and version rollback.
  • Collaboration: Topic-linked chats, searchable email and Teams context, calendar and file integrations, memory, and built-in and custom routines.
  • Model management: Model routers, catalog-driven imports, pricing and capability metadata, reasoning settings, provider built-in tools, and expanded provider support.
  • Enterprise governance: Rule-based model limits, guardrails across engines, SQL query policies, bulk access management, enterprise usage dashboards, and searchable audit trails.
  • Runtime modernization: H2 2.4.240, Tomcat 11, Java 25 container images, Python 3.14, React 19, and updated dependencies.

Breaking changes and upgrade requirements

1. H2 1.4 databases require migration before startup

SEMOSS upgrades H2 1.4.200 to H2 2.4.240. H2 1.4 database files cannot be opened directly by the new runtime. Replacing the H2 JAR or enabling a compatibility mode does not convert an old database. Migration requires exporting with the old driver and importing with the new driver. See the H2 migration documentation.

Use the SEMOSS H2 Migration Service before starting the upgraded deployment. Follow the local upgrade runbook for filesystem installations or the Kubernetes cloud migration guide for remote storage.

Which data is affected

Database or storage location Upgrade action
H2-backed system databases and user database engines under db/ Migrate the existing H2 files.
Engine audit databases Include them in the db/ migration pass.
Project insight metadata and persisted saved-insight frames, including H2_Store_*.mv.db files under project/ Include them in the separate project/ migration pass.
H2 files in supported S3, Azure Blob, GCS, or MinIO storage layouts Migrate the remote copies before upgraded nodes can pull them.
InsightCache files The utility skips these rebuildable caches. Persisted saved-insight frames remain migration targets.
Custom application H2 files outside recognized layouts Review separately; the utility reports unrecognized targets for manual review.
PostgreSQL or other non-H2 databases No H2 file conversion is needed for those databases. Still inventory retained H2 files, audit stores, and project/frame stores.

Required upgrade sequence

  1. Plan a maintenance window and stop every SEMOSS/Tomcat instance that can access the affected files or cloud storage. Keep them stopped for the real migration; do not run old and new nodes against the same data.
  2. Back up the deployment and databases. Keep a full rollback copy of db/ and project/, configuration, and any external system databases. Store migration backups outside the SEMOSS home. For cloud deployments, retain a recoverable copy of the affected storage objects.
  3. Run and review dry runs. Local installations require separate passes against the actual db/ and project/ directories, each with its own backup directory. Review every failed or unrecognized target before the real run.
  4. Run the migration and save its reports. Run as the OS user that owns the SEMOSS files. Follow the runbook's disk-space guidance: local work storage needs about three times the H2 data size, and the source filesystem needs room for at least the largest database's temporary import.
  5. Verify the converted data and deploy 6.0.0. Review the real-run reports and rerun the prescribed verification. For exploded Monolith deployments, remove the old h2-1.4.200.jar; the deployment must contain h2-2.4.240.jar without the old driver alongside it.
  6. Start and smoke-test the deployment. Verify login, system databases, a user database engine, an existing insight, and a saved insight with an H2 frame. Check logs for 90048/unsupported file-version and 90113/unsupported connection-setting errors.

Rollback requires the old data as well as the old application. H2 1.4 cannot open converted 2.x files. Stop SEMOSS, restore the pre-upgrade files and any system databases changed by startup, and restore the previous application/configuration. Keep the rollback copy and migration backups until the upgrade has been accepted.

H2 SQL and connection compatibility

  • H2 2.x reserves additional SQL keywords, including VALUE, KEY, YEAR, and USER. SEMOSS updates its reserved-word handling; custom SQL and schemas must quote identifiers where necessary.
  • Numeric and Boolean values are no longer interchangeable in regular mode. Use Boolean literals such as TRUE and FALSE instead of comparisons to 1 and 0.
  • Custom queries against INFORMATION_SCHEMA, identity/sequence syntax, and assumptions about data types or casts may need changes. Review the H2 SQL migration guidance.
  • H2 1.x URL settings such as EARLY_FILTER, LOG, UNDO_LOG, MVCC, and MULTI_THREADED are unsupported. SEMOSS strips known obsolete settings at connection time, and the migration utility updates supported H2 profiles. Review custom .smss generators and deployment scripts so they do not reintroduce them. This cleanup does not replace database-file migration.
  • Deployments using an external H2 TCP server must coordinate its version with the upgraded clients.

2. Tomcat 11, Jakarta APIs, and Java

The application moves from Tomcat 9 to Tomcat 11. Java EE servlet and REST imports move from javax.servlet.*/javax.ws.rs.* to jakarta.servlet.*/jakarta.ws.rs.*.

  • Deploy the new Monolith WAR to a compatible Tomcat 11 installation; an existing Tomcat 9 installation is not a compatible target.
  • Rebuild custom filters, servlets, authentication extensions, and Java integrations against the current SEMOSS and Jakarta dependencies. Merge custom web.xml, filter-chain, SSO, and container settings into the updated deployment configuration.
  • Official container builds move from Java 21 to Java 25. Semoss and Monolith Maven compiler settings continue to target Java 21 bytecode; the container JDK change is distinct from the source target.

See the Tomcat migration guides for container-specific changes.

3. Python runtime and custom environments

The SEMOSS Python package now requires Python 3.14 or newer, increased from Python 3.12. Container Python builders also move to 3.14.

Rebuild custom Python environments using the 6.0.0 dependency definitions and validate application-specific packages, native wheels, model clients, and custom tools. Reusing an older Python environment does not satisfy the new package requirement.

4. Legacy KServe and NER integrations removed

The legacy KServe/ZooKeeper model-serving implementation and its UI are removed. Removed engine types include KSERVE_VISION, KSERVE_IMAGE_EMBED, KSERVE_IMAGE, KSERVE_TTS, and NER. Associated legacy deployment/status reactors, the NER reactor, the Python model wrapper's .ner() method, and the model.ner automation node are also removed.

Replace affected engine definitions, Pixel calls, Python integrations, and workflow nodes with supported model-engine integrations before upgrading. Existing custom Java extensions that depend on the removed classes must be updated and rebuilt. See Semoss #3213.

5. Security database schema and access behavior

Favorites and visibility are now user preferences. They are stored in USERENGINEPREFERENCE, USERPROJECTPREFERENCE, and USERINSIGHTPREFERENCE, keyed by user and login type, rather than permission rows. Favoriting an item no longer creates an access grant. Startup removes the legacy preference columns and permission rows that have no permission level. Update custom reports or integrations that read those columns; users may need to reapply legacy favorites and hidden-item preferences. See Semoss #3144.

Model limits use a new rule-based schema. Startup migrates legacy per-user and per-engine limit columns into MODELUSAGELIMIT and removes the old columns after the copy. Update scripts and reports that depend on the former USAGERESTRICTION, USAGEFREQUENCY, MAXTOKENS, MAXRESPONSETIME, or corresponding user-level columns. Review migrated limits and billing-source assignments through the new administration views. See Semoss #3162.

These startup schema changes also affect installations whose security database is hosted in PostgreSQL or another external database. Back up that database before the first 6.0.0 startup.

6. Frontend, SDK, and MCP integrations

  • React 19: Rebuild custom frontend packages and check compatibility of React integrations. SemossWeb builds require Node.js >=24.4.0 <25 and pnpm 10.13.x.
  • MCP metadata: Internal and remote MCP metadata no longer emit SMSS_PROJECT_ID and SMSS_PROJECT_NAME. Update custom consumers to use SMSS_ENGINE_ID and SMSS_ENGINE_NAME. See Semoss #2829.
  • SDK room and agent APIs: The release adds RoomStore, AgentStore, and shared login state. Integrations built against intermediate 6.0.0 snapshots using the earlier function-based room/agent helpers should adopt the current exports and types.
  • Media inputs: RunAgent uses media as the canonical file/media input key. The legacy image key remains an alias. Use media for new integrations and files beyond images.

New features and improvements

Agents, Playground, and MCP tools

  • Separate Chat and Agent execution modes, with saved-agent selection independent of the execution-mode switch.
  • Streaming agent progress and tool results, inline tool grouping, run refresh, activity views, parent/subagent relationships, and administrator access to agent-run records.
  • Agent effectiveness metrics and model-assisted run assessments for inspecting execution quality.
  • Subagents and human delegation, including assignee lookup and delegated-request context in the receiving room.
  • Deferred tool loading, provider built-in tools, selective disabling of default tools, and room/workbench-specific toolboxes.
  • Custom workbench tools, remote MCP configuration, richer tool-schema and parameter editors, and clearer tool titles and resolution errors.
  • File and multimodal tool results, including file references and native tool views for mail, calendar, memory, and other supported components.
  • Configurable context compaction, more reliable model/tool cancellation, and improved interruption handling.
  • Message-content search with pagination, conversation downloads, tool-aware suggested questions, and clearer reasoning, cache, and context-usage information.

Workbench, notebooks, and application development

  • A shared workbench brings together code, files, assistants, SQL, and resource panels, with terminal access available across workbenches.
  • Project Git integration, commit history, and commits when reverting application changes.
  • A Notebook project type and catalog, plus interactive Jupyter .ipynb viewing and editing, code/Markdown/raw cells, outputs, and notebook downloads.
  • Chat code blocks can be run, saved as files, or added to a notebook. Notebook agents can find and update notebooks in project assets.
  • Browser automation adds multi-tab sessions, selected-text/context capture, AI-assisted actions, saved recordings, and improved session cleanup.
  • In-browser PowerPoint viewing and editing, presentation-building/review agents, and expanded Office document viewers and editing controls.
  • Project templates, template administration, improved agent creation and shared-definition editing, and additional platform agents and skills for app building, data, documents, and tools.
  • Build/publish improvements distribute custom reactors and portals across containers, preserve application commit history, and improve asset copying and project import/export.

Workflow Automation

  • Workflow Automation is a dedicated project type with visual node and scope authoring.
  • Loop nodes, configurable JEV decision routing, nested-variable completion, clearer run inputs, and notification configuration.
  • Direct Java execution with improved scope transport and more reliable loop execution.
  • Durable run history, run implementation snapshots, file outputs, and structured storage outputs.
  • Database actions support query parameters and frame-backed outputs.
  • Version listing, version-history panels, and rollback from the automation editor.

Collaboration and routines

  • A Collaboration experience connects work across topic-linked chats, email, calendar, Teams conversations, and files.
  • Guided onboarding imports and organizes source conversations into topics and people, with topic review, briefs, and background checks. Onboarding can continue past individual threads that fail sorting or filing.
  • Topic-linked chats, shared threads, memory, global search, and source context help the assistant work with the relevant conversation history.
  • Microsoft 365 integration covers Outlook mail and folders, whole email threads, attachments, calendar events, Teams threads, and OneDrive/Teams files.
  • A Today view and topic work areas support daily work discovery. Drafted email can open in the editor, and owners can choose the Outlook folder used for drafts.
  • Built-in routines include daily briefs, weekly meeting agendas, mail-triggered expense review against guideline documents, and event planning.
  • Custom routines support schedules and time zones, instructions and preferences, attached documents, skills, and direct results.
  • Routine history and live run views show execution progress and failure details.
  • Connector settings, popup sign-in, refreshed login state, and calendar-source handling are improved.

Models and inference

  • Model routers distribute requests across existing model engines, with clearer weighted routing and JEV/TypeSafe decision-based routing.
  • Catalog-driven model imports, matching and resetting metadata on existing engines, improved model-ID suggestions, and a TypeSafe model catalog.
  • Model metadata includes capabilities, modalities, serving/model providers, pricing, reasoning settings, and provider built-in tool configuration; metadata is included in import/export flows.
  • Expanded NVIDIA NIM support and Vertex AI batch inference for Claude and Gemini staged through GCS.
  • OpenAI-compatible Responses support in the model helper and HTTP filter, decisions-endpoint support, and authenticated in-platform Python access to SEMOSS-hosted model endpoints.
  • Better enforcement of model input modalities, configurable Claude cache TTL, and reporting of cache-read, cache-write, and reasoning tokens.
  • Improved provider/tool compatibility, including Amazon Nova tool-call sequencing, Gemini file deduplication, and uncompressed TypeSafe requests by default.

Connectors, databases, and storage

  • New Bing and Brave search function engines and a ServiceNow function engine.
  • Microsoft mail and calendar function engines, Exchange through Microsoft Graph, directory lookup, and Graph change-notification subscriptions/webhooks.
  • Teams and SharePoint storage engines, plus Microsoft 365 and Google Workspace connector selection in Playground.
  • Selected cloud storage engines and central cloud storage move from rclone-based operations to native provider SDKs, with compatibility fixes for existing storage credentials and container operations.
  • PostgreSQL/pgvector engine support and improved embedding insertion.
  • Parameterized SQL execution, shared JDBC parameter binding and resource cleanup, and faster schema synchronization.
  • SQL scripts can execute as one transaction, with SQL-write auditing and configurable query-policy rules in the workbench.
  • Updated database drivers and fixes for database-type normalization and failed-project cleanup.

Permissions, teams, governance, and audit

  • Bulk access management, validated permission batches, effective-permission views, and catalog filtering by permission and creator.
  • Team managers, My Teams, owner-approved team access, member previews, and copying people between team lists.
  • People search can use existing SEMOSS users or the Microsoft directory, with provider-name normalization and improved group access queries.
  • Separate administration controls for creating project types, including agents and skills.
  • Model usage limits support rule/source definitions and reporting of cost and the source billed for each call. GetUserModelUsage includes COST_MICROS.
  • Guardrails across engine types, policy and on-topic guardrails, self-harm/aggression checks, SQL guardrails, and JEV policy import.
  • Guardrail hit limits, locked-user handling, hit auditing, configurable tool-continuation behavior, and judge-error verdict handling.
  • Enterprise usage dashboards, searchable activity logs, agent-run inspection, and named audit events for engine/project exports and other user actions.

Catalogs, sharing, and user experience

  • Shared engine/project overview components, refreshed catalog artwork, themed avatars, and image uploads.
  • Project and engine rename actions, clearer display names, consolidated settings actions, and a Share App dialog.
  • Expanded theme configuration, including dark-mode logos/icons and form-driven Playground settings.
  • Improved file-explorer actions, workbench panel behavior, mobile room settings, chat loading, and code-block controls.
  • Users can remove their default model selections from My Profile.

Reliability and security fixes

  • Agent-run locking and Redis refresh coordination reduce conflicting updates during streaming; room projections now expire and are evicted when sessions end.
  • Cancellation propagates through model streams, pending tools, and agent work more reliably; failed cancellation and tool errors are surfaced more clearly.
  • System-database writes use transactions, and failed project creation rolls back more consistently.
  • Engine-secret changes close/reload engines across nodes; engine cloning/restart and cluster-wide project Python reload are available.
  • Project portals and custom reactors are released to every container more reliably.
  • Python guardrails terminate their Python processes when closed. Rendered Python figures can be returned inline without GUI backends terminating the process.
  • Request-controlled file paths and headers are handled more safely; regex-injection, SQL/TLS, and content-type handling are hardened.
  • Stored credentials use updated hashing, with legacy credentials migrated after a successful login.
  • SDK requests preserve useful Pixel error messages, improve CSRF/session handling, and support an opt-in cookie jar for headless use.
  • Fixes cover PostgreSQL Playground search, notebook refresh/editing, file uploads and downloads, OneDrive traversal, shared-app routing, and Office/Visio save compatibility.
  • Java, Python, frontend, and container dependencies receive security and compatibility updates, including database drivers, cryptography, networking, document processing, and model clients.

Deployment and build changes

  • Container builders use Tomcat 11, Java 25, and Python 3.14, with refreshed Node and Maven tooling.
  • The all-images build dispatcher targets UBI9 and Ubuntu 22.04, 24.04, and 26.04. UBI8 and Amazon Linux 2023 were removed from that aggregate dispatcher; deployments using those variants should review their image-build path.
  • FIPS-oriented builds add FIPS 140-3 provider configuration and separate FIPS dependency packaging. Pair a FIPS container base with the corresponding FIPS-profile WAR; validate custom cryptography and SSH integrations against that build.
  • Node execution is available to agents, with updated sandbox-path, process-limit, startup dependency, and Kubernetes environment handling.
  • Python-builder jobs refresh weekly and use current uv tooling so Python patch versions are not held back by an old builder tool.
  • Merge updated deployment templates and feature configuration for collaboration, Microsoft Graph notifications, model usage controls, guardrails, and Redis room expiration where those features are enabled.

Full change history

These notes cover committed changes after v5.4.0 in Semoss, Monolith, and SemossWeb, reviewed against upstream dev on November 1, 2026. The links below pin the reviewed commits so the release scope remains reproducible:

Deployment changes were also checked against semoss-artifacts. The H2 upgrade instructions refer to the separate H2 Migration Service.

What's Changed

New Contributors

Full Changelog: v5.4.0...v6.0.0