Skip to main content

​
Genesis v1.19.75 Release Notes

June 27, 2026 Restricted Caller’s Rights as a dedicated Snowflake connection type, stronger LiteLLM proxy and connection governance, Genesis Apps that recover after restarts, and broad reliability improvements across the Context Graph, Knowledge Base, git workflows, and platform startup.

​
Snowflake Restricted Caller’s Rights

Snowflake administrators on SPCS deployments can now configure Restricted Caller’s Rights through a dedicated connection auth option instead of toggling a routing flag on a standard connection.
  • Restricted Caller’s Rights appears as a first-class Snowflake auth method alongside PAT, OAuth, and key-pair options, available in SPCS mode only.
  • A guided setup wizard provides copyable SQL for the caller grant, compute-pool network rules, and network-policy steps — with no credentials, account name, or OAuth flow required for the connection itself.
  • Test Connection returns clear guidance when validating RCR outside an SPCS deployment.

​
LiteLLM Proxy and LLM Providers

LiteLLM proxy deployments gained smarter model discovery, more reliable Context Graph scanning, and fixes for long-thread stability.
  • Proxy model aliases now resolve to their underlying provider models for capability detection, pricing, and UI display; discovered models are materialized into the Model Universe when the proxy connection is saved.
  • Updating a proxy connection no longer clears stored API keys or static headers when those fields are left blank on save.
  • Context Graph scans and embedding calls route through LiteLLM proxy with OAuth credentials, so delegated-auth proxy deployments work end to end.
  • Embedding dimension metadata is registered for proxy-backed embedding models, improving compatibility with vector search and Context Graph indexing.
  • The OAuth proxy wrapper upstream timeout increased to five minutes, reducing timeouts on long LLM calls.
  • Claude Opus 4.7 and 4.8 threads use the correct 300K context ceiling again, with aggressive compression anchored to the real provider limit so large threads no longer crash in a compression loop.
  • Bedrock embedding requests no longer fail due to an unsupported streaming parameter.
  • Providers marked as configured must now have their required credentials present; incomplete Databricks configurations no longer auto-select as the active LLM on a clean boot.

​
Data Connections

Connection defaults and scoped credentials now behave consistently across database tools, integrations, and infrastructure connectors.
  • Operator-set connection defaults take effect in sandbox, cloud, Microsoft 365, Google Workspace, and other infrastructure tools that previously ignored configured defaults.
  • GitHub, Databricks, Confluence, dbt Cloud, and image-analysis connectors resolve user- and bot-scoped defaults instead of silently falling back to ambient or legacy credentials.
  • SharePoint LIST honors folder selectors: agents can descend into subfolders by item ID or path instead of always returning the drive root.
  • Secret configuration fields set only via environment variables are captured into the managed secret store at startup, so both the config layer and legacy environment readers see the same value.

​
Context Graph and Wiki

The Data Estate experience is more resilient when LLM services are temporarily unavailable.
  • When estate Overview regeneration fails (LLM outage, auth error, or ungrounded output), the last good Overview is preserved instead of being erased from the page.
  • Wiki read events are tagged again so per-learning read attribution works as expected.

​
Knowledge Base and Managed Documents

Git-backed Knowledge Base workflows are clearer for both operators and agents.
  • When an agent attempts a raw git or file write against a managed document repository, the platform steers it to the correct Knowledge Base write-back tools instead of returning a dead-end error.
  • The managed-sources panel shows the true document count across all indexes (for example, “10 documents in 5 indexes”) instead of under-reporting to the primary index only.

​
Genesis Apps

App runtime reliability improved for deployments that restart frequently.
  • Genesis Apps auto-restart after a server or container restart when a stale process record would previously leave the app unreachable until a manual restart.
  • Apps that bind to scheduled datasets no longer hit a startup error on slow-boot environments.

​
Git Workflows

Repository operations are more predictable for agent-driven development workflows.
  • Creating a pull request or merge request honors a caller-supplied base branch instead of always defaulting to the repository’s main branch.
  • Git repositories with loose-object or hash-path corruption auto-heal from the remote when safe to do so, not only when pack files are corrupted.
  • GitHub App-backed repositories mint installation tokens for push and fetch operations.

​
Platform Reliability and Security

Startup, database, and container hardening improvements reduce downtime and address known vulnerabilities.
  • If the local metadata database is corrupted at startup, Genesis attempts recovery from the most recent valid backup before loading the server.
  • Database initialization runs once at startup instead of lazily on first use, eliminating unpredictable worker subprocess forks during normal operation.
  • Concurrent SQLite writes are serialized to prevent lost updates and misuse errors under load.
  • Custom OIDC providers (such as Microsoft Entra) can override the Auth0 domain setting when Auth0 is not the identity provider.
  • Container images received security updates for bundled npm, Tailscale, and Snowflake connector dependencies.

​
User Interface

  • Combo-box fields no longer clear their displayed value when the dropdown chevron is clicked twice in quick succession.

​
Upgrade Notes

  • Restricted Caller’s Rights: On SPCS, create or edit a Snowflake connection, select Restricted Caller’s Rights as the auth method, and follow the setup wizard SQL in Snowsight. Run Test Connection to confirm same-account routing, then verify an agent query reflects the calling user’s Snowflake privileges.
  • LiteLLM proxy: Re-save your proxy connection and confirm discovered models appear in the Model Universe with correct underlying-model badges. Trigger a Context Graph scan and verify it completes without authentication errors. Open a long Opus thread and confirm it compresses gracefully instead of crashing.
  • Connection defaults: Review scoped defaults under Config → Connections for sandbox, Microsoft 365, Google Workspace, and GitHub integrations. Run a short agent workflow that uses each default and confirm the expected credential is selected.
  • SharePoint: Ask an agent to list files inside a subfolder by folder ID or path and confirm results match the selected folder, not the drive root.
  • Genesis Apps: Restart the server, open a previously running app, and confirm it auto-activates without a manual restart click.
  • Git pull requests: When agents open pull requests against integration branches, verify the base branch in the resulting PR matches the branch you specified.
  • Secrets via environment variables: After upgrade, confirm provider API keys set only through environment variables are visible in the config UI and resolve correctly in agent chat. Rotate secrets through the UI if the underlying env var has changed since the initial capture.
  • Validate after upgrade: Open the Context Graph Data Estate page and confirm the Overview section persists through a scan even if LLM generation is temporarily unavailable; check managed Knowledge Base sources for accurate document counts; send a test message on a long-running thread using Opus 4.7 or 4.8.
— The Genesis Team