AI project harness: concepts, comparisons and workflows

How an AI project harness keeps agent work organized, checked and recorded, and how Liquid Brain approaches each part.

CONCEPTS

agent run history and reports Agent run history and reports: what to record about AI agent runs, how to read usage coverage honestly and where unknown differs from zero.
AI agent project memory AI agent project memory explained: why durable project records beat chat history, and how Liquid Brain keeps context with the work.
evidence gates for AI work Evidence gates for AI work: separate proposed from approved execution, run checks, and record outcomes so acceptance rests on evidence.
human review of agent output Human review of agent output: what to inspect before accepting AI changes, and how recorded outcomes make the review honest.
kanban for AI agents Kanban for AI agents: the board states that matter when software does the work, including review, blocked and decision owed.

CLAUDE.md alternatives CLAUDE.md alternatives compared: what a project instruction file does well, where it stops, and what a project harness like Liquid Brain adds.
project cards vs chat threads Project cards vs chat threads: when a conversation with an AI agent is enough, and when a structured card record is the better home for the work.

Claude Code project management Claude Code project management as a workflow: run Claude from project cards, schedule tasks and review results before you accept them.
Codex CLI project management Codex CLI project management as a workflow: launch Codex from project cards, schedule explicit tasks and inspect outcomes before accepting.
local AI agent workflow A local AI agent workflow keeps project records and agent runs on your own computer. Here is what that gives you and what it costs.
multi-agent project coordination Multi-agent project coordination: keep Claude and Codex work on one project organized with shared cards, scope, authority and review.
scheduled agent tasks Scheduled agent tasks done carefully: explicit prompts, readiness and authority checks, and why a started run is not a finished one.

COMING SOON

Verified against the October 17, 2026 development candidate (reviewed October 18, 2026)