Skip to main content
Harnest gives managed and advanced agents the same development server, neutral API, events, and playground.
Serving from source uses the shared development environment and harnest-development.lock. harnest compile uses the lean production profile; serve the resulting launcher in deployment so development tools are not packaged. Playground assets, including the Markdown parser, live in the native CLI—not in compiled agents or the Python runtime wheel. Local harnest serve provides those assets temporarily; the deployed launcher does not expose the playground, its trace viewer, or its evaluation routes. Agent replies in the local playground support Markdown headings, lists, tables, links, and code blocks across responses, streams, and restored sessions. Raw HTML and automatic image loading are disabled; tool payloads remain plain text.

Server configuration

Configure the bind, timeout, concurrency, limits, and playground.

Development reload

Recompile changes and replace the local agent process safely.

Neutral API

Use sessions, JSON responses, SSE streams, and live WebSockets.

Custom HTTP endpoints

Expose business-specific FastAPI routes through the managed agent runtime.

Approvals and client tools

Handle required actions and resume suspended work.

Production deployment

Add authentication, durable storage, TLS, supervision, and network policy.

Response modes

Start with the copyable curl requests. For machine-readable discovery, fetch /agent and /openapi.json; /docs provides the interactive API explorer. Input and output Pydantic schemas apply to every mode and OpenAPI.