Welcome to Plico
A folder of Markdown and TypeScript becomes a runnable, inspectable agent app.
Plico is a TypeScript-first agent app kit. A folder of Markdown instructions, skills, TypeScript tools, config, evals, memory, and artifacts becomes a runnable, inspectable agent app.
Plico needs Node 22.18 or later. CI tests 22.18 and 24. Plico keeps runs in Node's built-in
node:sqlite, which Node still marks experimental. The plico command hides that warning; a
host that embeds Plico with createPlico sees it once at startup. Plico reads
plico.config.ts and tool files with esbuild and tsx, so you need no build step and Plico does not install the TypeScript
compiler. Add typescript to your own project if you want to type-check tools with tsc.
Why Plico?
Most agent frameworks lock you into an SDK, a provider, or a runtime. Plico starts from a different premise: your agent should be a folder of files — readable, version-controllable, reviewable alongside your app code.
Core principles
- File-first. The project model is a directory tree. No black boxes, no hidden state. Everything is a file you can read, edit, and commit.
- Event-native. Every run produces a replayable canonical trace. Studio, evals, artifacts, and streams all derive from that one log.
- Provider-agnostic. Adapters map provider shapes to the project contract. Swap models and providers without rewriting your agent.
Where to go next
Quickstart
Project layout
Tools
defineTool.