Praecise Harness v1.1.0 Get started

Documentation · Getting started

The folder

Nothing here is required except the one folder you actually use.

agents/          one file per agent
workflows/       one file per workflow
memory/          .md and .txt every agent can answer from
functions/       your own code, callable by an agent
tools/           MCP services the app may act through
skills/          how to do a kind of work, read when it applies
evals/           what a right answer looks like, checked on demand
stores/          somewhere to keep things
guard.ts         which tool calls the app actually makes
hooks.ts         what happens after a tool runs and before an agent stops
praecise.config.ts
.env

A file's name is its name: agents/support.ts is the agent support, served at /support. Nothing to register, no imports between files, no config to keep in sync.

TypeScript works with no setup. praecise dev, run, list, mcp and package compile the app before loading it, into .praecise/build, using the typescript in your own project — so the version you chose is the version your code is built with, and praecise itself stays dependency-free. Only what changed is rebuilt.

It is a transpile, not a type check: types are erased and nothing is verified, which is why it takes milliseconds and why a type error never stops a dev server. Checking types is npm run typecheck (tsc --noEmit), in your editor and in CI, where a type error should stop something.

Nothing is built for a JavaScript app, or on a runtime that reads TypeScript natively.

Edit this page on GitHub · Read it as Markdown

    Type to search. Arrow keys move, Enter opens.