Builds the agents
Fabric Harness
A TypeScript framework for durable, deployable autonomous agents.
Your first agent reaches production in weeks, and the tenth costs a fraction of the first. Durability, approvals, sandboxing, model routing, and Unity Catalog-bounded data access are already solved, so your engineers write the agent instead of the plumbing under it.
3 common questions, answered below ↓- Role in the family
- Builds the agents
- Databricks surfaces
- Unity AI GatewayUnity CatalogDatabricks AppsModel ServingTemporal
- Status
- A feature-rich alpha. The local runtime, Temporal worker path, model provider registry, approvals, tasks, artifacts, metrics, and Docker sandbox are used in controlled pilots and CI. Unattended production use is still being hardened.
- Documentation
- harness.fabric.pro
The problem
Agent demos run in a notebook and die on the first timeout. Getting one into production means solving durability, approvals, sandboxing, model routing, and cost accounting. No framework tutorial covers those.
How it works
Agents are defined once and deployed to a target: a local Node runtime, a Temporal worker, a Cloudflare Worker, or a Databricks App running under its own service principal. The Databricks path wires Unity AI Gateway for model serving and Unity Catalog-governed tools, so an agent's data access is bounded by the same catalogue permissions as a human analyst's.
What it does
One agent, several targets
The same definition builds for local, Temporal, Cloudflare, or a Databricks App without rewriting the agent.
Approvals as a first-class step
An agent that needs a human decision parks and waits, and survives a worker restart while it does.
Governed tools
Tools resolve through Unity Catalog, so an agent cannot reach data its service principal has no grant for.
Sandboxed execution
Code the agent writes runs in a bounded sandbox, not in the worker process.
Your first agent reaches production in weeks, and the tenth costs a fraction of the first. Durability, approvals, sandboxing, model routing, and Unity Catalog-bounded data access are already solved, so your engineers write the agent instead of the plumbing under it.
FAQ
Fabric Harness, answered
Is Harness production-ready?
It is a feature-rich alpha. The local runtime, Temporal worker path, model provider registry, approvals, tasks, artifacts, metrics and Docker sandbox are used in controlled pilots and CI. Unattended production use is still being hardened, and we will tell you at the start of your engagement.
Where do agents built with Harness run?
The same definition builds for a local Node runtime, a Temporal worker, a Cloudflare Worker, or a Databricks App running under its own service principal. You choose the target without rewriting the agent.
How is an agent stopped from reaching data it should not?
Tools resolve through Unity Catalog, so an agent's data access is bounded by the same grants as a human analyst's. It cannot reach what its service principal has no permission for.