Skip to main content

Knot Harness

A file-first agent loop orchestration framework you use with your favorite agent and IDE.

|

Documentation
Knot rigging illustration

The Problem Knot Solves

Agent output is scattered across chat logs, temp directories, and ephemeral tool calls. Knot gives your workflow a home — a single directory in your repository that looks and behaves like a real project structure.

your-project/
.git/Each agent invocation is committed — full audit trail via normal git history
src/Your project source files, kept clean from workflow state
rig/Workflow configuration, self-contained and portable to any project
code-review-loom/A loom grouping related knots for a domain of work
review.mdA knot definition — agent + prompt + input directory
tie-offs/Runtime state produced by knot processing
code-review-loom/One folder per loom, one per invocation
events/Events produced by the agent during its work, triggering any listening knots
tie-off.mdThe agent's output — what it did, what it found, what changed

How Knot Works

Knot takes a file-first approach — it watches your repository and works with you seamlessly as you use your agent and IDE.

Knot Background Process

Knot Background Process

Knot runs in the background listening as you work.

Filesystem Interface

Filesystem Interface

Knot interfaces via your filesystem in plain text files — everything is a file.

Your IDE

Your IDE

Your IDE is the main control pane. IDEs are perfect for filesystem management, but feel free to use your terminal.

You — The Agent

You — The Agent

You use your agent with Knot's skills to create and manage your reusable workflows.

Getting Started

Why Knot

Knot runs in the background and works with your existing agents as the orchestration layer.

Version-Controlled Workflows

Everything is plain text, reviewed through normal git diffs. An agent's turn is automatically committed.

Goal-Seeking Agents

Knots read state, compare against a goal, and apply only what's needed — idempotent by design.

Composable Pipelines

Looms group related tasks, knots wire agents to file-based triggers. Share and re-use across projects.

Token Efficiency

Sure...... it might help? We'll get back to you on that.

Local Development

Smaller contexts via workflow decomposition. Let it run unattended for hours, grounded by your specifications.

Long Horizon

Decompose and tune your workflow iteratively in Knot. As it comes together, it takes off.

Natural Evals

Your rig is standalone — copy it, modify the profiles, rerun, assess and compare.

HITL Native

Human In The Loop grounds your agents. Create knots with HITL strands and they'll keep coming back to your truth.

Knot rigging illustration

Core Concepts

3 basic concepts and your existing agent

Knots

A single processing task: agent + prompt + input directory. Knots read state, compare against a goal, and apply only what's needed — idempotent by design.

Looms

A namespace for a domain of responsibility. Looms group related knots and can be shared and re-used across multiple projects.

Rig

Your project's Knot configuration, living at ./rig/. Everything is plain text — reviewed through normal git diffs.

Your Agents

Bring your own agent — Knot provides the structure. Integrates with Pi out of the box. Write .md files to disk, Knot watches for changes and orchestrates sessions automatically.