15 docs tagged with "context-engineering-studio"

Assemble, test, and ship the business context every AI agent needs to produce accurate, trustworthy answers.

Describe your use case in Context Engineering Studio, approve the assets CES proposes, and review the semantic model it assembles. The repository references your Atlan assets instead of copying them.

Deploy a context repository in Context Engineering Studio to Databricks Genie. CES pushes descriptions into Unity Catalog, creates one Metric View per table, and configures a Genie Space. On Databricks, deploying is part of the build cycle because building and simulating both run on the live Genie Space.

Deploy a context repository from Context Engineering Studio to Snowflake Cortex Analyst as a Semantic View, then grant access to your business users and verify the view in Snowflake.

Enable Context Engineering Studio on your Atlan tenant in Atlan Labs, assign access to your team by enabling the CES flag on a persona, and optionally enable Data Exploration for richer semantic models seeded from sample values.

Grant the Unity Catalog and workspace permissions Context Engineering Studio needs to deploy a context repository to Databricks Genie. Required at deploy time. On Databricks, Simulate also runs on a live Genie Space, so simulating requires a first deploy.

Grant the Snowflake permissions Context Engineering Studio needs to deploy a context repository to Snowflake Cortex Analyst. Required only at deploy time. You can connect, build, and simulate without them.

Why Context Engineering Studio holds some metrics back from a deployed engine, where those metrics are still available, and what happens when CES repairs a metric automatically to meet an engine requirement.

The engines and agents a Context Engineering Studio repository serves: which deploy directly, which render a format for you to take away, and which read it over MCP.

Simulations in Context Engineering Studio run autogenerated question sets on your context repository to surface where it answers well, where it misses, and the specific descriptions, joins, filters, or assets to add next.

Find troubleshooting guides for Context Engineering Studio organized by query engine. Covers Snowflake Cortex Analyst setup, Databricks Genie deployment, OAuth, Unity Catalog, Cortex preflight checks, and chat errors.

Resolve common Databricks errors in Context Engineering Studio, including OAuth token failures, Genie Space creation issues, Unity Catalog access errors, Metric View YAML validation, SQL warehouse problems, and chat errors.

Resolve common Snowflake errors in Context Engineering Studio, including preflight check failures, generation errors, YAML validation issues, evaluation timeouts, Cortex Analyst deployment failures, JWT authentication, and chat errors.

Context Engineering Studio (CES) is Atlan's workspace for assembling, testing, and deploying the business context AI agents need to answer questions accurately. CES assembles a context repository for one use case from the governed context in your Atlan catalog and glossary, then makes it available to Snowflake Cortex Analyst, Databricks Genie, dbt, and Claude.

A Context Engineering Studio repository holds linked assets that reference your governed Atlan context, and a semantic model that says how those assets answer questions. This page covers both, and how to scope a repository to one use case.