This guide covers the three supported development workflows for the Multi-Agent Genie System. Choose the workflow that best fits your current task.
Best for: Writing unit tests, modifying single agent logic, fast iteration without deploying.
# Setup virtual environment
python3 -m venv .venv
source .venv/bin/activate
pip install -e .
# Setup pre-commit hooks for code quality
pip install pre-commit
pre-commit install
Copy the example environment file and fill in your values:
cp .env.example .env
# Edit .env with your credentials and resource IDs
# Test individual modules
pytest tests/unit/test_planning_agent.py -v
# Test full system locally
python src/multi_agent/main.py
Best for: Integration testing, debugging with real Databricks services (Genie, Vector Search, Lakebase) before deployment.
We recommend using Databricks Repos to keep your Databricks workspace synced with your git repository:
databricks repos update <repo-id>
The notebook tests use dev_config.yaml. Make sure your variables in this file point to your development/sandbox resources.
Open the Databricks UI, navigate to the synced repo, and run:
Notebooks/test_agent_databricks.pysrc/multi_agent/ code (changes will auto-reload if using %autoreload 2)Best for: Final deployment to Model Serving endpoints.
Our CI/CD pipeline automatically runs tests and deploys based on branch pushes.
git checkout develop
git commit -m "feat: add new agent"
git push # Auto-runs tests, validates bundle, and deploys to dev workspace
# Create a Pull Request to main branch
# Once merged:
# Auto-runs tests, validates bundle, and deploys to prod workspace
If you need to deploy manually using the Databricks Asset Bundle (DAB):
# Validate the bundle
databricks bundle validate
# Test agent in Databricks (Dev)
databricks bundle run agent_integration_test -t dev
# Deploy to Dev
databricks bundle run agent_deploy -t dev
# Deploy to Prod
databricks bundle run agent_deploy -t prod