cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Genie Hub
Explore technical articles, practical guides, best practices, and real-world use cases to help you get the most out of Databricks Genie. Learn from the Databricks team, MVPs, and community experts.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Genie can now live in your favorite IDE!

LingeshK
Databricks Employee
Databricks Employee

You can now open a terminal in your project folder and type genie ๐ŸŽ‰

You now have a coding agent that can read your local files, run commands, and query your Unity Catalog tables in one conversation. ๐Ÿš€

That is Genie Code CLI, now available in Beta.

Most data work lives in two places. Your scripts, sample files, and prototypes sit on your laptop. Your governed tables, pipelines, serving endpoints, and apps sit in your Databricks workspace.

Until now, you carried the work across that line yourself. You read a file, checked a table, wrote the code, ran it, checked the result, and deployed. Each step is easy. The hand-offs between the steps are where the time goes.

Genie Code CLI works on both sides of the line. You describe the task. The agent reads and edits your local files, runs commands, and reaches into Databricks on your behalf.

What is Genie Code CLI?

Genie Code CLI is a coding agent that runs locally in your terminal. Databricks tuned it for data and AI work.

"Locally" refers to where the agent runs and which files it operates on. The model does not run on your machine. Databricks provides and governs model access through Unity Gateway, so you do not bring your own model subscription.

Genie Code CLI is also a separate tool from the Databricks CLI. You install the Databricks CLI yourself, and Genie Code CLI uses it.

To find your data and answer questions about it, Genie Code CLI calls the Databricks CLI, including databricks genie ask. The agent reaches your workspace through the same command-line tool you already signed in with. Genie Code CLI runs under your own identity. It can access only the data and perform only the operations that your Databricks permissions allow.

LingeshK_0-1792108981567.png

Fig 1: One conversation across your laptop and your workspace.

How do you get started?

You have to adhere to the following three requirements first:

Then set it up in four steps:

  1. Install: on macOS or Linux, run curl -fsSL https://github.com/databricks/genie-code-cli/releases/latest/download/install.sh | bash. On Windows, use the PowerShell command in the docs.
  2. Check: run genie --version.
  3. Launch: go to your project with cd my-project, then run genie.
  4. Connect: select a Databricks CLI profile when prompted, or authenticate if you have none. Then confirm that you trust the contents of the directory.

The agent will read and edit files and run commands in that project. Pick the profile on purpose, especially if your machine has both a development and a production profile.

What can you ask it to do?

The docs give five example prompts. Each one crosses the line between your laptop and your workspace:

  • "Clean up these monthly sales CSVs, load them into Unity Catalog, and show me revenue by region over time."
  • "Which of my catalogs has customer churn data, and what were the top drivers last quarter?"
  • "Add a silver refunds table to my orders pipeline and backfill the last 90 days."
  • "Run this training script on Databricks and put the model behind a serving endpoint."
  • "Build a local app prototype for my customer's table and deploy it as a Databricks App."

Take the first prompt. It holds three jobs: clean the files, load them into a governed table, and answer a business question. Most of us would do those in three different tools.

A short prompt still needs exact terms. Name the catalog and schema to write to. Say if the agent may replace an existing table. Say what counts as revenue, for example, whether refunds are in or out. The agent can connect the steps. It cannot guess your business rules.

The backfill prompt needs the same care. A backfill processes historical data, so it is more than a code edit. Name the environment, and ask the agent to show you its plan before it runs anything.

Is this the same Genie Code you use in the workspace?

Genie Code CLI is a separate experience, built for local, terminal-based work.

It has its own tools, skills, and instructions, and at this time, it does not share them with Genie Code in the workspace. If you set up personal skills or instructions in the workspace, Genie Code CLI will not see them today.

It also does not yet include all the capabilities of the workspace UI. Use Genie Code CLI when you work locally with files, scripts, and prototypes. Stay with Genie Code in the workspace for the richer, fully featured experience.

LingeshK_1-1792109133360.pngFig 2: Genie Code CLI and Genie Code in the workspace, side by side.

Which budget controls the spend?

This is the point I would raise with workspace admins first. The product carries the Genie name, and the billing runs through Unity Gateway. Genie Code CLI usage is billed the same as using the model directly through Unity Gateway, and it appears in your Unity Gateway usage.

It is not billed under Genie pricing, and Genie budgets do not apply to it. To control spending, set budgets for Unity Gateway. Databricks also manages the model choice. During Beta, Genie Code CLI uses GPT 5.6, and you cannot choose a specific model.

My 2 cents....

  • Beta means change. The docs say the capabilities, commands, and interfaces change frequently. Check the docs before you build automation on top of a command.

  • Start small. Open Genie Code CLI in a non-production project with a clean git working tree. Ask it to explain the project first. Then ask for one small change, and read the diff before you keep it.

  • Keep two boundaries apart. In the workspace, your Databricks permissions limit what the agent can do. On your laptop, the agent runs in your terminal session, so treat any command it runs as one you ran yourself.

Set up well, I would expect to see:

  • One Databricks CLI profile per environment, named clearly, so you do not point a prototype at production by mistake.
  • A Unity Gateway budget in place before a wider team rollout.
  • Prompts that name the catalog, the schema, and the environment.
  • Changes are reviewed as a diff before they land.

Thanks for reading this far. I would love to hear how you plan to use it, so here are three questions to start:

  1. Which of your workflows crosses the line between your laptop and your workspace most often?
  2. How would you split the work between Genie Code CLI and Genie Code in the workspace for your team?
  3. For the admins here, what would you want to see in Unity Gateway usage before you roll Genie Code CLI out to more people?

For more good discussion about Genie, I am always up for it. ๐Ÿงž๐Ÿ‘‡๐Ÿป

Feel free to connect with me directly or drop a DM: linkedin.com/in/lingeshwarankanniappan

Sources

LK
0 REPLIES 0