Building in the open
pre-release

Your agent is a folder of files.

Plico is a file-first framework for agent development — still in its early stages, built in public. Define identity in agent.md, compose skills in Markdown, extend with TypeScript tools. No SDK. No lock-in. Just files.

agent / pr-review-agent
Explorer
📁 pr-review-agent
📄 plico.config.tsts
📄 agent.mdmd
📁 skills
📄 review.mdskill
📁 tools
📄 read-file.tool.tsts
📄 search-code.tool.tsts
📄 post-comment.tool.tsts
📁 evals
📁 artifacts
📁 memory
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
# PR Review Agent
You are a code review assistant for a
TypeScript monorepo. Help developers
ship better code by reviewing PRs.
## Identity
You work in the team's review workspace.
You have context about the project's
style guide and testing conventions.
## Instructions
1. Review the full diff on each PR
2. Check type safety and test coverage
Preview: agent identity in one file.

This is what an agent looks like in Plico. A single agent.md defines who it is, how it behaves, and what tools it can use. The design is settled — the runtime is being built.

pr-review-agent / agent.md identity + system prompt
# PR Review Agent

You are a code review assistant for a TypeScript monorepo.
Your purpose is to help developers ship better code by
reviewing pull requests for correctness and style.

## Identity

You work in a review workspace with access to the project's
source files. You have context about the team's coding
conventions, testing standards, and common patterns.

You are thorough but constructive. You never block a PR
without explaining the rationale behind each concern.

## Instructions

1. When a PR is opened, load and review the full diff.
2. Check for type safety issues, missing error handling,
    test coverage gaps, and style violations.
3. Comment on specific lines when you find issues.
4. Approve the PR only when all concerns are resolved.

## Tools

- read-file   — Read file contents from the PR
- search-code — Search across the codebase
- post-comment — Post review comments on lines
🧠

Identity

Who your agent is, the context it operates in, and its personality. Written in plain English.

📋

Instructions

Step-by-step behavioral rules. Numbered lists, priorities, constraints — whatever your agent needs.

🔧

Tools

Every TypeScript tool your agent can invoke. Declared by name — the implementation lives in tools/.

No YAML. No JSON schema. No DSL.
Just Markdown — the most readable, reviewable format on the planet.
The vision, in four pillars.

Plico's design centers on these principles. We're actively building toward v1.

📄

File-first

Your agent is a directory tree — readable, version-controllable, reviewable alongside your app code. No black boxes.

📋

Native event log

Every run produces a replayable event trace. Studio, evals, artifacts, and streams all derive from one canonical log.

🔍

Workbench included

Inspect tools, prompts, event history, artifacts, evals, and readiness checks — all from a local Studio UI.

🔌

Provider-agnostic

Adapters map provider shapes to the project contract. Swap models and providers without rewriting your agent.