Lab flagship

$ vepol brief --today --write-memory

Vepol

A self-improving local AI partner that grows with you while every step stays inspectable.

OpenClaw made always-on agents feel real in everyday channels. Hermes makes agent runtimes feel expandable and compounding. Vepol goes after the next problem: an AI partner that plans your day, runs routine work, studies your patterns, self-reflects on its strategy, and takes on more of your work over time while you stay in control. The local markdown knowledge field is the mechanism that makes that growth auditable across Claude Code, Codex, Antigravity/Gemini and future CLI agents.

Read Vepol on GitHubJoin the waitlist
Local
Runs on your machine
Self-improving
Strategy and autonomy evolve in files
Source-available
Read, fork, run
Vepol cover — a self-improving local AI partner with auditable memory

// agent field

The product is autonomy that compounds

Vepol is more than a shared agent workspace. It is a controlled self-improvement loop: observe the work, update the knowledge base, revise strategy, and raise autonomy only where the human has evidence.

Studies the way you work

After sessions, Vepol extracts decisions, lessons, action items and patterns, then uses them in tomorrow’s plan.

Self-reflects in the open

Weekly strategy reviews rewrite assumptions in files you can inspect, edit or roll back.

Autonomy grows under control

Vepol watches what you accept versus edit and increases autonomy by task type, not by blind trust.

// inspectable proof

Self-improvement with a visible trail

The repository is explicit: Vepol plans, runs routine work, studies the user, self-reflects, and compounds autonomy over time. The reason it stays trustworthy is that every improvement passes through readable files.

Vepol cover — a self-improving local AI partner with auditable memory
Product frameVepol positions the knowledge base as the control surface for a partner that grows in agency over time.
Five pillars of Vepol's working discipline: memory, coordination triad, weekly review, cross-agent review, event log
Visible disciplineThe system keeps memory, weekly review, cross-agent review and the event log in one readable structure.
Category map for OpenClaw, Hermes and Vepol — presence, runtime and local knowledge field
OpenClaw / Hermes / VepolOpenClaw is presence in channels. Hermes is runtime breadth. Vepol is the controlled self-improvement loop that keeps agency coherent.
Vepol autonomy growth timeline — context compounding from first day to later work
Autonomy compoundsVepol becomes more useful by preserving what was accepted, edited, blocked and learned, then adjusting its next plan.

// operating field

One field for people and agents

Vepol’s self-development is deliberately not hidden inside a model. Runtime can change; strategy, memory, incidents, reviews and autonomy rules stay in plain files.

Vepol architecture diagram — many agents working over one shared knowledge field
Human judgment, CLI agents, plans, incidents, strategies and decisions operate over one local knowledge base that turns experience into safer autonomy.

// open development

Open development

Vepol is used to evolve Vepol: specs, tests, reviews, incidents, strategy updates and follow-up work go through the same knowledge base described on this page.

GitHub repositoryRead the source, docs and release trail.MethodologyHow shared memory, review gates and agent handoff are designed.Demo wikiA synthetic example showing how the knowledge base feels in use.

Waitlist

Want an AI partner that improves with your work?

Leave a short note. We will route it to the lab and reply directly.