Repository navigation
Releases
v0.3.0: npm package and Pi package
Install from npm and as a Pi package. Requested by @cerredz.
Added
- The npm package
vidbyte-memory(the rootpackage.json).npx vidbyte-memory initrunsscripts/install.pyfrom the package's own copy of the template, so it works offline and installs the same release as the package;uninstalland every installer option pass through. It looks for Python 3.9+ the way the agent plugins do (VIDBYTE_MEMORY_PYTHON, thenpy -3,python,python3on Windows). It works once the package is published to npm. - A Pi package in the same
package.json:pi install git:github.com/cerredz/vidbyte-memory@v0.3.0loads the turn-end extension for every repo and theinstall-memoryskill. Thepi-packagekeyword lists it in the Pi gallery once it is on npm. - Template CI tests the npm command end to end (install, then uninstall, from the package's files), packs both npm packages, and fails when
package.jsonstops shipping a file the installer copies.
Fixed
- Hermes on Windows never blocked a turn. Hermes runs from its own venv, whose launcher exports
PYTHONHOME. The project's Python inherited it, died at startup, and the plugin let every turn end. The plugin now dropsPYTHONHOMEbefore it starts the guard. Found in a live Hermes run. - Pi ran the guard twice with both copies loaded. With the Pi package and the project's
.pi/extensions/vidbyte-memory.jsboth loaded, each copy ran the guard. After the guard gave up at round 5, the other copy started a second cycle of 5. Now only the copy loaded last gates the process. Existing task repos: copyintegrations/pi/vidbyte-memory.jsto.pi/extensions/vidbyte-memory.js.
Tested
- The turn-end plugins were run live on 2026-10-30 against a local mock model, in repos with a failing test and an uncommitted file. Each kept the session working until the guard's cap (Hermes: its own cap of 3 nudges per turn).
- OpenCode 1.19.5 and 2.2.4, Kilo 7.8.18, Pi 1.4.0, and Hermes from git through its in-process runner.
- Headless
opencode run(1.x) andkilo runexit before the plugin's new prompt starts. The host pages indocs/hosts/say so.
Changed
opencode-vidbyte-memoryships its license file, ready fornpm publishfromintegrations/opencode.
Full changelog: v0.2.1...v0.3.0
v0.2.1: ready for agent marketplaces
A patch release with fixes found while submitting v0.2.0 to agent marketplaces. The memory itself is unchanged.
Added
.codex-plugin/plugin.json: Codex's own plugin manifest, with full listing metadata (long description, icon, screenshots, privacy and license links), plus a.codexignore. The HOL plugin scanner (plugin-scanner3.58.0) now scores the repo 100/100 with no findings. With that, vidbyte-memory is listed in awesome-codex-plugins.
Changed
- The
install-memoryskill no longer pipescurlinto Python. Outside the plugin, it clones the release it shipped with (git clone --depth 1 --branch v0.2.1 …) and runsscripts/install.pyfrom there. The owner can read the script first, and the install is the reviewed release. A test keeps the tag equal to the plugin version. - GitHub Actions are pinned to commit SHAs.
Task repos made from v0.2.0: copy skills/install-memory/SKILL.md and run python scripts/sync_skills.py.
Full changelog: CHANGELOG.md
v0.2.0: install into any repo, from inside any coding agent
Install vidbyte-memory into any existing repo, from inside the coding agents you already use. Every correction you give the agent still becomes a slim fact, a test that fails if the mistake comes back, and a footprint commit. What's new is that this now works in your repo and your agent, not only in a fresh template copy.
Install
From the repo you want to give memory:
curl -fsSL https://raw.githubusercontent.com/cerredz/vidbyte-memory/main/scripts/install.py | python3 -On Windows PowerShell, use irm … | python -. Add --dry-run to see the plan first. You can also install it as a plugin:
- Claude Code:
/plugin install vidbyte-memory --marketplace cerredz/vidbyte-memory - Codex:
codex plugin marketplace add cerredz/vidbyte-memory, thencodex plugin add vidbyte-memory@vidbyte - Gemini CLI:
gemini extensions install https://github.com/cerredz/vidbyte-memory - Antigravity:
agy plugin install https://github.com/cerredz/vidbyte-memory - Skills only, in any of 78 agents:
npx skills add cerredz/vidbyte-memory
Then ask the agent to "install vidbyte-memory in this repo".
Added
- A one-command installer,
scripts/install.py:- It copies the memory in without overwriting any of your files, and backs up every file it edits.
- It folds your existing
AGENTS.mdinto the new Task section. - It wires the turn-end guard for every agent it finds.
- It lists each write in
.vidbyte-memory/install.json. A second run changes nothing.
install.py uninstallundoes the install:- It deletes what the install created and restores what it changed.
- It takes its hook back out of agent settings you edited since, keeping your own settings.
- It keeps the memory your agent wrote unless you add
--force.
- Enforcement in more agents. While tests fail, feedback is pending or work is uncommitted,
scripts/guard.pykeeps the agent working:- Stop hooks written by the installer: Claude Code, Codex, GitHub Copilot, Gemini CLI and Antigravity. Cursor, Devin CLI and Grok Build read the Claude Code hook.
- New plugins in
integrations/:- OpenCode and Kilo Code: re-prompts the session on idle.
- Pi:
agent_before_settle. - Hermes: a
pre_verifyplugin.
- Plugin manifests, so the repo installs as a plugin:
.claude-plugin/: the Claude Code marketplacevidbyte;plugin.json(Agent Plugins 1.0): Codex, Copilot, Cursor, Kiro, Devin, Goose and others;gemini-extension.json;- an
install-memoryskill.
- Skill mirrors in
.agents/skills/and.claude/skills/, where about 25 agents look for project skills. - docs/hosts: one page per agent (24), each with the install command, what the agent reads and how much is enforced.
Fixed
- Footprint commits failed on Python 3.9.
scripts/footprint.py --writeand--commitcrashed there, the oldest version the README supports. Task repos made from v0.1.0: copyscripts/footprint.py. - Two of the six skills were invisible to skill loaders. Five files had frontmatter values that YAML cannot parse, so the loaders skipped
handle-feedback, the protocol's entry point, and one other skill. The CHANGELOG lists the files to copy.
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
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