Praecise Harness · v1.1.0
Documentation
Praecise Harness is the framework for AI agents. A folder is an app: write what an agent knows and can do, and run it. Agents can read all of it as Markdown: llms.txt, llms-full.txt, or any page with .md in place of the last slash.
Getting started
Introduction
The framework for AI agents. A folder is an app.
Install
Node 22 or newer.
The folder
Nothing here is required except the one folder you actually use.
As an SDK, without a folder
The folder is the default and not the only way in. The same app can be a value you import:
As a library to build on
A third shape, for a package whose job is to be built on. Export a piece of an app and let the application compose it:
Building
Agents
Every field but role is optional. memory/** is already included for every agent, so knows is for narrowing, or for pulling in something from elsewhere.
Workflows
Steps run in order. Any {{name}} is replaced before the step runs, and can reference an input or an earlier step.
When a run stops badly
A workflow that waits for a human is the easy case. The hard cases are a process that died and a decision that turned out to be wrong, and they need different answers.
Tools
Anything that speaks MCP goes in tools/, one file per service:
Stores
That is a working store. It keeps a file under .praecise/ and needs nothing installed. Give it a url, or a credential naming the environment variable that holds one, when it...
Reading documents into a store
praecise ingest turns a folder of documents into rows an agent can answer from:
Skills
A skill is how to do a kind of work, written once and read only when it applies. It is a folder in the open Agent Skills format:
Evals
An eval says what a right answer looks like, so a change to a role, a tool or a model can be checked rather than hoped about:
Events
A workflow can be started, or continued, by something that happened elsewhere.
Work that outlives a connection
Three callers can start work here and come back for it later:
Plugins
A plugin is a package that extends an app from praecise.config.ts:
Running
Running it
doctor is the first thing to run when something is not working. It reports what will stop the app, then what merely degrades it, then what is only worth knowing, and exits...
Config
Optional. A project needs none.
Handing it to someone else
An app is finished when someone else can run it. praecise package writes a directory that installs and starts like anything else on npm:
Deploying to Praecise Cloud
These commands are in 0.6.0 and later.
Bring your own, or bring one key
The framework is open source and complete on its own. Point it at your own model endpoints, your own database, your own object storage, and it runs entirely on things you...
Underneath
The runtime is part of the package and has no dependencies of its own — nothing to install alongside it, nothing to configure. It takes each question to the cheapest model that...
Trust
What you are trusting
A framework does not get to assume where it will run, so here is what this one assumes and what it does not.
Acting under someone else's rules
An agent that pays, signs or moves anything usually answers to rules the app does not write: a mandate, a policy service, a signed delegation. Five seams carry that, all off...
Deciding what leaves the building
Anything published can say who may reach it and what calling it does:
Reference
What the API covers
Every name exported from @praecise/harness is listed in API.md, grouped by the task it belongs to. From 1.0 that list is what semantic versioning covers.
API reference
Every name exported from @praecise/harness, grouped by the task it belongs to.
Capabilities
What the framework does, row by row, and how far each is built.
Changelog
What changed in each release.