FabricFabricHarness
CLI

fh dev

Start a local HTTP/SSE dev server for the workspace.

fabric-harness dev [--target node|cloudflare] [options]

fh dev boots an HTTP server with the same routes as the deployed Node/Cloudflare target, plus a streaming SSE endpoint. It watches .fabricharness/agents/ and reloads on changes.

Routes

  • GET /health
  • GET /manifest
  • POST /agents/:agent/:id — invoke an agent. The body is the JSON payload.

Options

FlagDescription
--target <node|cloudflare>Default node. The Cloudflare target uses the local Worker dev shim.
--env <file>Load .env-style variables. Repeatable; shell env wins.
--host <host>Listen address (default 127.0.0.1).
--port <port>Listen port (default 3030).
--auth-token-env <var>Require Authorization: Bearer $$VAR for invocations.
--max-body-bytes <n>Reject request bodies larger than n.
--rate-limit-window-ms <n>Rate-limit window in ms.
--rate-limit-max <n>Rate-limit max requests per window.

Example

fh dev --port 4000 --auth-token-env FABRIC_DEV_TOKEN
curl -X POST \
  -H "Authorization: Bearer $FABRIC_DEV_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"question":"What is Temporal?"}' \
  http://localhost:4000/agents/ask/run-001

When to use which

  • fh run — one-shot invocations, scripts, CI smoke tests.
  • fh dev — interactive development, webhook testing, browser-driven UIs.