live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent
nl2sql.ai
newsDirectory alert

Vanna’s repository is archived while its product surfaces still look active

The 23,800-star text-to-SQL project now carries GitHub’s read-only flag, but its docs and package metadata do not yet explain the maintenance change.

Archived repo beside active-looking documentation and package metadata.
Side by side: what changed
By The Tools Desk· Aug 23, 2026the quick take — two AI hosts go live when you do

The main Vanna repository is archived. GitHub’s repository record marks it read-only, shows 23,821 stars and 2,485 forks, and dates the last push to February 2, 2026. That is a material maintenance signal for one of the most visible open-source text-to-SQL projects—even though the rest of Vanna’s public surface still reads like a current product.

The documentation remains online and introduces Vanna 2.0 as a user-aware AI agent framework that connects language models to databases. It describes tool execution, learned tool memory and permissions that flow through the system. The PyPI package page likewise presents Vanna 2.0 as an installable framework for natural-language-to-SQL, user-aware permissions, streaming tables and charts, and FastAPI or Flask integration.

GitHub’s release history puts the latest tagged version at v2.0.2, published on February 2. Its only listed change is a fix for unnecessary embedding-function initialization during ChromaDB collection retrieval. The repository still carries an MIT license, so archiving does not prevent users from forking or maintaining the code themselves. It does, however, prevent new issues, pull requests and repository changes unless the owner reverses the archive setting.

What users should do now

Do not interpret live documentation as evidence of active maintenance. Existing deployments should pin Vanna and its transitive dependencies, inventory open security and compatibility risks, and test a clean installation from the exact lockfile used in production. Teams evaluating Vanna should ask the maintainer whether development has moved to another repository or product before making the framework a long-lived dependency.

The project’s own migration notes make that diligence more important. Vanna 2.0 is described as a complete rewrite from the 0.x VannaBase API to an agent-based architecture, with a legacy adapter offered as a gradual bridge. A codebase that has already crossed a major compatibility boundary needs an explicit maintenance path; an archived repository with active-looking docs leaves that path unclear.

The nl2sql.ai directory now marks Vanna’s repository as archived while preserving its MIT license, current documentation link and latest verified release. That distinction matters: the software remains available, but availability and maintenance are not the same thing.

sources

Filed by The Tools Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk