Ecosystem
Tools that extend Fabric Harness development, evaluation, and operations.
Fabric Harness integrations use normal TypeScript packages and the same job, agent, session, sandbox, and eval APIs as the core framework. This catalog lists integrations backed by current code, a tested structural adapter, or an explicit project-local recipe.
Catalog
| Category | First-party surface | Guides |
|---|---|---|
| Channels | 17 signed first-party adapters across chat, support, commerce, billing, knowledge, and email. | Provider setup and outbound tools. |
| Sandboxes | Databricks SQL, Cloudflare, Daytona, E2B, Modal, Vercel, Kubernetes, and the generic remote adapter. | SQL, code, edge, and remote sandbox guides. |
| Databases | Postgres/Lakebase stores plus Postgres, MySQL, MongoDB, Redis, and SQLite governed tools. | libSQL, Supabase, Turso, and Valkey guides. |
| Tooling | Fabric evals and OpenTelemetry hooks. | Braintrust, Jetty, OpenTelemetry, Sentry, and Vitest evals. |
| Deployment | Node, Docker, Cloudflare, Azure, Databricks, Render, Kubernetes, and Temporal targets. | Deployment catalog |
Tooling
- Jetty grades job output with a separately deployed rubric and stores comparable trajectories.
- Fabric evals runs deterministic and model-judged quality gates locally or in CI.
Add integrations
fh add exposes two explicit modes:
fh add # browse the full recipe catalog
fh add --json # machine-readable catalog
fh add channel slack # scaffold files directly
fh add daytona --print # print a guide for a coding agent
fh add daytona | codex # apply the guide with Codex
fh add discord --install-deps | codex # install declared dependencies, then apply the guideA scaffold recipe writes files and tests and installs missing dependencies through the detected package manager. --no-install updates the manifest only. A connector guide is Markdown for adapting a provider SDK to the current project; --install-deps installs its cataloged dependencies before emitting the guide. The catalog labels each entry so these paths are not confused.
Keep external credentials in environment variables or secret managers. Do not place them in prompts, job inputs, session history, or uploaded evaluation files.