You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Demo of "5 Tips to Get More Out of Your Claude Code with MLflow" (blog post).
Quick Start
# 1. Set required environment variablesexport DATABRICKS_HOST=https://your-workspace.cloud.databricks.com
export DELTA_TABLE=my_catalog.default.claude_code_traces
# Optional:# export DATABRICKS_PROFILE=my-profile # Databricks CLI profile# export DB_USER=you@company.com # auto-detected if not set# export MLFLOW_TRACING_SQL_WAREHOUSE_ID=abc123 # for LLM judge evaluations# 2. Run setup (creates venv, authenticates, enables tracing)
./setup.sh
# 3. Run the interactive demo
./run_demo.sh
# Or run a specific tip (1-5)
./run_demo.sh 2
Environment Variables
Variable
Required
Description
DATABRICKS_HOST
Yes
Your Databricks workspace URL (e.g. https://my-workspace.cloud.databricks.com)
DELTA_TABLE
Yes (for setup.sh)
Unity Catalog table for trace archival (e.g. catalog.schema.table)
DATABRICKS_PROFILE
No
Databricks CLI profile name (auto-derived if not set)
DB_USER
No
Databricks user email (auto-detected from CLI auth)
MLFLOW_TRACING_SQL_WAREHOUSE_ID
No
SQL warehouse ID for LLM judge evaluations
MLFLOW_EXPERIMENT_NAME
No
Experiment name (used by Python scripts if not passed as arg)
The 5 Tips
#
Tip
What it does
Script
1
Monitor Usage Patterns
Trace every Claude Code session with mlflow autolog claude
scripts/01_setup_tracing.sh
2
Measure Performance
Evaluate traces with custom scorers + LLM judges
scripts/02_evaluate_traces.py
3
MLflow as a Tool
Give Claude Code access to MLflow via MCP server + CLI