Composable local agent runtime • receipts-first by default

Build your own Hermes-like agent.

Harness Kit gives you the practical pieces to run a sharp personal agent locally: memory, routines, skills, receipts, and direct tool calls—without dragging you into a monolithic stack.

↳ Local-first control ↳ Small composable surface ↳ Verifiable actions
1 runtime One local surface for tools, memory, workspace, and routines.
Receipts-first Actions are grounded in evidence, not hand-wavy status claims.
Composable Skills stay small, targeted, and easy to reason about or replace.
Fast to ship Go from prompt to local files to live deploy in a direct path.
Core building blocks

Everything you need, nothing bloated.

Harness Kit is designed for builders who want agent infrastructure they can inspect, shape, and ship—not a giant black box that hides the actual flow.

Explicit tool execution

Keep actions concrete. Read, write, search, deploy, and schedule through a narrow interface that stays understandable.

  • Direct browser and workspace access
  • Deploy static artifacts to Pages
  • One-tool-at-a-time control flow

Skills over monoliths

Package repeatable behavior into small markdown skills that guide planning, implementation, design, or QA.

  • Readable skill bodies
  • Easy local updates
  • Clear trigger and workflow rules

Memory with accountability

Use profile facts, durable notes, routines, and recent receipts so the agent can stay useful without inventing state.

  • Persisted user preferences
  • Routine scheduling for follow-ups
  • Receipts as the source of truth
FAQ

Built for practical operators.

If you care about local control, composability, and deployable outputs, this is the shape. Harness Kit is not trying to be everything. It is trying to be dependable.

What kind of agent is this for?

Personal and operator-facing agents that need memory, routines, file access, and clean tool execution without excessive infrastructure.

Why “receipts-first” matters?

Because a useful agent should show evidence for what it did. That keeps automation auditable and cuts down on false claims.

Do I need a giant framework?

No. The point is to keep the runtime small enough to understand, while still being capable enough to ship real tasks and pages.

Ready to launch

Start with a narrow loop. Expand only where it pays off.

Build a focused agent that can inspect context, take explicit actions, and leave receipts behind. That is a much better starting point than a sprawling stack you cannot reason about.