# TechFabric Harness

> A TypeScript framework for durable agents that deploy to Databricks Apps, Temporal or Cloudflare, and keep running through a restart.

Role: Agent development framework
Databricks surfaces: Unity AI Gateway, Unity Catalog, Databricks Apps, Model Serving, Temporal
Status: Production-grade. The local runtime, Temporal worker path, model provider registry, approvals, tasks, artifacts, metrics, and Docker sandbox support agents running under real production workloads.
Documentation: https://harness.techfabric.com
Canonical: https://www.techfabric.com/accelerators/harness

---

## 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 changes for you

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.

## Questions

### Is Harness production-ready?

Yes. The local runtime, Temporal worker path, model provider registry, approvals, tasks, artifacts, metrics and Docker sandbox support agents running under real production workloads.

### 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.

