Terminal
Terminal/Skill
Entry-point guide for the Databricks CLI covering install checks, authentication, profile selection, and bundles.
By Databricks
Works with
npx skills add databricks/databricks-agent-skills --skill databricks-coreCore skill for Databricks CLI, authentication, and data exploration.
For specific products, use dedicated skills:
For data discovery, exploration, and query generation — finding tables, answering natural-language questions about the data, or generating SQL — use databricks-data-discovery (it asks Genie One first, then falls back to manual exploration). If it isn't installed, use the AI-tool commands below and Manual Data Exploration.
CLI installed and current: the CLI must be >= v1.0.0. A CLI that is present but too old is not "good enough" — it must be upgraded, not worked around.
UPGRADE or INSTALL: STOP and follow that reference file to upgrade or install — do
not proceed or tell the user their CLI is fine.databricks-setup-local needs v1.16.0), that skill already detected the gap. A passing
v1.0.0 floor check is not enough: follow the Update / repair procedures to install the
latest stable, which satisfies any skill's floor.DATABRICKS_HOST and DATABRICKS_TOKEN environment variables if present in the shell. See the Databricks REST API docs.Authenticated: databricks auth profiles
NEVER auto-select a profile.
databricks auth profilesEach Bash command runs in a separate shell session.
# WORKS: --profile flag
databricks apps list --profile my-workspace
# WORKS: chained with &&
export DATABRICKS_CONFIG_PROFILE=my-workspace && databricks apps list
# DOES NOT WORK: separate commands
export DATABRICKS_CONFIG_PROFILE=my-workspace
databricks apps list # profile not set!
Use these instead of manually navigating catalogs/schemas/tables:
# discover table structure (columns, types, sample data, stats)
databricks experimental aitools tools discover-schema catalog.schema.table --profile <PROFILE>
# run ad-hoc SQL queries
databricks experimental aitools tools query "SELECT * FROM table LIMIT 10" --profile <PROFILE>
# find the default warehouse
databricks experimental aitools tools get-default-warehouse --profile <PROFILE>
Names are literal. Use catalog/schema/table names exactly as given — never change a
hyphen to an underscore or otherwise normalize them. In SQL, backtick-quote any name part
with special characters (e.g. `my-catalog`.schema.table); unquoted hyphens cause a
parse error.
These commands are first-class for running known SQL and profiling — Genie isn't
required for that. For natural-language data questions, locating data you can't
pin down, or generating a query from a question, prefer the databricks-data-discovery
skill (above) if it's installed. See Manual Data Exploration for the
full command surface, quoting rules, and troubleshooting.
⚠️ CRITICAL: Some commands use positional arguments, not flags
# current user
databricks current-user me --profile <PROFILE>
# list resources
databricks apps list --profile <PROFILE>
databricks jobs list --profile <PROFILE>
databricks clusters list --profile <PROFILE>
databricks warehouses list --profile <PROFILE>
databricks pipelines list --profile <PROFILE>
databricks serving-endpoints list --profile <PROFILE>
# ⚠️ Unity Catalog — POSITIONAL arguments (NOT flags!)
databricks catalogs list --profile <PROFILE>
# ✅ CORRECT: positional args
databricks schemas list <CATALOG> --profile <PROFILE>
databricks tables list <CATALOG> <SCHEMA> --profile <PROFILE>
databricks tables get <CATALOG>.<SCHEMA>.<TABLE> --profile <PROFILE>
# ❌ WRONG: these flags/commands DON'T EXIST
# databricks schemas list --catalog-name <CATALOG> ← WILL FAIL
# databricks tables list --catalog <CATALOG> ← WILL FAIL
# databricks sql-warehouses list ← doesn't exist, use `warehouses list`
# databricks execute-statement ← doesn't exist, use `experimental aitools tools query`
# databricks sql execute ← doesn't exist, use `experimental aitools tools query`
# When in doubt, check help:
# databricks schemas list --help
# get details
databricks apps get <NAME> --profile <PROFILE>
databricks jobs get --job-id <ID> --profile <PROFILE>
databricks clusters get --cluster-id <ID> --profile <PROFILE>
# bundles
databricks bundle init --profile <PROFILE>
databricks bundle validate --profile <PROFILE>
databricks bundle deploy -t <TARGET> --profile <PROFILE>
databricks bundle run <RESOURCE> -t <TARGET> --profile <PROFILE>
| Error | Solution |
|---|---|
cannot configure default credentials | Use --profile flag or authenticate first |
configuration does not support OAuth tokens | The command requires OAuth (e.g., databricks apps logs). Re-authenticate with databricks auth login --host <URL> --profile <PROFILE>. See CLI Authentication. |
PERMISSION_DENIED | Check workspace/UC permissions |
RESOURCE_DOES_NOT_EXIST | Verify resource name/id and profile |
| Task | READ BEFORE proceeding |
|---|---|
| First time setup | CLI Installation |
| Auth issues / new workspace | CLI Authentication |
| Exploring tables/schemas | Manual Data Exploration (or databricks-data-discovery if installed) |
| Deploying jobs/pipelines | Use /databricks-dabs |