v0.2.5 — Local-first · Governed · Inspectable
The agent kernel that
stays legible after the run.
Approve before side effects. Inspect receipts after execution.
Roll back when needed. Same model loop — different operator contract.
$
curl -fsSL https://raw.githubusercontent.com/heggria/Hermit/main/install-macos.sh | bash
Generic Agent
- Chat-first sessions
- Direct model-to-tool execution
- Transcript as context
- Tool logs as "audit"
- Memory as sticky notes
Hermit
- Task-first durable work
- Policy, approval & scoped authority
- Artifacts, beliefs & working state
- Receipts, proofs & proof bundles
- Evidence-bound memory governance
Why Hermit
A kernel gives you semantics for governing execution.
A framework gives you structure for composing agents. The difference matters.
Task-First Kernel
All meaningful work flows through durable Task objects with identity, lifecycle, and outcomes. Tasks survive sessions, approvals, pauses, and failures. CLI, chat, scheduler, webhook, and adapters converge on the same task semantics.
Governed Execution
Between the model's proposal and execution, the kernel evaluates policy, records decisions, and issues scoped capability grants. Not just human-in-the-loop — structured authority with full audit trails.
Receipts & Proofs
Important actions produce structured receipts. Proof bundles make action chains independently verifiable.
Rollback Recovery
Undo supported actions with structured reversal, not manual cleanup or hoping it worked out.
Artifact-Native Context
Context compiled from artifacts, working state, beliefs, and task state — not just transcript.
Evidence-Bound Memory
Durable memory promotion cites evidence. Memory without provenance is hidden authority.
The Governed Execution Path
Models propose actions, the kernel authorizes, then the executor runs.
No direct model-to-tool execution.
Task
Step
Policy
Approval
Authority
Execution
Receipt
Proof / Rollback
See It In Action
One task, still visible afterward.
# Run a task
$ hermit run "Summarize the current repository"
# Inspect the task record
$ hermit task list
$ hermit task show <task_id>
# View receipts and proof
$ hermit task receipts --task-id <task_id>
$ hermit task proof <task_id>
# Roll back if needed
$ hermit task rollback <receipt_id>
Built For Work That Matters
When the operator later asks "what happened and why" —
Hermit has an answer.
Local Coding Agent
Asks before writing outside the workspace. Every file change produces a receipt. Rollback restores the original.
Scheduled Assistant
Produces artifacts and keeps an inspectable task ledger across scheduled runs. Works unattended.
Channel Operator
Approvals and task continuity matter when connected to Feishu, Slack, or other messaging channels.
Memory Runtime
Durable memory cites evidence. Memory promotion is governed, not a free-for-all scratchpad.
Ready to make agent work inspectable?
Hermit is open source (MIT) and shipping today.