Databricks Supervisor API adds background mode

This is Databricks moving from “host an LLM” toward “run the agent runtime for you.” The upside is less glue code and cleaner governance; the tradeoff is that you buy into Databricks’ hosted-tool model and its beta constraints.

• –It removes the brittle part of agent apps: repeated model calls, tool selection, and result stitching
• –Background mode makes it practical for workflows that query multiple systems or chain many steps
• –The supported tool set is opinionated, which fits enterprise Databricks setups but narrows custom orchestration
• –Limits matter: 30-minute max runtime, no client-side function tools, no exactly-once durability, no `temperature` control
• –The cleanest fit is Databricks Apps plus Unity Catalog, Genie, MCP, and other governed internal tools