> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genesiscomputing.com/llms.txt
> Use this file to discover all available pages before exploring further.

# v1.9.2

> Genesis Data Agents v1.9.2 release notes — February 27, 2026

## v1.9.2 — February 27, 2026

### RBAC hardening, Snowflake/Databricks deployment controls, and reliability upgrades across chat, git, and metadata systems

#### RBAC and Access Governance

Access control moved to role-scoped enforcement across runtime and UI workflows, with stronger ownership and delegation protections.

* Replaced agent-level connection access with role-based RBAC controls and scoped per-repo git access
* Added scope selection and personal ownership transfer flows in `ManageAccessModal`
* Enforced RBAC checks for dashboard fork gates and cross-agent delegation target validation
* Restricted app SQLite access paths to reduce unintended local database exposure
* Added agent budget tracking with spend limits and warning thresholds for governance

#### Snowflake and Deployment Operations

Release and deployment workflows gained branch-aware controls, richer metadata, and safer environment handling.

* Added branch-aware Snowflake Dev deployment controls in release dashboard workflows
* Enabled Snowflake Dev deploy APIs to accept explicit branch selection and deployment metadata
* Added Docker image tagging for Snowflake Dev version/patch in GHCR
* Added Databricks native deployment support and Databricks OAuth setup wiring
* Raised Helm chart minimum resource requests and added Azure AKS / local Kubernetes environment directories

#### Databricks and OAuth Experience

Enterprise auth and workspace onboarding flows were expanded and tightened for operator reliability.

* Added Databricks user OAuth setup flow with grants and improved setup guidance
* Landed OAuth and project guard fixes as part of broader git browser and RBAC polish work
* Improved auth config retry UX with visible countdown behavior during fetch failures

#### Git Browser and Developer Workflow Hardening

Git and project workflows now provide safer defaults and more predictable behavior during automation and handoffs.

* Shipped git browser UX refinements and reliability fixes across repo actions
* Ensured PR command branch creation always rebases from latest `main` before branch creation
* Hardened thread/git behavior in environment rollout updates and context-control improvements
* Added `clean-macos-duplicates` skill support for repository hygiene operations

#### Data Layer and SQLAlchemy Modernization

Major metadata and ORM work closed remaining backend parity gaps and improved multi-backend consistency.

* Closed 50+ SQLAlchemy mode gaps across 23 files to improve compatibility and correctness
* Synced metadata-layer behavior for multi-backend support in SQLAlchemy paths
* Improved standalone startup ordering by running ChromaDB rehydration before harvester launch

#### Chat, Handoff, and UI Reliability

Thread continuity and user experience were hardened across handoff, metrics, and mobile layouts.

* Fixed duplicate handoff thread replay behavior and navigation click handling issues
* Preserved user-defined thread titles during handoff and history transitions
* Hardened thread export behavior against timeout scenarios
* Fixed metrics dashboard source switching, instance selector behavior, and mobile filter/tab layout

#### Tools, Skills, and Platform Extensibility

Agent tooling and operational capabilities were expanded to simplify runtime administration.

* Added `connections_action` tooling for agent-driven connection management
* Added Eve branding management tooling and fixed UI/API edits for Eve tools and instructions
* Expanded weekly summary and environment package updates for delivery quality and repeatability
* Added Snowflake deployment control flows and related release-dashboard operational improvements

***

#### Upgrade Notes

Upgrade from `v1.8.5` to `v1.9.2` includes broad RBAC and deployment-surface changes; validate role mappings, deployment branch selection defaults, and Databricks OAuth configuration in lower environments before production rollout.