Repository navigation
v0.1.0: correction-driven memory for coding agents
First public release of vidbyte-memory: correction-driven memory for coding agents. No API key, no database and no service; agent memory lives as files, tests and git in a repo you own.
Each time you correct your agent, the correction becomes:
- a slim fact or rule the agent loads next time,
- a pytest test or verifier that fails if the mistake comes back,
- a footprint commit that records how memory changed.
See it working in the live example, cerredz/vidbyte-memory-example. Two real corrections became 16 tests and a verifier there. In the next request, a fresh-context verifier caught a missing price tier before the owner saw it.
Added
- The template. It contains:
AGENTS.md, the runtime protocol and memory index;- 17 typed memory files mapped in
memory/MAP.md, plus slim facts infacts/; - six skills;
- three feedback subagent prompts, with Claude Code wrappers;
- the memory-conformance verifier and the memory integrity tests;
scripts/footprint.pyand thescripts/guard.pyStop hook.
- An adoption marker. Footprint commits end with a
Memory-Template: vidbyte-memorygit trailer, so public task repos made from the template can be counted with GitHub commit search. Leave it off one commit with--no-marker, or remove it for good by settingTEMPLATE_MARKER = "". - A landing-page README. It has a quick start you can paste into your agent, a demo, a before-and-after comparison, known limits and an FAQ.
- Agent-readable docs.
llms.txt,context7.jsonand.devin/wiki.jsonlet coding agents and their documentation indexes read the template. - Community files. A contributing guide, a code of conduct, a security policy, issue forms (including "A correction didn't stick"), a pull request template and release-note categories.
- A template-only CI matrix. It tests Python 3.9 and 3.13 on Ubuntu and 3.11 on Windows. It runs only in this repo, so it never uses your Actions minutes.
Credits
Requested by @cerredz. Every release credits whoever asked for each change, so open an issue or a discussion and your name goes in the next one.
Full changelog: CHANGELOG.md