Skip to main content

​
Genesis v1.19.79 Release Notes

July 3, 2026 New Context Graph sources for SAP, Confluence, and SharePoint, a redesigned Data Estate experience, stronger LiteLLM proxy governance, and broad reliability improvements across missions, Knowledge Base workflows, Snowflake OAuth, and managed deployments.

​
Context Graph and Data Estate

The Context Graph gains three major new source types, and the Data Estate browser is easier to navigate at a glance.
  • SAP S/4HANA is available as a connection type and Context Graph source. Scans walk the OData service catalog, parse entity metadata, and index SAP entities for search and source-to-target mapping.
  • Confluence spaces can be scanned for wiki generation and semantic search, supporting both Cloud and Data Center authentication.
  • SharePoint document libraries and site pages can be scanned, with incremental state tracking so subsequent scans process only new or modified items.
  • The Data Estate page is now the front door of the wiki browser. The left tree groups content into labeled Topics and Scanned sources drawers instead of raw scheme roots, making it clear what has been indexed and where to start exploring.

​
Dashboard and Navigation

  • The Launchpad is now the landing page when you open Genesis or click the logo in the header, replacing the previous default redirect to a chat thread. This is done so that new users can start their Genesis Journey easier. Of course old page is still there and can be navigated to by clicking Agents.

​
LiteLLM Proxy and LLM Providers

LiteLLM proxy deployments are more predictable across fresh installs, upgrades, and long-running threads.
  • More predictable LiteLLM proxy configuration across installs and upgrades — admin-saved settings (auth, API key, headers) now take priority over container-baked environment variables, provider credentials from the secret store or env vars survive upgrades, and first-time saves activate a provider only after model discovery succeeds, so UI config is no longer silently overridden or lost.
  • New native Anthropic transport option — the LiteLLM proxy provider can now speak the Anthropic Messages API directly instead of OpenAI-compatible chat, preserving prompt caching on gateways that expose Claude only through that route.
  • Assorted proxy reliability fixes — correct fast/slow classification for discovered models, reliable thread compression on long proxy-backed threads, and AWS Bedrock Test Connection now honoring the configured chat route (fixing false failures on IAM/IRSA deployments).

​
Missions

  • Mission search responds instantly as you type instead of firing a network request on every keystroke or eating the first character.

​
Misc

  • Knowledge Base and managed documents are more reliable — changing the embedding model now detects the index mismatch and guides recovery instead of silently breaking search, Overwrite & sync no longer deletes hand-uploaded files that aren’t part of the remote source, managed-source sync jobs stop returning false timeouts on large repos (with lower GitHub reconnect overhead), and chat file download links refresh when a bot rewrites a file in place so proxies no longer serve stale content.
  • Config imports and connections are safer to apply — partial config files now replace only the sections they contain (leaving auth, branding, and rate limits intact), config-defined connections merge with existing ones instead of wiping them, OAuth secret headers resolve through the managed secret store, cross-account Snowflake user OAuth from SPCS routes to the correct account host, and approving one External Access Integration no longer overwrites another’s binding.
  • Platform stability and identity fixes — embedded-Tailscale deployments self-heal External Access bindings after restart, thread-service workers are isolated from the bot cache for better stability during concurrent updates, OAuth-proxy users now see their real display name in avatars and hover cards, and Mission search filters instantly as you type.
  • Security and deployment upkeep — container images picked up dependency updates for known vulnerabilities in bundled browser, display server, and Tailscale components, ignored findings auto-reopen when a fix becomes available, Genesis-managed instances now track GA releases automatically while preserving config, and the in-app changelog serves the notes for your actual running build instead of freezing at an older version.

​
Upgrade Notes

  • Context Graph scanners: Configure SAP, Confluence, or SharePoint connections, add them as scan sources, and run an initial scan. Open the Data Estate page and confirm entities appear under Scanned sources with the new tree layout.
  • Launchpad: Navigate to the base URL and confirm you land on the Launchpad. Click the Genesis logo from any page and verify it returns to the Launchpad.
  • LiteLLM proxy: Re-save your proxy connection and confirm admin-chosen auth settings persist after restart. On a fresh install, verify the provider does not activate until models are discovered. If using an Anthropic-only gateway, set transport to Anthropic and confirm chat works with prompt caching. Open a long proxy-backed thread and confirm compression completes without errors.
  • Bedrock: Run Test Connection on your Bedrock provider and confirm it succeeds with your configured route mode.
  • Knowledge Base: If you recently changed embedding models, check managed indexes for recovery prompts. Run Overwrite & sync on an adopted index that includes hand-uploaded files and confirm those files remain. Download a file the bot rewrites in chat and confirm you receive the latest content.
  • Missions: Search for a mission by name on the missions list and confirm instant filtering. Open a mission work log, preview an injected document from a prior phase, and confirm the file loads.
  • Snowflake OAuth: Test a cross-account user OAuth connection from SPCS and confirm token exchange succeeds.
  • Config files: Deploy a partial config file and verify unrelated sections and manually created connections are preserved.
  • Changelog: Open the in-app changelog and confirm release notes match your running version.
  • Validate after upgrade: Run a Context Graph scan on at least one new source type, send a test message on a long proxy-backed thread, and confirm chat avatars show correct display names on proxy-authenticated deployments.
— The Genesis Team